Features
What the product does, once the hero has your attention.
3 alternatives. Each is a starting point — copy one and rewrite the content.
Six short capabilities, three to a row.
Everything the API layer needed anyway
Six things you would have built yourself in the first month, already built and already tested.
Typed endpoints
Every route is generated from the schema, so the types and the database never drift apart.
Row-level rules
Write the policy once. It runs on every read and every write, including the ones you forgot.
Instant rollback
Every deploy keeps its predecessor warm. Reverting is one command and takes under a second.
Edge cache
Reads are served from the nearest region and invalidated by the write that made them stale.
Audit log
Who changed what, when, and from where — retained for a year and exportable as JSON.
No lock-in
It's your Postgres. Point the connection string elsewhere and everything keeps working.
One feature at a time, image and copy swapping sides.
It reads the database you already have
Point Acme at a connection string and it walks the schema — tables, columns, foreign keys, constraints — and serves the API that describes it. There is no separate model to keep in sync, because there is no separate model.
acme link postgres://… ✓ 14 tables ✓ 38 endpoints ✓ 6 relations inferred
Access rules live next to the data
A policy is a single expression evaluated per row. It applies the same way to a REST call, a GraphQL query and a direct SQL session, so there is no path around it and nothing to remember to apply twice.
policy "own rows" on orders for select using (customer_id = auth.uid())
A dense list for buyers scanning for one specific thing.
What you get, without asking
The list procurement wants, on the page rather than in a PDF you have to request.
- Unlimited environments
- Preview deploys per branch
- Point-in-time restore, 30 days
- SOC 2 Type II report
- SSO via SAML and OIDC
- 99.9% uptime SLA
- Log drains to any sink
- Terraform provider