Fóir for developers
You define the models. The API, the admin, the access rules and the types come out of them, and the part you would rather not operate is not yours to operate.
Types you did not hand-write
The failure mode of a content API is a field that quietly changed shape and a client that finds out in production.
Fóir generates a typed GraphQL schema from your models. Change a model, regenerate, and the compiler tells you what broke before the deploy does.
Access rules that hold when you forget
Authorisation that lives in application code is correct until a code path skips it, and the failure is silent and total.
In Fóir the rules you write are enforced underneath the application. A read that forgets a check comes back empty rather than complete, and somewhere new to store data cannot ship without rules covering it.
Config you can commit
Click-configured environments drift, and the drift is only visible when one of them breaks.
Models, keys, hooks, providers and design tokens can live in a file you commit and push, so environments match because they came from the same source.
Agents inside the same rules as your team
Pointing an agent at your content usually means a key with more reach than you would give a person.
Fóir's MCP surface covers content and the control plane, inside the caller's own permissions, and destructive calls are held for approval with a gate that fails closed.
The parts you would otherwise stand up
Already running, and yours to leave with.
Typed SDK and CLI
A client for your application and a CLI for everything you would rather script than click.
Hosted sign-in
Your end users, with password, one-time code, social and OIDC, on your own domain.
Operations
Call the systems you integrate with, in the background or inline, with retries and a record of what happened.
Event hooks
Fire on publish, change or delete, with delivery tracking and a dead-letter queue when a target is down.
Schedules
Cron against your own content, in the same place as everything else.
Secrets
A vault for the credentials those calls need, referenced by name.
Search and vectors
Full-text, embeddings for retrieval by meaning, and proximity search over coordinates.
Postgres export
One command produces a database you own, with your access rules translated onto it.
Define one model and read it back
Create a project, push a model, and query it over a typed API in the same sitting.