Fóir as an alternative to Contentful
Both are hosted, both model content as structured entries. The differences are where personalisation is decided, and how much of the application around the content you still stand up yourself.
Side by side
| Capability | Fóir | Contentful |
|---|---|---|
| Price | £0.99, £29 or £99 a month | $300 a month for Lite, $850 per extra Space, Enterprise on request |
| Records | 25,000 on Entry, 500,000 on Starter, 2,000,000 on Pro | 10,000 in the Space every plan includes, 50,000 in the $850 Lite Space |
| Content management | Standard | Standard |
| Personalisation | Built in, resolved per request | Built in, resolved in your app |
| Hosted auth | Sign-in, roles and tokens included | Editors only, not your users |
| Backend beyond content | Operations, hooks, schedules, secrets | Functions and app framework |
| API | Typed GraphQL, generated | REST and GraphQL, with rate limits |
| Agent access | Content and control plane | Content over MCP |
| Many sites | Organisations on one schema | A space each, schema copied |
| Data ownership | Postgres export, access rules included | Export as JSON entries |
Price
- Fóir
- £0.99, £29 or £99 a month
- Contentful
- $300 a month for Lite, $850 per extra Space, Enterprise on request
Records
- Fóir
- 25,000 on Entry, 500,000 on Starter, 2,000,000 on Pro
- Contentful
- 10,000 in the Space every plan includes, 50,000 in the $850 Lite Space
Content management
- Fóir
- Standard
- Contentful
- Standard
Personalisation
- Fóir
- Built in, resolved per request
- Contentful
- Built in, resolved in your app
Hosted auth
- Fóir
- Sign-in, roles and tokens included
- Contentful
- Editors only, not your users
Backend beyond content
- Fóir
- Operations, hooks, schedules, secrets
- Contentful
- Functions and app framework
API
- Fóir
- Typed GraphQL, generated
- Contentful
- REST and GraphQL, with rate limits
Agent access
- Fóir
- Content and control plane
- Contentful
- Content over MCP
Many sites
- Fóir
- Organisations on one schema
- Contentful
- A space each, schema copied
Data ownership
- Fóir
- Postgres export, access rules included
- Contentful
- Export as JSON entries
Contentful's behaviour is taken from its published documentation, current at August 2026. Where we say a thing is absent we mean absent from the product and its official plugins, not impossible to build. Corrections are welcome and we will make them.
Personalisation decided before it reaches the client
Contentful personalises through an SDK in your application: you identify the visitor and the front end picks the variant. Every consumer repeats that work, and a native app and a website can disagree.
Fóir resolves it server-side and returns the content already chosen for the request, so every client gets the same answer.
Sign in the people who use what you build
Contentful authenticates editors. Your own users are a separate service you run or buy, and a second place identities live.
Fóir signs them in on your domain, with roles and refresh, and the content rules already know who is asking.
One schema, not a copy per space
Keeping several Contentful spaces aligned means copying content types between them and hoping they stay in step.
Fóir defines a model once on the project and every organisation inside it inherits that definition, so there is no copy to keep in step.
Everything around the content
Scheduled work, outbound calls to the systems you integrate with and somewhere safe to keep their credentials are all assembled separately.
In Fóir they are part of the same project as the content they act on.
What you would otherwise assemble
A content API is the smallest part of what an application needs. These come with it.
Publishing
Drafts, full version history, revert, publish at a future time, and bulk rollouts when a batch has to go live together.
Model behaviour
Per model: versioning, publishing, variants, or none of them. Records can be plain data, owned by a customer, or public.
Permissions
Roles for your team and roles for your customers, plus per-record visibility and grants to a named person.
Hosted sign-in
Password, one-time code, and social or OIDC providers, on your own domain, with tokens and refresh handled for you.
Media and assets
An asset library with upload, transformations and responsive renditions, and the same access rules over files as records.
API keys
Each key reaches exactly the models and operations you allow, against a schema generated for that project.
Automation
Cron schedules, lifecycle hooks on publish and change, outbound operations, and a vault for the keys they need.
Notifications
Transactional email and push to web, iOS and Android, from the same events your content already emits.
Notes and tasks
Comments anchored to the record they concern rather than to a page, assignable to whoever has to act on them.
Ask Fóir
An assistant that works your content through the same tools and permissions your team has, staging its edits for review.
Work that carries on without you
Assign a task to Fóir and it works while you are away, coming back on the note when it needs an answer or is done.
Extensions
Install apps that add your own tools to the admin, beside the content they operate on.
Search and vectors
Full-text search, and embeddings generated for your records so you can retrieve by meaning rather than by keyword.
Geo
Store coordinates on any model and query by proximity: what is near this point, ordered by distance.
See it against your own models
Create a project, define a model, and read it back over the API.