Fider Hosting
Collect customer feedback, organize requests, and let users vote on product ideas.
- One click deploy
- 1 GB RAM Memory needed
- 15 GB Disk Space Needed
- From 2 € Price
Official links
Fider’s official links and original website
Fider Website
More
Tech
- Docker image
- getfider/fider:stable
- Default port
- 3000
- Database
- postgres
How Fider works
A team creates a feedback site where visitors submit suggestions, vote for ideas they support, add comments, and see status changes. Administrators moderate content, merge duplicates, assign tags, and update a suggestion as it moves from consideration to planned, completed, or another configured state. The board gives customers a visible place to contribute without exposing the internal engineering tracker.
Fider uses PostgreSQL for accounts, posts, votes, comments, tags, and settings. Its upstream authentication flow sends sign-in links by email. The catalogue setup can expose an initial configuration session, but AvaHost application email is disabled, so returning administrators and users cannot complete the normal email-link authentication flow afterward.
Key Fider features
Voting helps a team observe relative interest, while comments capture the problem behind a request. Tags and statuses organise the board, and duplicate handling prevents the same idea from fragmenting across several posts. Public visibility can reduce repeated support questions about requested features.
The application should complement rather than replace product judgement. Vote totals reflect the audience that visits the board and may not represent revenue, strategic importance, effort, security, or regulatory obligations. Internal planning still needs its own decision process.
Fider vs Canny
Fider is a self-hosted feedback board focused on suggestions, votes, comments, tags, and public status updates. Canny is a provider-managed customer-feedback platform that combines boards with roadmaps, changelogs, user segmentation, integrations, and commercial account administration.
Canny may suit teams that want a vendor-operated service linked to their customer and product tooling. Fider is more appropriate when the organisation wants a straightforward board on its own infrastructure, but the hosted authentication limitation must be resolved before it can serve as a dependable production feedback portal.
Who uses Fider
Software teams gather feature requests, open-source communities collect proposals, and service providers let customers vote on improvements. The board can also help a small product organisation publish status changes without granting customers access to a private ticketing or development system.
Fider is not a survey platform, support desk, or roadmap execution tool. It records and discusses product ideas; detailed research, private customer data, delivery estimates, and internal work should remain in systems designed for those tasks.
Self-hosting Fider: requirements and cost
Usage grows with registered users, suggestions, comments, votes, searches, and moderation activity. PostgreSQL stores the complete feedback record and is provisioned beside Fider, but it remains unmanaged. The database memory is not part of the exported application minimum, which moves the corrected deployment to the next public plan.
Fider carries no separate catalogue software fee, and AvaHost maps it to Plan 2 at €5. The platform includes one-click deployment, a custom feedback domain, automated HTTPS, automatic application updates, and scheduled backups. Application email is disabled, so Fider's emailed-link sign-in cannot be used after the initial setup session; this is a material service limitation.
F.A.Q
Fider starts at €5 on Plan 2 after accounting for its PostgreSQL container. The hosting package includes a feedback domain, automated HTTPS, application updates, and scheduled backups. User registrations, suggestions, votes, comments, searches, and moderation activity determine whether the board later benefits from additional resources.
The one-click stack creates PostgreSQL and connects Fider to it. User identities, suggestions, votes, comments, tags, statuses, and configuration depend on that database. PostgreSQL is included but unmanaged, so its records and any persistent application data must be considered together when planning updates, migration, export, or recovery.
A custom domain can be connected to the Fider board with automated HTTPS once DNS points to the service. Select the final address before publishing feedback links or embedding them in a product. After connection, verify the initial setup, public board, voting pages, comments, and any integrations that reference the previous hostname.
Normal return sign-in is not functional on the current AvaHost configuration. Fider authenticates users through emailed links, while application email delivery is disabled. The first setup page may create an initial session, but administrators and contributors cannot rely on future authentication. The service should not be treated as production-ready until that dependency is changed.