# omg.dev platform docs

The handbook for the omg.dev platform: request flow, deploys,
auth, and the SDK for building DB-backed apps. Each page below is
a public URL on this site; fetch /llms-full.txt for the full plain-text dump.

## Pages

- [Welcome](https://docs.omg.dev/docs) — What omg is, how it fits together, and how to run it yourself.
- [Architecture](https://docs.omg.dev/docs/architecture) — Request path from browser to Firecracker microVM and back.
- [Auth](https://docs.omg.dev/docs/auth) — JWT principals, JWKS rotation, on-behalf-of pattern.
- [Brand — visual + voice reference](https://docs.omg.dev/docs/brand) — Canonical colors, type, logo, and voice for omg.dev. Where the tokens live, when to deviate, when not to.
- [Deploy flow](https://docs.omg.dev/docs/deploy-flow) — From POST /v1/deploys to :slug.apps.omg.dev serving 200.
- [MCP — drive omg from Claude Code](https://docs.omg.dev/docs/mcp) — OAuth-authenticated MCP server at mcp.omg.dev. Install, tool surface, how the auth dance works.
- [Runbooks](https://docs.omg.dev/docs/runbooks) — When something is on fire, start here.
- [Sandbox API](https://docs.omg.dev/docs/sandbox-api) — Create and control isolated Firecracker sandboxes over HTTP with an API key.
- [Authentication](https://docs.omg.dev/docs/sandbox-api/authentication) — Create an API key in the dashboard and send it as a Bearer token.
- [Quickstart](https://docs.omg.dev/docs/sandbox-api/quickstart) — Create a sandbox from your own app — key, create, poll, connect.
- [Reference](https://docs.omg.dev/docs/sandbox-api/reference) — Every Sandbox API endpoint, with request/response shapes and examples.
- [Templates](https://docs.omg.dev/docs/sandbox-api/templates) — Start from a baked snapshot, pick a coding-agent preset, or bake your own template with the typed SDK baker.
- [Webhooks](https://docs.omg.dev/docs/sandbox-api/webhooks) — Signed lifecycle events the platform emits — wire format, signature verification, and what's self-serve today.
- [SDK overview](https://docs.omg.dev/docs/sdk) — Building DB-backed apps with @omg-dev/schema, @omg-dev/sdk, and @omg-dev/server.
- [AI & agents](https://docs.omg.dev/docs/sdk/ai) — Zero-config AI SDK access from any Vibes app. No keys, no baseURL, automatic per-end-user attribution.
- [Multi-user auth](https://docs.omg.dev/docs/sdk/auth) — Per-user data, login UI, and JWT handling for deployed Vibes apps — no extra config.
- [Schema reference](https://docs.omg.dev/docs/sdk/schema) — defineSchema, collection, fields — the contract that decides static vs runtime deploy.
- [useQuery reference](https://docs.omg.dev/docs/sdk/use-collection) — The exact return type, REST contract, WebSocket realtime behaviour, and reconnect strategy of @omg-dev/sdk's useQuery hook (and the deprecated useCollection alias).
- [Service tokens](https://docs.omg.dev/docs/service-tokens) — Long-lived svc:* JWTs and where they live.
- [Static deploys](https://docs.omg.dev/docs/static-deploys) — When the runtime VM is skipped entirely.