Introduction
What Authoric is, where to start for what you want to build, and how these docs are laid out.
Authoric is a backend you build multi-tenant products on: a database with a REST API for every table, sign-in for your users, file storage, server-side handlers, scheduled jobs, email, billing, and AI agents. Every caller, whether a person, an API key, a scheduled job or an agent, goes through the same policy engine and the same audit log. The rules live in the server that holds the data, not in a prompt, so an agent can only do what its roles grant, and a limit such as "may refund up to $5,000" is enforced as policy rather than requested in its instructions.
Start here
Pick the goal closest to yours. Each card opens the first page to read.
Build an app's backend
Create an app, add a table, grant access, sign a user in, and read rows over the API.
Sign your users in
Password, magic links, email codes, Google and GitHub, sessions and 2FA for your app's users.
Write handlers and jobs
Server-side code with a governed SDK, run on a request, on a schedule, or as an agent's tool.
Give an AI agent governed access
An agent whose tools come from its roles, with approvals for the steps you choose.
Call the REST API or MCP
Base URL, tokens and API keys, uid addressing, paging, errors and rate limits.
Decide who can do what
Roles, policies and conditions: the one access model every caller shares.
New to the platform? Read Core concepts first. It is short, and every other page assumes it.
Map of the docs
| Section | What it covers |
|---|---|
| Getting started | Quickstart, Core concepts, The governance model, Glossary, Errors and status codes |
| Build | Auth, Organizations, Database, Storage, Handlers, Scheduled jobs, Email |
| Govern | Agents & AI, Access control |
| Operate | Billing |
| Reference | API reference, Error codes, Handler SDK reference |
Guides follow the same order: what a feature is, how you set it up in the console, then how
your application uses it at runtime. Code samples come in cURL, JavaScript (fetch) and Python
(requests); pick one once and every page follows.
The API reference and the error-code catalog are generated from the API's own contract and error registry, so they describe what the server actually accepts and returns.