Baserow is an open-source Airtable, and it is a good one: grids, views, form building, collaboration and a plugin system, self-hostable under an open licence. If the question is where a small team should keep a new dataset, Baserow is a reasonable answer and cartapel is not.
The distinction that matters here is ownership. Baserow is happiest creating and managing its own tables inside its own database — that is the product. Connecting it to a production schema owned by an application is going against the grain, where cartapel is designed for exactly that: introspect what exists, change nothing, and expose only what you register.
The second distinction is where configuration lives. Baserow is configured by clicking, and that state sits in its database. In cartapel the panel is a directory of HCL files in your repository, reviewed in pull requests and deployed with your code.
| cartapel | Baserow | |
|---|---|---|
| Where the data lives | Your existing database, untouched | Its own tables, in its own database |
| Existing production schema | The whole point — introspected at boot | Against the grain; import-oriented |
| Feel | Admin panel | Airtable-style no-code database |
| Configuration | Visual editor or HCL by hand — both produce files in git, reviewed in PRs | Clicked in the UI |
| Runtime | One Rust binary | Python and Node services |
| Audit and revert | Built in — before/after diff, one-click revert | Row history and trash, varies by tier |
| License | MIT, free, no seats | MIT core with paid premium/enterprise features |
Yellow cells are nuanced — the sections below say why.
Pick Baserow if The data does not exist yet and non-technical people should own it.
Pick cartapel if The data lives in a production database and an application owns the schema.
No login. Click anything — the demo resets on a schedule.
The admin you already know — but the live schema is the model, and there is no Python app to host it.
The open-source, self-hosted answer when what you actually needed was a database panel, not an app builder.
Metabase answers questions about the data. cartapel changes it, safely, and writes down who did.
The closest philosophical neighbour — same introspection bet, a much larger surface, and a different licence.
A spreadsheet over your database, versus a reviewable panel over a schema you did not want touched.
Keep pgAdmin for engineers. cartapel is the one you can safely give to everyone else.
Everything on one page: the full matrix against all seven.