# Docs

- Get Started
  - [What is concile?](/docs/get-started/what-is-concile): An open-source reactive backend you host yourself.
  - [Quickstart](/docs/get-started/quickstart): Get a concile backend running and watch it update live, in a few minutes.
  - [Tutorial](/docs/get-started/tutorial): Build a small reactive chat app, end to end, with a real React UI.
  - [How it works](/docs/get-started/how-it-works): The reactive model: how concile knows which queries to refresh when data changes.
  - [Performance](/docs/get-started/performance): How fast concile is, measured under matched conditions with every caveat stated plainly.

- **Build**
- Core Concepts
  - [Schema & tables](/docs/core-concepts/schema-and-tables): How you describe your data, tables, documents, validators, and indexes.
  - [Queries](/docs/core-concepts/queries): How you read data, and why a query's read set is the heart of reactivity.
  - [Mutations](/docs/core-concepts/mutations): The only writers. Every mutation runs as one serializable transaction.
  - [Actions](/docs/core-concepts/actions): Fetch, timers, and randomness: side effects that run outside the transaction.
  - [Reactivity](/docs/core-concepts/reactivity): What makes a subscribed query re-run, which query shapes get the cheapest live updates, and what happens on reconnect.
  - [HTTP and webhooks](/docs/core-concepts/http-and-webhooks): Expose a plain HTTP endpoint for webhooks and REST calls with httpAction and a conventional http.ts router.
  - [File storage](/docs/core-concepts/file-storage): The _storage table, ctx.storage, and why uploads are a two-phase process.
  - [CLI](/docs/core-concepts/cli): Every concile command and its flags.
- Client
  - [Client SDK](/docs/client/client-sdk): useQuery, useMutation, useAction.
  - [Optimistic updates](/docs/client/optimistic-updates): Instant local UI with exact rollback.
  - [Offline sync](/docs/client/offline-sync): The durable offline outbox: queue, drain, receipts, and everything built on top of them.
- Components
  - [Components](/docs/components/overview): Opt-in capabilities composed in concile.config.ts.
  - [Auth](/docs/components/auth): Sessions, email, OAuth, MFA, and passkeys.
  - [Authorization](/docs/components/authorization): RBAC, ReBAC, and row policies.
  - [Notifications](/docs/components/notifications): Email, SMS, in-app, and push.
  - [Scheduling](/docs/components/scheduling): runAfter, runAt, and cron jobs.
  - [Workflows](/docs/components/workflows): Durable multi-step orchestration.
  - [Triggers](/docs/components/triggers): React to table changes.

- **Deploy & operate**
- Deploy & Operate
  - [Local development](/docs/deploy/local-dev): concile dev's hot-reload server and the built-in dashboard.
  - [Vite plugin](/docs/deploy/vite-plugin): Run your frontend and the concile backend with one vite command, on one origin.
  - [Self-hosting with Docker](/docs/deploy/self-hosting): concile serve and docker compose up, the baseline production self-host path.
  - [Postgres](/docs/deploy/postgres): Point concile at a Postgres database instead of SQLite, with no code changes.
  - [Deploy and build](/docs/deploy/deploy-and-build): Live hot-swap onto a running server with concile deploy, or compile a self-contained binary with concile build.
  - [Cloudflare](/docs/deploy/cloudflare): concile deploy --target cloudflare provisions a Durable-Object-native host via wrangler.
  - [Scaling](/docs/deploy/scaling): The tiered model - single-node free forever, plus a Postgres fleet and an object-storage substrate for multi-node write scale-out under a commercial entitlement.

- **Reference**
- Reference
  - [Testing](/docs/reference/testing): Test functions against the real engine with @concile/test.
  - [Migrate from Convex](/docs/reference/migrate-from-convex): Use concile migrate to port a Convex project's imports, then work through its report.
  - [Configuration](/docs/reference/configuration): The full v.* validator catalog, concile.config.ts, crons.ts, http.ts, and every environment variable the engine reads.
  - [FAQ](/docs/reference/faq): Honest answers about what concile is, what it isn't, and what isn't built yet.
  - [Glossary](/docs/reference/glossary): Plain-language definitions of the terms used across the concile docs.