FAQ
The objections, answered before they're raised.
2 alternatives. Each is a starting point — copy one and rewrite the content.
Collapsed answers, for a long list.
Questions we get asked first
If yours isn't here, the answer is usually one email away.
Who owns the database?
You do. Acme connects to a Postgres instance you control and never copies it. Point the connection string somewhere else and the API follows.
What happens to my existing API?
Nothing, until you turn it off. Most teams run both for a release or two, compare responses, and then delete the old service once the diff is empty.
Is there a request limit?
Plans include a monthly allowance and then bill per million. There is no hard cut-off — traffic is never dropped because of billing.
Where does it run?
Reads are served from the closest of eighteen regions. Writes go to the primary you chose when you linked the database.
How do I leave?
Delete the project. There is nothing to export, because everything of yours was already in your own database.
Usually answered same day.
Everything open, for a short one.
Frequently asked
Everything open, because the list is short enough to read.
- Do I need to change my schema?
- No. Acme reads what is already there, including the constraints and the foreign keys it uses to infer relations.
- Does it support GraphQL?
- Yes, over the same policies as REST. Both are generated from one schema, so neither can drift from the other.
- How are secrets handled?
- Connection strings are encrypted at rest with a per-project key and are never written to logs or build output.
- Can I self-host?
- The runtime ships as a single container on the Enterprise plan. The control plane stays with us.
- What about migrations?
- Run them however you run them today. The API picks the new shape up on the next introspection, within a second.
- Is there a free tier?
- One project, ten thousand requests a month, no card. It's the same runtime, just smaller.