cartapel vs Directus

Directus is the closest thing to cartapel in this list, and shares its central bet: point it at an existing SQL database, introspect the schema, and do not demand that you rebuild your data model to suit the tool.

On top of that it does considerably more. It generates a full REST and GraphQL API over your data, has a flow and automation engine, digital asset management, and works as a headless CMS. If your admin layer must also be your API layer, Directus is the stronger platform and cartapel is not a candidate.

The differences are footprint, authoring and licence. Directus is a Node application whose configuration — collections, fields, permissions, flows — lives in its own system tables inside your database; it is exportable as schema snapshots, but it is not primarily authored as files. And since version 10 it is licensed under BSL 1.1: free below a revenue threshold, not open source in the OSI sense. cartapel is deliberately smaller: one MIT binary, no API generation, no app platform, and the whole configuration is plain HCL in your repository.

The Permissions tab of the Customize drawer in cartapel, with per-role and per-column rules
Permissions are part of the same file as the rest of the screen — not rows in a system table added to your database.

Side by side

cartapel Directus
Scope Admin panel only Panel + REST/GraphQL API + flows + DAM + CMS
Existing database Introspects the live schema Introspects, and mirrors schema changes both ways
Databases Postgres, MySQL, MariaDB (+ ClickHouse read-only) Postgres, MySQL, SQLite, MSSQL, Oracle and more
Runtime One Rust binary Node application
Where config lives Visual editor or HCL by hand — both produce files in git, reviewed in PRs System tables in your database; snapshot export
Writes to your schema Never — reads the schema, writes only rows you allow Adds directus_* system tables
License MIT, free, no seats BSL 1.1 — free under a revenue cap
Audit log Built in — before/after diff, one-click revert Activity and revisions tracked

Yellow cells are nuanced — the sections below say why.

Where Directus is the better answer

Where cartapel is the better answer

The short version

Pick Directus if You are choosing a data platform — API, automations and content alongside the admin.

Pick cartapel if You are choosing an admin panel, permissively licensed, with configuration that lives in git.

Try the live demo Get started GitHub

No login. Click anything — the demo resets on a schedule.

Questions people actually ask

Does cartapel create tables in my database?
No. It reads your schema and writes only to the rows and columns you expose. Its own state — sessions, audit log, saved views — lives in a small separate data directory, so the database it administers stays exactly as your application defined it.
Can cartapel serve an API like Directus?
No, and it is not planned. If you need a generated REST or GraphQL layer over the same schema, Directus is the better fit.
What does BSL 1.1 mean in practice?
Directus is free to use below a company revenue threshold and requires a commercial licence above it, with each version converting to a fully open licence after a delay. Whether that matters depends on your company; cartapel is MIT with no such condition.

Other comparisons

cartapel vs Django admin

The admin you already know — but the live schema is the model, and there is no Python app to host it.

cartapel vs Retool

The open-source, self-hosted answer when what you actually needed was a database panel, not an app builder.

cartapel vs Metabase

Metabase answers questions about the data. cartapel changes it, safely, and writes down who did.

cartapel vs NocoDB

A spreadsheet over your database, versus a reviewable panel over a schema you did not want touched.

cartapel vs Baserow

An open-source Airtable that wants to own the data, versus a panel over data that is already owned.

cartapel vs pgAdmin

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.