Open Source Featurebase Alternatives

Fider is a feedback portal for feature requests and suggestions. Product decisions drawn from scattered emails, support tickets and hallway opinions are guesses. Fider gives your customers a voice and lets them tell you what they need, so you spend less time guessing and more time building the right product.

The mechanics stay simple on purpose. Anyone submits an idea or a request, everyone votes, and the discussion happens in a thread under the post. Submissions remain searchable and organized rather than getting lost, and a board can be published to customers or kept inside a team.

A board can be shaped to fit the product it serves.

• Voting: the audience decides which requests matter most.
• Discussion threads: conversation attached to each individual request.
• Branding: a custom welcome message, a custom domain and your own look.
• Multiple languages: an interface translated for an international audience.
• Private boards: feedback restricted to a team instead of published.
• Moderation and SEO indexing: content control and search visibility on the paid plan.

There are two ways to run it. Fider Cloud is fully managed by the creators, with a free tier capped at 250 feedback items and unlimited users, voting and discussions. Self-hosting is free, and most people use Docker to run Fider on their own infrastructure, with guides for Coolify, AWS, Azure and Heroku. Development is supported by donations and sponsors on Open Collective.

LogChimp gives customer feedback one address instead of a dozen. Requests that would otherwise sit in support tickets, sales calls and direct messages land on a board where the team can read, organize and act on them, and where customers can see what happened next.

The whole thing is self-hosted and brand customizable, so the board looks like part of your product rather than a vendor's. A dashboard behind it manages posts, boards, users, roadmaps and roles, and the project positions itself for anyone from a new startup to an established company that wants to build around what users ask for.

The pieces that make up a feedback loop are all here.

• Boards: posts are grouped so feedback arrives in the right place rather than one undifferentiated pile.
• Roadmaps: show what is planned, underway and shipped without writing a separate status page.
• Comments: discussion happens on the post itself, currently in beta.
• Brand customization: colors and identity are yours, front end and back.
• Role-based access control: seven permission levels covering site owner, admin, moderator, manager, user, contributor and viewer.
• User management: see who is participating and what they have been doing across the site.

Linux is the recommended production environment, and deployment options run from Docker and Docker Compose to one-click installs on Railway, Render and Coolify. Contributions are welcome with one condition worth knowing up front: discuss the idea in public channels and get core team approval before you start writing code.

ClearFlask collects product ideas from users and turns them into a public roadmap. It is positioned as an alternative to Canny and UserVoice, so a team can keep its feedback portal, customer dashboard and roadmap on infrastructure it controls rather than renting the whole conversation.

The codebase separates an OpenAPI definition from a Java server and a React frontend. A Node server nicknamed Connect serves static files and server-side rendered pages and issues TLS certificates for customer domains, while the backend keeps most data in DynamoDB, replicates it to Elasticsearch for search, serves uploads from S3 and uses KillBill for billing.

Self-hosting is the part the documentation covers most closely.

• One-click deploy: a Railway template runs a self-contained instance with API server, rendered frontend and MariaDB on a generated domain.
• Docker Compose: a single compose file with a dependency profile brings everything up and opens on localhost.
• Kubernetes: Helm charts install ClearFlask and its dependencies after you generate the signing and cursor secrets.
• Storage choice: search runs against Elasticsearch or MySQL, with a documented migration between them.
• Domains and mail: a custom domain needs DNS and certificate setup, and outgoing email is configured separately.

Managed hosting is offered by the maintainers for teams that would rather not operate any of this. The self-hosted path suits a product team that wants its feedback portal on its own domain and its data in its own account.

Release notes only get written when someone remembers to write them. Changes.Page is a changelog platform where updates are composed in a markdown editor with live preview and image uploads, or pushed straight from a CI pipeline through its command line tool, which takes the remembering out of it.

The application is built on Next.js and Tailwind CSS with Supabase for data, Inngest for background work and Postmark for mail. Self-hosting is documented in the repository, and a local run needs Node 18 or newer with pnpm, environment files for the web and page apps, and your own Supabase instance.

Around the changelog itself sit the features a public update page needs.

• Roadmap boards: a public board collects ideas and lets your audience vote on them.
• Publishing controls: posts can be scheduled, pinned and reacted to by readers.
• Custom domains: a changelog runs on your own domain with a certificate included.
• Embedding: a React SDK and a widget put updates inside your product, with a JSON API and an RSS feed for everything else.
• Integrations: GitHub and Zapier connect the changelog to the tools already in your release process.
• Analytics: visitor numbers show which updates people are actually reading.

Email notifications are an add-on rather than part of the base, and team members can be invited into a page. The hosted service is priced per page with a free trial, which leaves the repository as the route for anyone who would rather run the whole thing themselves.

ShipShipShip publishes a changelog and a public roadmap from one small self-hosted service. The updates, the reactions and votes readers leave on them, and the newsletter announcing a release all belong to the same instance, which is a lot less to run than a hosted changelog plus a feedback board.

The backend is Go with Gin, GORM and SQLite, and the admin panel is a SvelteKit application using Svelte 5, TailwindCSS, shadcn-svelte and the TipTap editor. One Docker image covers AMD64 and ARM64, configuration is environment variables, and the data directory holds the database, uploads and themes.

The admin side covers the work around an update.

• Rich entries: entries are written in a TipTap editor with markdown support, tags and media uploads.
• Kanban board: a drag and drop board moves entries between statuses you define yourself.
• Voting: readers vote on proposed features before anyone builds them.
• Reactions: eight emoji reactions give readers a lighter way to respond.
• Newsletter automation: emails send themselves when an entry reaches a chosen status.
• Themes: the public changelog is an installed theme with its own settings and status mapping.

A REST API exposes public events, reactions and newsletter signups, with admin routes behind a JWT. The project is Apache 2.0, and a demo instance with published credentials is open for anyone who wants to click through the admin panel before installing it.

Reflet gives a product team one place for the feedback that otherwise arrives through support tickets, sales calls and direct messages. Users submit requests, other users upvote and comment, and tags, filtering and full-text search turn the pile into an ordered view of what matters to the people actually using the product.

Those same items then move across a kanban roadmap through backlog, planned, in progress and done, and release notes link back to the features that were requested, closing the loop with whoever asked. Real-time collaboration keeps every connected client in sync, which the Convex backend handles natively.

The rest of the product handles what a public board exposes you to.

• Privacy control: boards can be public or private, so internal discussion stays apart from the customer-facing list.
• Organizations: multi-tenant workspaces with team invitations and owner, admin and member roles.
• Branding: public pages take your colors, custom CSS and your own domain.
• Notifications: status changes, new comments and vote milestones are surfaced without flooding anyone.
• Changelog: release notes are published to users and tied to the requests they answer.

It is React 19 and Next.js on the front with Convex behind it, Better-Auth for sign-in and a Turborepo and Bun toolchain, self-hosted with a clone, an install and one backend setup command. The license is the SSPL: free to use, modify and self-host, but not to resell as a competing hosted service.