Self-hosted feedback tools vs cloud: how to choose

You've decided you want a feedback board. The next question is where it lives: on a server you run, or with a company that runs it for you.

Raw cost is the first thing people usually compare, but it doesn’t tell the full story.

The real issue is who's going to look after it. Self-hosting a feedback tool costs you less in money and more in attention. Paying for a hosted one is the opposite.

And if your board is small, there's a third solution worth knowing about: most hosted tools have a free tier that beats anything you could run yourself, at least until you outgrow it.

Here's how the two major options differ, where the free tier fits, and what to check before you commit.

What you're really choosing between

Plenty of feedback tools are open source, so you're often choosing between two ways of running the same software (rather than between two different products). You can run it on a server you control, or pay the people who build it to run it for you. (Fider works both ways.)

Three things change depending on which you pick:

• Who runs the server. Updates, uptime, and security patches.
• Who holds the database. Your infrastructure or theirs.
• Who fixes it when it breaks. You, or their support team.

Hosted tools also tend to bundle extras around the feedback board, like a roadmap page, or a changelog. Whether you need those on day one is a separate question, and the answer might well be no.

What self-hosting costs

It’s usually somewhere between $5 and $60 a month for a small board, depending on how much you want handled for you.

Expect to see something like three tiers:

• Bare bones. One small server running the app and the database together, around $5 a month.
• Managed platform. Something that handles deployments, updates, and certificates for you, roughly $15 to $30.
• Comfortable. Add a managed database with backups included, and you're at $35 to $60.

There are two extra costs to watch out for. The first is transactional email. Your board sends sign-in links and notifications, so you need a service that delivers them. Pay-per-send providers charge around $0.10 per 1,000 emails, so a small board's bill rounds to nothing. The fixed-price services start around $15 a month, which will be more than the server costs.

The second is backups. and they're cheaper than you might expect. A feedback board is almost all text, so even a busy one is a few megabytes of database, which costs a fraction of a cent a month to store. Most hosts will snapshot the whole server for about 20% on top of the plan, turning a $5 server into a $6 one. The real cost is the afternoon you spend setting it up, not the storage.

Server prices move, too. Hetzner is one of the cheapest options around, and it raised cloud prices twice in 2026, with entry-level plans going up by roughly 30%. Running your own server is more predictable than metered SaaS pricing. It isn't fixed.

What hosted pricing does as you grow

In most cases, it makes sense to start with the free tier. Most hosted tools have one, and for a board with a couple of dozen voters it's cheaper and faster than anything you'd set up yourself.

Past that, you’ll want to keep an eye on the pricing structure:

• Per seat. You pay for each of your own people with an admin login, not for the users posting on the board. A busy board doesn't change the bill (but hiring does).
• Per tracked user. You pay for everyone who posts, votes, or comments. Your bill goes up when the board gets popular.
• Flat rate. One price whatever happens, usually with a lower ceiling on features.
• Metered extras. AI features are increasingly billed per use, on top of the plan.

For a small team past the free tier, expect somewhere between $20 and $100 a month.

Enterprise tiers cost a lot more and buy things like single sign-on and compliance paperwork. Possibly dedicated support, too. If these aren’t on your radar already, you're probably not the intended customer.

The cost that isn't on any pricing page

Maintenance is where the two options really part company, and the published estimates are all over the place.

Companies selling self-hosted software put the upkeep at about an hour a month. Companies selling hosted plans put it closer to ten. Everyone quoting a figure has a stake in the answer, so look at the jobs instead:

• Updates. Pulling a new version and restarting takes minutes once you've scripted it. If you leave it for a year, you're jumping several versions at once, which is a much bigger job.
• Database upgrades. Roughly annual, and higher stakes than the rest. Worth rehearsing on a copy first.
• Backups. Testing that a restore works properly is something people skip. So a broken backup usually gets discovered on the day it's needed.
• Email deliverability. The DNS records take an hour to set up once. Working out why sign-in emails suddenly land in spam can take a lot longer.
• Spam and moderation. This scales with how busy your board is, not with where it runs. What changes is the tooling: some paid plans include moderation features you'd otherwise handle by hand. (Moderation tools come with Fider's paid plan.)

None of these are particularly difficult. But if nobody on your team is comfortable with Docker and a Linux box, self-hosting isn't "free." You’ll just pay the bill in hours instead of dollars.

Getting your data out

Whichever way you go, run an export in your first week, before the board fills up, and look at what you get.

Post titles, descriptions, statuses, and vote counts usually survive a move between tools. Those are the fields the common CSV exports and importers handle.

What tends to fall out is anything a spreadsheet row can't hold:

• Who voted. The count comes across, but not the names. Voter lists are usually a separate export, and sometimes available only one post at a time.
• Per-post subscribers. Rarely part of a standard export, so notifications get rebuilt by hand.
• Comments. Some importers carry the threads across. Some drop them.
• Formatting. Post text can arrive as HTML that needs cleaning up before it will import anywhere else.

Losing the voter list is a bad one. A board's value sits in the record of who wanted what. Without those names you can't go back and tell people you delivered what they asked for, which is the habit that keeps a board alive.

Running that export takes 10 minutes, and it tells you how much of your board you'd lose if you ever moved.

One more thing worth checking on the open-source side: some projects put certain features behind a paid license even when you host the software yourself. Read the license before you assume self-hosting means everything's included.

Which way to go

Lean toward running it yourself if:

• Someone on the team is comfortable with Docker, Postgres, and a Linux box
• You have rules about where your data lives
• Your team is growing faster than your board is, so per-seat pricing would sting
• You want to change how the tool works, not just how it's configured

Lean toward paying for hosting if:

• Your board is small enough that a free tier covers it
• Nobody on the team wants to own a server
• You'd rather spend the afternoon on your own product
• You want the roadmap and changelog pages ready-made

Still unsure? Start hosted and get the board live this week. Two months of real posts will teach you more about what you need than any comparison, this one included.

And whichever you pick, the thing that decides whether it works is whether you keep answering posts, not where it's running.

‍