Fóir as an alternative to Convex
Convex is a reactive backend for developers writing TypeScript. Fóir is a backend the developers and the content team share, with the editing surface already built.
Side by side
| Capability | Fóir | Convex |
|---|---|---|
| Price | £0.99, £29 or £99 a month | $25 per member a month, then usage on top |
| Typed access | Generated GraphQL schema | TypeScript functions you write |
| Content modelling | Models, fields, relations | Documents and validators |
| Editor experience | Built for non-developers | A data dashboard |
| Publishing | Drafts, versions, scheduling | Build it yourself |
| Localisation | Per-field translations | Build it yourself |
| Personalisation | Built in, resolved per request | Build it yourself |
| Media | Library, transformations, renditions | File storage |
| Hosted auth | Included, on your domain | Convex Auth in beta, or a third party |
| Backend beyond content | Operations, hooks, schedules, secrets | Functions, crons, actions |
| Data ownership | Postgres export, access rules included | Export your documents |
Price
- Fóir
- £0.99, £29 or £99 a month
- Convex
- $25 per member a month, then usage on top
Typed access
- Fóir
- Generated GraphQL schema
- Convex
- TypeScript functions you write
Content modelling
- Fóir
- Models, fields, relations
- Convex
- Documents and validators
Editor experience
- Fóir
- Built for non-developers
- Convex
- A data dashboard
Publishing
- Fóir
- Drafts, versions, scheduling
- Convex
- Build it yourself
Localisation
- Fóir
- Per-field translations
- Convex
- Build it yourself
Personalisation
- Fóir
- Built in, resolved per request
- Convex
- Build it yourself
Media
- Fóir
- Library, transformations, renditions
- Convex
- File storage
Hosted auth
- Fóir
- Included, on your domain
- Convex
- Convex Auth in beta, or a third party
Backend beyond content
- Fóir
- Operations, hooks, schedules, secrets
- Convex
- Functions, crons, actions
Data ownership
- Fóir
- Postgres export, access rules included
- Convex
- Export your documents
Convex'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.
A backend two audiences can share
Convex is a pleasure if the only people touching data write TypeScript. The moment someone else has to change a headline, that goes through a developer or through an admin panel a developer builds and then owns.
Fóir gives the content team a real editing surface from the same models your code reads, so neither side is waiting on the other.
The publishing layer already exists
Drafts, version history, revert, scheduled publishing and bulk rollouts are what content work is actually made of, and on Convex each of them is something you design and maintain.
They are properties you turn on per model here.
Sign-in that is already finished
Convex Auth handles passwords, one-time codes and social sign-in, and its own documentation calls it beta and lighter on features than the third-party providers it points you at for production.
Fóir signs your users in on your own domain, with roles, refresh and the content rules already aware of who is asking.
Content that resolves per request
A locale or an audience is not a field you fetch and branch on in every client.
Fóir resolves it server-side, so a website, a native app and an agent all get the same answer for the same request.
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.