getfider/fider

Open platform to collect and prioritize feedback

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 15th, 2026
Created on January 17th, 2017
Open Issues & Pull Requests: 60 (+0)
GitHub issues: Enabled
Number of forks: 853
Total Stargazers: 4,533 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.9 days
Mean response time: 114.5 days
90th percentile: 259.3 days
Tracked items: 121

Most active contributors

Sign in to see contributor activity.

How this project is maintained

95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 89% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 22
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 589 days
Stale 30+ days: 21
Stale 90+ days: 15

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type: bug (45)
  • help wanted (6)
  • type: enhancement (6)
  • good first issue (5)
  • type: new feature (4)
  • go (3)
  • javascript (2)
  • Bounty - 50 USD (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Fider is a feedback portal that collects and prioritizes feature requests and suggestions from customers.

The tool addresses the problem of product teams spending time guessing what customers need rather than building based on validated demand. Fider provides a platform where customers can submit feature requests and suggestions, which the team can then organize and prioritize. This approach shifts decision-making from speculation to data-driven feedback collection, helping teams understand what their users actually want.

Fider suits organizations that want to involve customers in product direction decisions. It works well for teams building products where user input is valuable for prioritization. The project offers both a managed cloud service for teams wanting minimal operational overhead and a self-hosted option for those preferring to run it on their own infrastructure. Self-hosting is free but requires the organization to handle updates and maintenance.

The project maintains active engagement with its community through a public feedback instance where users can see how the tool itself is being developed. Development activity shows consistent responsiveness to issues and pull requests, with maintainers actively reviewing contributions. The project accepts donations and sponsorships to support ongoing development, indicating a sustainable model for long-term maintenance.