Atrium platform docs
Atrium developer documentation
Build, deploy, secure, and publish an Atrium app with subscriptions and workspace integration.
Build an app on Atrium
An Atrium app has an atrium.yaml manifest, one or more services, and its own user interface.
Atrium provides deployment, workspace access, subscriptions, and marketplace discovery. Your app
owns its data authorization, workflows, and customer experience.
Start with Quickstart to generate a project, run it locally, and deploy. Choose a Next.js frontend, a frontend with FastAPI, or a frontend with FastAPI and Hasura.
Guides by task
| Task | Guide |
|---|---|
| Describe services and configuration | Manifest schema |
| Run a development session | Local development |
| Protect routes and use service URLs | App access |
| Manage schema and metadata changes | Databases and migrations |
| Define Free and paid plans | Manifest billing |
| Enforce features and usage limits | Billing and entitlements |
| Deploy source and follow progress | Deployments |
| Publish the marketplace listing | Studio |
| Test customer enrollment and launch | Workspace apps |
| Show work across apps in Home | AgentCase contract |
| Collaborate in a workspace | Team access |
For automation, use Authentication, the developer API reference, and the CLI reference. Otto illustrates a deployed app with frontend, backend, and Hasura services.
What you configure
Keep source, service paths, health checks, access rules, and billing declarations in your repository. Use returned URLs and runtime environment values for integrations. Credentials, resolved deployment state, and reserved configuration do not belong in the manifest.
Studio saves listing changes separately from application deployment. See Manifest lifecycle before combining Studio edits with manifest updates.
Availability
The CLI examples target published stable version 0.1.16, verified September 22, 2026.
Check atrium --version and command help when comparing examples with your installation.
- Hasura services require database and service setup before deployment.
- Isolated development databases require additional platform setup; do not assume they are enabled.
- One-time credit purchase fulfillment has unresolved issues and is not recommended for production use.
- Reverse tunnels and newer behavior found only in local CLI builds are not released features.
Each guide distinguishes supported workflows from these prerequisites and limits.