Fóir compared
Who Fóir gets weighed against, and what actually differs. Every claim comes from the other side's published documentation, and we correct them when they change.
Payload
Config-as-code, self-hosted, native to Next.js. The comparison is where each of us enforces isolation, and how much of the backend arrives with the content.
Sanity
Hosted, editor-first, queried with GROQ. The comparison is sign-in for your own users, and how much of the application around the content you still assemble.
Supabase
Postgres, auth and storage, the same substrate we run on. The comparison is the content layer above it: modelling, drafts, and an interface a marketer can use.
Convex
A reactive backend for TypeScript. The comparison is whether the people who write the content can work in it without a developer.
WordPress
The page engine with an application bolted on. The comparison is structured content, a generated API, and having nothing to patch.
EmDash
Open source, and built into an Astro site you host. The comparison is what you run and patch, and which front ends can read the content.
Contentful
Hosted and structured, with personalisation of its own. The comparison is where that personalisation resolves, and who signs in your users.
Strapi
The open-source CMS you run yourself. The comparison is what you operate, and what arrives already built.
Directus
A studio and an API over a database you bring. The closest of these, and the comparison is whether content or the table came first.
Firebase
A strong application backend with no content layer. The comparison is where the person who writes the copy is supposed to work.
Or just try it
Create a project, define a model, and read it back over the API.