Let us start with the honest part: NocoDB is the easiest service on this site to self-host. It runs from a single container, works out of the box with the built-in SQLite, and one line of docker run gets you there in ten minutes. If you just want to try it, self-hosting is entirely reasonable — no need to pay anyone.
But this article is about a different stage: once NocoDB goes from “let me play with this” to “the company’s customer list and orders live in here”, the cost structure changes completely.
The 30-second overview
| Item | Self-hosted | Managed |
|---|---|---|
| Monthly cost (incl. your time) | About NT$1,000–1,800 | NT$499 |
| Biggest time sink | Backups and restore verification | Not your problem |
| Technical bar | You need Docker and database skills | None |
| When self-hosting pays off | You already have a server and this is your Nth service | — |
| Most underestimated | Your ability to restore when the database breaks | |
Self-hosting is easy, but that is not the point
NocoDB has a small appetite for resources. 512 MB of memory serves a small or mid-sized team, far lighter than a multi-container architecture like Dify’s. The cheapest VPS you can find (NT$150–300/mo) is more than enough.
So if you look only at the server’s monthly fee, self-hosting really is cheaper. The problem is that the server fee was never the main cost of self-hosting.
The real cost: backups, and “are you sure they restore?”
What NocoDB stores is usually structured operational data — customer lists, orders, inventory, project tracking. This kind of data has one characteristic: you do not notice the moment it is lost, and by the time you do notice it is too late.
A backup strategy that actually works needs:
- Off-site storage — a backup file on the same machine as the database is not a backup
- Automatic scheduling — a manual backup is not a backup, because people always forget
- Multiple retained points in time — if the data was deleted by mistake three days ago, yesterday’s backup will not save you
- Regular restore drills — the step most often skipped, and the most fatal. A backup you have never restored is just insurance you assume exists
Doing all four and keeping them going is the actual workload of self-hosting NocoDB. That is a completely different level of difficulty from “getting it running”.
The second thing people underestimate: upgrades
NocoDB iterates at a decent pace, and its upgrades occasionally come with database schema migrations. Self-hosted, you have to back up before upgrading, verify data integrity afterwards, and know how to roll back if something goes wrong.
None of that is hard, but it is something somebody has to remember to do. And in a small team, things that “somebody has to remember” are usually things that do not happen — until the day you need a feature only the new version has.
The same comparison in one table
| Item | Self-hosted | RoamerHost |
|---|---|---|
| Server fee | NT$150–300 | NT$499/mo (all in) |
| Backup storage and scheduling | On you | |
| SSL certificate | You request and renew it | |
| Specs | Your call | 1 CPU core / 5 GB storage |
| Time to live | 10 minutes to 1 hour | About 60 seconds after payment |
| Per-user billing | None | None |
| Restore drills | You schedule them | We handle them |
How to choose
Self-hosting makes more sense if: you are still evaluating, the data does not matter much yet, or you already run a solid backup system that can cover this too.
Managed makes more sense if: losing the data in NocoDB would disrupt the business, and nobody on your team owns regular backup verification.
This judgment has nothing to do with technical ability. Plenty of people who could self-host choose managed — not because they cannot, but because they do not want to deal with it on a weekend.
Decision table
| Your situation | Recommendation |
|---|---|
| NocoDB is your first self-hosted service | Managed — one service absorbs all the fixed costs |
| You already have a server and backup mechanism | Self-hosted — low marginal cost |
| It holds the only copy of your customer data | Managed — unless you are confident in your restore process |
| You need to connect to a database on your internal network | Self-hosted — this is an architectural requirement |
| You want to learn Docker and database operations | Self-hosted — the time cost is tuition |
Why backups are the crux for this particular service
NocoDB is different from n8n or Dify: it holds your data itself, not a process that handles data.
A broken n8n workflow can be rebuilt; a Dify knowledge base can be re-uploaded. But NocoDB holds customer lists, order records, inventory movements — and nowhere else has a copy of those.
So the real cost of self-hosting NocoDB is not the install; it is building and maintaining a backup mechanism that genuinely restores. That involves three things:
- Regular backups — including the database, not just the files
- Off-site storage — a backup on the same machine as the database disappears with the disk
- Regular restore drills — a backup you have never restored does not count as a backup
The third is the most commonly skipped and the most fatal. Most people discover their backup file is corrupt on the day they actually need to restore it.
The full cost of self-hosting
Time is valued at NT$600/hour below; substitute your own number and recalculate:
| Item | Amount/month | Notes |
|---|---|---|
| VPS | NT$300–600 | Runs the app and the database |
| Initial setup, amortized | NT$100–300 | 2–5 hours, spread over 12 months |
| Version upgrades | NT$300 | About 0.5 hours per month |
| Backups and restore verification | NT$300–600 | 0.5–1 hour per month; this is the crux |
| SSL and miscellaneous | NT$100 | |
| Total | NT$1,100–1,900 | In a month where nothing breaks |
FAQ
Q: Is my data safe on someone else’s server?
Every instance is an isolated container on an isolated network. The thing to watch is not “whose machine is it on” but whether you can export everything at any time — that is what keeps you from being locked in.
Q: With managed hosting, who owns backups?
The managed environment has system-level backups. Even so, we recommend exporting your important data periodically yourself — any backup mechanism can fail, and one extra copy costs very little.
Q: How powerful a machine does self-hosting need?
NocoDB itself is not heavy, but it has to run a database. Actual requirements depend on your data volume and concurrent users; a typical small team does not need much.
Q: Can I connect it to my existing database?
NocoDB supports connecting to existing databases. That is genuinely useful when you already have a system and just want a good interface on top of it, and it is one of the real advantages of self-hosting.
Q: When is self-hosting mandatory?
When the data cannot leave your own data center, or when you need to reach a database on your internal network. That is not a cost question, it is an architecture question.
Sources and further reading
NocoDB’s field types and permission model follow the official documentation:
Further reading
- NocoDB tutorial: create your first table and view
- Introduction to NocoDB
- NocoDB vs Airtable: data sovereignty, row limits and cost
- NocoDB API quickstart
- RoamerHost managed NocoDB plans
Want someone to build it for you?
As data volume grows, or when it has to plug into your company’s existing systems, this stops being just a tool choice. Roamer Tech takes on enterprise system customization and API integration:
