Databases
Xema provides org-managed databases — fully-isolated, platform-managed relational databases provisioned and managed by the platform on behalf of each org. Biomes and apps get structured, schema-isolated access to persistent storage without managing infrastructure themselves.
Databases are provisioned through org-database-pool-api, which allocates databases in a fleet of devops-provided database clusters. Each org gets its own database; each biome and app gets its own schema within that database.
Quick Links
| Page | What it covers |
|---|---|
| Concepts | DB-per-org naming, schema-per-purpose, DbPool model, isolation guarantees |
| Provisioning | ProvisionDatabase workflow, naming conventions, capability gates |
| Migrations | Migration runners, running migrations, Xema Workflow Runtime orchestration |
| Connections | Connection brokering, short-lived credentials, roles |
| App Studio Dev/Prod | Dev and prod schemas, Promote-to-prod workflow |
Getting Started
- Concepts — understand the isolation model before provisioning.
- Provisioning — provision your first org or biome database.
- Connections — connect your biome or app to the database.
- Migrations — run schema migrations safely.
FAQ
Q: Do I manage the database server? A: No. The platform provisions databases in a devops-managed database cluster. You interact with your schema only, not the server or cluster configuration.
Q: Can two biomes access the same schema? A: By default, each biome gets an isolated schema. Cross-biome schema access requires an explicit capability grant.
Q: Is a specific migration framework required? A: Two runners ship today: one applies the migration files a biome ships inside its bundle; the other applies a platform-generated typed schema-change plan. See Migrations.