NocoDB without the DevOps overhead
NocoDB turns your MySQL or Postgres server into a spreadsheet-style interface. If you already run a database server, that's useful. If you don't, it means setting up Docker, Node.js, reverse proxies, and database migrations before you can type a single record.
What NocoDB asks of you
NocoDB is open source and self-hosted. That appeals to people who want control over their data and their stack.
The cost is operational. You provision a Linux VM or a Docker host. You set up Node.js, configure environment variables, manage SSL certificates, and run database migrations when NocoDB updates. For a developer who already maintains servers, this is routine. For a photographer, a landlord, or a small shop owner, it's a second job.
The web interface works well once it's running. The problem is getting there and keeping it there.
What Dosirak does instead
Dosirak is a native desktop app for macOS and Windows. Download it, open it, and start.
A project is a folder on your disk. TOML defines the schema. SQLite stores the records. No containers, no server process, no port forwarding.
Your AI agent connects through the embedded MCP server. It reads the schema, queries records, and files updates as todo cards for your approval. All of this runs locally.
NocoDB and Dosirak, side by side
| NocoDB | Dosirak | |
|---|---|---|
| Setup | Docker + Node.js + database server | Download and open |
| Hosting | Self-hosted Linux/cloud VM | Local (your Mac or PC) |
| Underlying database | MySQL or PostgreSQL | SQLite (embedded) |
| Web access | Yes (browser-based) | No (desktop app) |
| Multi-user | Yes, with auth | Single operator |
| Schema format | SQL (in the connected database) | TOML files in a folder |
| API / Agent | REST API | Embedded MCP server |
| Maintenance | You manage updates, backups, SSL | App updates; data is a folder |
Where NocoDB wins
- Existing SQL databases. NocoDB connects to a MySQL or Postgres server you already run and gives it a spreadsheet frontend. Dosirak creates its own SQLite stores. It cannot sit in front of your existing SQL server.
- Web access for a team. NocoDB serves a browser UI that 10 to 15 people can use from different machines. Dosirak is a desktop app for one person.
- Full-stack control. Self-hosted means you own every layer, from the reverse proxy to the database engine. Some teams want that responsibility.
If you manage servers for a living and want a web-accessible spreadsheet over your existing database, NocoDB is the better fit.
Where Dosirak wins
- Zero infrastructure. No Docker, no Node.js, no VM, no SSL cert. A native app on your desktop.
- Instant startup. Open the app. Open a project folder. The data is right there.
- Native agent protocol. MCP is built into the app, not bolted on through a REST API.
- Git-syncable schemas. TOML files version-control cleanly. Schema changes show up as readable diffs.
Questions
Does Dosirak use the same database as NocoDB?
NocoDB connects to MySQL or PostgreSQL. Dosirak uses SQLite in a local folder. Both are SQL databases, but SQLite runs embedded with no server process.
Can I import data from NocoDB?
Export your NocoDB tables to CSV and import them into Dosirak.
Is Dosirak open source?
The project format (TOML schema + SQLite) is open. The desktop application itself is not open source.
Does Dosirak require Docker?
No. Dosirak is a native desktop app. Download, open, and start. No containers, no Node.js, no server.
Can Dosirak connect to an existing MySQL or Postgres database?
No. Dosirak creates its own SQLite databases in local project folders. It is not a frontend for existing SQL servers.