There are many good ways to put an admin UI in front of a database. These pages are the comparison a fair-minded engineer would trust: what cartapel does well, what each alternative does better, and when you should pick them instead. Start with the matrix, then open the one you are actually weighing.
| cartapel | Django admin | Retool | Metabase | Directus | NocoDB | Baserow | pgAdmin | |
|---|---|---|---|---|---|---|---|---|
| Databases | Postgres, MySQL, MariaDB (+ ClickHouse RO) | via Django models | many sources | many sources | several SQL DBs | Postgres/MySQL + own metadata | prefers its own tables | Postgres only |
| Single binary | one Rust binary | part of a Python app | multi-container / SaaS | JVM app | Node app | Node services | Python + Node services | Python app |
| Existing DB, no schema ownership | introspects live schema | ORM models to sync | queries any source | read-oriented | introspects both ways | connects, adds metadata | import-oriented | raw access |
| Config as code / PR review | HCL in git — visual editor or by hand | Python in git | GUI-first; git sync paid | GUI-first; serialize paid | config in DB; snapshots | GUI-configured | GUI-configured | n/a |
| Roles + audit | inheritance, audit + revert | roles solid; audit via packages | full audit on higher tiers | sandboxing is paid | granular roles, revisions | base/table roles | history varies by tier | Postgres roles only |
| Dashboards | SQL tiles, charts, vars | not built in | build anything | best-in-class BI | insights panels | basic views/charts | basic views/charts | DBA charts only |
| License + price | MIT, free | BSD, free | proprietary, per-user | AGPL core; paid Pro | BSL 1.1 | AGPL / open-core | MIT core / paid tiers | Postgres license, free |
Yellow cells are nuanced — open the page for that tool before deciding.
Each is written to be useful even if you end up choosing the other tool.
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.
An open-source Airtable that wants to own the data, versus a panel over data that is already owned.
Keep pgAdmin for engineers. cartapel is the one you can safely give to everyone else.
What cartapel is for: a team with an existing production database that wants a safe, audited, role-scoped operations panel — one binary, config reviewable in a pull request.