Signal Collective
Hong Kong Book a call
Signal Collective The Library Support
We find where your growth is · Then we build it

Support · Tickets triaged, replies drafted, the recurring ones found. · a tool

Find out what customers keep asking for, and let them vote

The open-source project fider, by getfider

“Open platform to collect and prioritize feedback” — the project's own words, on GitHub

What it does
You get a public board of your own where customers post what they want, vote on each other's requests and comment, so the asks that keep recurring in your support inbox stop hiding there and sort themselves by how many people want them. Every request carries a status you set, open, planned, started, completed or declined, with a short public reply, so the people who asked can see what happened without you emailing each of them. You host it on a server you control, so the list of who wants what stays with you. It needs Docker, a small server and working email, because sign-in is an emailed link.
Replaces
a customer-feedback board subscription, or the spreadsheet where support requests go to be forgotten
For
A founder or product lead whose customers keep asking for things inside support threads, and who wants those asks counted in one public place instead of remembered.
Not for
Not for someone with a handful of customers they already talk to every week, a public board only earns its server once enough people are asking to be worth counting, and it will not start at all without Docker and a working email sender.
Setup
30 min · Claude Code, Kimi, Gemini CLI or Codex · docker, docker compose, an SMTP server or Mailgun account to send sign-in emails, a server or small cloud machine to run it on
Tickets, all at once Sorted by kind Drafts, and one for you how do I a bug a refund to a person

Get it running

Paste this into the AI that runs on your computer. It does the install, checks it works, and tells you what to type first. If anything fails, paste the error back to it.

Paste into Claude Code
Install fider (https://github.com/getfider/fider) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Claude Code, running on my machine.

1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password.
2. Create /var/fider/docker-compose.yml from the Hosting on Docker guide at docs.fider.io (the getfider/fider:stable image plus a postgres:17 service), then run docker compose pull and docker compose up -d from that folder.
3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says.
   Tool-specific notes: Create /var/fider/docker-compose.yml with two services, db (postgres:17, data volume at /var/fider/pg_data) and app (getfider/fider:stable, ports 80:3000), copying the guide's file exactly and changing the database password.
Set BASE_URL to the exact public address including http or https, DATABASE_URL to point at the db service, JWT_SECRET to a long random string (openssl rand -base64 48), and EMAIL_NOREPLY to a real sender address.
Email is required, not optional: set EMAIL_SMTP_*, EMAIL_MAILGUN_* or EMAIL_AWSSES_*, or the app exits with panic: could not find environment variable named 'EMAIL_SMTP_HOST'. For a local test only, add the mailhog service from the guide (EMAIL_SMTP_HOST mailhog, EMAIL_SMTP_PORT 1025) and read the sign-in mail at http://localhost:8025.
Run docker compose pull then docker compose up -d in /var/fider; docker compose logs app should show http server started on :3000, then open http://localhost and complete the installation form.
If the log shows dial tcp ...:5432: connect: connection refused, the app started before the database was ready; wait a moment and check the log again, it retries on its own.
If the installation form's confirmation email never arrives, it is the email config; fix it and resend the code from Fider rather than resetting the database.
4. Run the smallest test the README gives, and show me the output.
5. When it works, tell me what to type first, in one line, for this job: Seed it with the asks you already have.
If anything fails, show me the exact error and fix it before going on.

What to point it at first

1

Seed it with the asks you already have

Go through the last month of support replies and post the five requests that came up more than once, in the customer's own words, so the board opens with real items rather than an empty page.

2

Answer one request publicly

Pick one seeded request, set its status to planned or declined with a one-line public reason, and read it back as a customer would, that status line is the whole point of the board.

3

Check who is actually voting

Before you treat a vote count as demand, open the votes list on the top post and check they are distinct customers, not your own team or one person on several sign-ins.

What it must never do unattended

  • It drafts. It never replies to a customer.
  • Anything about money, a refund or a legal word goes to a person.
  • Never let it set a status or post a public reply on a request unattended; a status change is a promise your customers read.
  • Never let it delete a post or mark one a duplicate on its own; both change what every customer sees.
  • Never run the tenant-reset SQL from the docs FAQ on a live board; it deletes every post, vote and comment and cannot be undone.

Who made it

getfider/fider on GitHub, under the AGPL-3.0 licence. 4,514 stars, checked 11 September 2026. Last change 27 July 2026. We did not write it; we checked it, and wrote this page so you can use it.

Also in Support

What's in the library is how we work.

If you're launching or growing a brand across Asia and the West, a call is where we work out whether it's a fit.