Directus vs Strapi vs Payload

Architecture comparison 3 projects Built from source-audited deep dives

All three are TypeScript headless CMSs with REST and GraphQL. Directus wraps an existing SQL database and generates its APIs from the live schema, with a Vue admin; Strapi defines content types as JSON schema files and syncs the database to them, with a React admin on Koa; Payload installs into your own Next.js app and reaches Postgres, SQLite or MongoDB through adapters.

Directus Strapi Payload CMS

Directus: TypeScript · NOASSERTION
Strapi: TypeScript · NOASSERTION
Payload CMS: TypeScript · MIT
Updated: 2026-09-26

Which one should you pick?

Pick Directus if…

You already have a SQL database and want APIs and an admin on top of it
You need a less common database such as SQL Server, Oracle or CockroachDB
You want user-written extensions to run in a separate V8 isolate

Pick Strapi if…

You want content models as JSON files versioned in Git
You want editors to build content types visually without writing migrations
You want a plugin system that can add models, GraphQL types and admin tabs

Pick Payload CMS if…

Your site is a Next.js app and you want the CMS in the same process
You want MongoDB or Cloudflare D1 as an option alongside Postgres and SQLite
You prefer the MIT license

Side by side

Attribute	Directus	Strapi	Payload CMS
Written in	TypeScript Vue	TypeScript JavaScript Handlebars	TypeScriptCSSJavaScript
License	NOASSERTION	NOASSERTION	MIT
Frontend	Vue Vite PiniaVue Router	React TypeScript	React Next.js
Backend & APIs	Express Knex.js GraphQLisolated-vm	Node.js Koa GraphQL	TypeScript Next.js GraphQL
Data & persistence	PostgreSQLMySQL / MariaDB / SQLite / MSSQL / Oracle / CockroachDBRedis	PostgreSQL SQLite MySQL	MongoDB PostgreSQL SQLite Drizzle
Infrastructure & deploy	DockerStorage drivers (S3, GCS, Azure, Cloudinary, Supabase, local)pm2	Docker	pnpm Turborepo Vercel
Key decisions	The database layer is Knex-based, not a heavier ORM Studio, API, and SDK are separate pnpm workspace packages that compose into one server Extensions execute inside an isolated-vm sandbox, not the main process	Modular plugin architecture with dynamic schema composition Database abstraction via Knex query builder layer Declarative Content-Type Schema Builder	Four database adapters share one export contract Payload installs into an existing Next.js /app folder, not a standalone server GraphQL ships as an optional package, not a core dependency
Audited	5cf557b · 2026-09-17	3cd7dba · 2026-09-17	9a2cdcb · 2026-09-17

How they differ

Where the content model lives

Directus reads the connected database and generates REST and GraphQL endpoints from its schema, so the database is the source of truth. Strapi keeps content types as schema.json files and creates tables, foreign keys and join tables to match them. Payload is configured in code inside a Next.js project and talks to the database through an adapter.

Server and admin

Directus runs an Express API next to a Vue 3 Studio built with Vite and Pinia; user extensions run in an isolated-vm sandbox, and Redis handles schema-cache invalidation across instances. Strapi runs on Koa with a React admin that includes a visual Content-Type Builder and a media library. Payload’s React admin, REST API and Local API are wired into Next.js route handlers by packages/next.

Hosting

Directus ships a two-stage Alpine image that runs as a non-root user under pm2 and defaults to SQLite until you point it at another database. Strapi is built with yarn build and run behind a reverse proxy against an external PostgreSQL or MySQL. Payload deploys like a normal Next.js app and offers host-specific starters for Vercel Postgres, Vercel with MongoDB and Cloudflare D1.

Architecture diagrams

Directus Open SVG

Strapi Open SVG

Payload CMS Open SVG

Frequently asked questions

Which databases do Directus, Strapi and Payload support?

Directus uses Knex with drivers for PostgreSQL, MySQL, MariaDB, SQLite, SQL Server, Oracle and CockroachDB; its Docker image defaults to SQLite. Strapi uses its own Knex-based layer for PostgreSQL, MySQL, MariaDB and SQLite. Payload uses adapters: MongoDB through Mongoose, and PostgreSQL, SQLite, Vercel Postgres and Cloudflare D1 through a shared Drizzle layer.

Does Payload need its own server?

No. Payload installs into an existing Next.js app: its admin UI, REST API and Local API run as Next.js route handlers in the same process, so it deploys like any Next.js project.

Is GraphQL built in?

Directus derives a GraphQL schema from the same data model as its REST API, with subscriptions over WebSockets. Strapi generates REST endpoints for each content type and adds GraphQL through an optional plugin. Payload keeps GraphQL in an optional package, so REST-only projects do not pull it in.

More architecture comparisons

View all