Fider

Overview

Fider is a free, open-source feedback platform designed to centralize customer feature requests, enable community voting, and provide transparent product decision-making. It turns scattered feedback (emails, Slack, spreadsheets) into a structured, prioritized workflow visible to customers.

Core Functionality

Feedback Submission & Organization

• Customers submit feature requests with title, description, status
• Tag and filter requests by theme, product area, priority
• Status tracking: Planned, In Progress, Completed
• Organize large volumes of feedback systematically

Community Voting & Prioritization

• Users vote on feature requests
• Most popular ideas rise naturally to top
• Transparent priority based on community demand
• Shows which ideas are gaining traction

Transparency & Engagement

• Public roadmap showing planned features
• Status updates keep community informed
• Notification system for suggestion updates
• Community feels heard and valued

Public Idea Boards

• Submit feedback without friction
• Anonymous submission option (no login required)
• View all community feedback
• Vote on others’ ideas
• Comment and discuss improvements

Key Features

Customization & Branding

• Custom CSS styling for brand alignment
• Custom domain names
• Logo and color customization
• Feels integrated with your product
• White-label ready

Integrations

• Slack webhooks for notifications
• Discord webhooks for alerts
• Public API for custom integrations
• Zapier support (community)
• Third-party automation options

Multi-Language Support

• Available in 10+ languages
• English, Spanish, French, German, etc.
• Global audience support
• Localized interface

Privacy & Access Control

• Public or private feedback sites
• Control who can submit/vote
• Restrict access to team or customers
• Sensitive feedback protection

Analytics & Insights

• Voting patterns and trends
• Popular feedback tracking
• Engagement metrics
• Comment activity analysis

Setup Process

Simple 4-step workflow:

1. Sign up (fider.io cloud or self-host)
2. Customize with logo, colors, text
3. Invite people to suggest ideas and vote
4. Respond to suggestions and update status

Takes ~15 minutes to launch.

Deployment Options

Cloud Hosted (fider.io)

• Zero setup required
• Automatic updates
• Included hosting
• Paid plans for privacy/branding

Self-Hosted

• 100% open-source
• Docker-based deployment
• Complete control over data
• Customizable codebase
• Free (your infrastructure cost)

Use Cases

Optimal for:

• SaaS products validating feature ideas
• Startups seeking customer input
• Teams gathering structured feedback
• Transparent product roadmapping
• Reducing scattered feedback
• Building community engagement

Not ideal for:

• Bug tracking (use GitHub Issues instead)
• Internal feedback (use Slack/email)
• Support requests (use Zendesk/Freshdesk)

Comparison with Alternatives

vs GitHub Issues

• Fider simpler for feedback
• GitHub Issues for bugs/tasks
• Fider has voting, Issues have tracking

vs Canny

• Fider open-source, free to self-host
• Canny proprietary, $50+/month
• Similar features, different philosophy

vs StatusPage

• StatusPage for status updates
• Fider for feature requests
• Different use cases

Strengths

• 100% open-source: Full transparency, customizable
• Free self-hosting: No SaaS costs
• Community voting: Organic prioritization
• Easy setup: 15 minutes to launch
• Multiple languages: Global reach
• Privacy options: Control over data
• Transparent roadmap: Builds customer trust
• API available: Custom integrations

Limitations

• Community moderation: Requires active management
• Scope creep: Feedback volume can be overwhelming
• Limited integrations: Smaller ecosystem than Canny
• Self-hosting complexity: Docker/infrastructure required
• No AI features: Manual feedback analysis
• Basic analytics: Less detailed than enterprise tools

Key Metrics

Success Indicators

• Active submission rate
• Voting participation
• Feature request completion rate
• Customer satisfaction with process
• Time-to-response for feedback

Typical Usage

• 2,000+ sites globally
• 30,000+ total ideas
• 200,000+ total votes
• Growing open-source community

Getting Started - Cloud

1. Visit fider.io
2. Sign up with email
3. Create feedback site
4. Customize branding
5. Invite users (via email, link, or embed)
6. Launch and promote

Getting Started - Self-Hosted

1. Clone GitHub repo: fider/fider
2. Docker Compose setup
3. Configure environment variables
4. Run docker-compose up
5. Access at localhost:3000
6. Customize and deploy to production

Requirements:

• Docker and Docker Compose
• PostgreSQL database
• Basic Linux knowledge
• Domain name (optional)

Workflow Example

1. Customer submits idea: “Dark mode for dashboard”
2. Community votes: 47 upvotes, 3 comments
3. Product team evaluates: Mark as “Planned”
4. Notify subscribers: Status update sent
5. Feature developed: Update to “In Progress”
6. Launch feature: Mark as “Completed”
7. Customer sees it: Recognition and satisfaction

Integration Examples

Slack notification

• New high-vote requests → product channel
• Status updates → feedback channel
• Weekly summary → team channel

Discord notification

• New feedback → feedback-requests
• Vote milestones → trending
• Status changes → roadmap

Custom API

• Pull feedback into internal dashboard
• Sync with Jira/Linear for task creation
• Export for quarterly reviews

Moderation Best Practices

• Review submissions: Check for duplicates/spam
• Respond promptly: Comment within 24 hours
• Set expectations: Clear status update schedule
• Merge duplicates: Consolidate similar requests
• Engage community: Thank voters, ask clarifying questions
• Communicate delays: Explain why features are “Planned” long-term

Pricing

Cloud (fider.io)

• Free tier: Basic features, community site
• Pro: $25/month - custom domain, branding
• Business: $100/month - private sites, webhooks
• Enterprise: Custom pricing

Self-Hosted

• Free (open-source)
• You pay for hosting infrastructure only

Best For

• Startups: Low cost, fast feedback loop
• SaaS companies: Transparent roadmapping
• Open source: Community engagement
• Budget-conscious: Free self-hosting option
• Privacy-focused: Self-hosted control

When NOT to Use Fider

• Don’t use for bug tracking (→ GitHub Issues)
• Don’t use for support tickets (→ Zendesk/Freshdesk)
• Don’t use for internal-only feedback (→ Slack)
• Don’t expect AI analysis (→ Canny for advanced features)

ROI & Benefits

Hard ROI

• Reduced support inquiries (customers see roadmap)
• Prioritized development (votes show demand)
• Lower cost than surveys
• Free self-hosted option

Soft ROI

• Increased customer loyalty
• Transparent communication
• Community engagement
• Product-market fit validation
• Customer retention

Common Pitfalls

Over-committing to feedback

• Solution: Be realistic about roadmap
• Mark features “Considered” if not planned

Ignoring negative feedback

• Solution: Engage thoughtfully
• Thank users for input even if feature rejected

Letting community moderation slide

• Solution: Assign owner
• Review daily initially, then weekly

Not promoting enough

• Solution: Email all customers
• Add link to product/website
• Include in onboarding

Getting Started Checklist

• Decide cloud vs self-hosted
• Set up and customize
• Invite initial user group
• Create 5-10 example features
• Plan moderation schedule
• Set communication expectations
• Promote to customer base
• Monitor for first month
• Iterate based on usage