Fóir as an alternative to Supabase
This is not a fight about the database. Fóir runs on Postgres too. The question is how much you assemble on top of it before an editor can change a headline.
Side by side
| Capability | Fóir | Supabase |
|---|---|---|
| Price | £0.99, £29 or £99 a month | From $25 a month, plus compute for each extra project |
| Database | Postgres | Postgres |
| Row-level rules | Generated from your model | SQL policies you write |
| Content modelling | Models, fields, relations | Tables and columns |
| Editor experience | Built for non-developers | A table editor |
| Publishing | Drafts, versions, scheduling | Build it yourself |
| Localisation | Per-field translations | Build it yourself |
| Personalisation | Built in, resolved per request | Build it yourself |
| API | Typed GraphQL from your models | REST, GraphQL and SQL from your tables |
| Media | Library, transformations, renditions | Object storage, transforms on paid plans |
| Hosted auth | Included | Included |
Price
- Fóir
- £0.99, £29 or £99 a month
- Supabase
- From $25 a month, plus compute for each extra project
Database
- Fóir
- Postgres
- Supabase
- Postgres
Row-level rules
- Fóir
- Generated from your model
- Supabase
- SQL policies you write
Content modelling
- Fóir
- Models, fields, relations
- Supabase
- Tables and columns
Editor experience
- Fóir
- Built for non-developers
- Supabase
- A table editor
Publishing
- Fóir
- Drafts, versions, scheduling
- Supabase
- Build it yourself
Localisation
- Fóir
- Per-field translations
- Supabase
- Build it yourself
Personalisation
- Fóir
- Built in, resolved per request
- Supabase
- Build it yourself
API
- Fóir
- Typed GraphQL from your models
- Supabase
- REST, GraphQL and SQL from your tables
Media
- Fóir
- Library, transformations, renditions
- Supabase
- Object storage, transforms on paid plans
Hosted auth
- Fóir
- Included
- Supabase
- Included
Supabase'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.
The same substrate, most of the way further along
Supabase hands you Postgres, auth, storage and a place to put functions. That is a genuinely good foundation and it is a foundation: content modelling, drafts, versions, scheduling, localisation and an interface a marketer will actually use are all yours to build and then maintain.
Fóir starts from the same substrate and ships that layer. You define models; the API, the admin and the rules come out of them.
Rules you generate rather than write
On Supabase your isolation is the row-level policies you author in SQL, and they are correct until someone adds a table in a hurry.
In Fóir those rules come from the model. A project that gains somewhere new to store data cannot ship without rules covering it, because the check is generated rather than remembered.
An interface for the people who write the words
A table editor is a developer's tool. Handing it to the person responsible for the homepage is how content ends up going through an engineer.
Fóir's admin is built for them: real fields, drafts they can preview, a publish button, and comments on the record itself.
You can still leave with everything
The usual reason to pick a database platform is that the data stays yours.
It does here too. One command produces a Postgres database you own, a table per model, references as real foreign keys, and your access rules translated onto it.
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.