Apiome and Api-DB
Api-DB stores the data for the tables defined by your Apiome project.
Schema in, records out
- Shape it in Apiome. Define tables, fields, relations and constraints in the Apiome schema designer — the same model that drives your APIs.
- Api-DB provisions it. Every table you publish gets durable, versioned storage. There are no migrations to hand-write and no drift between schema and data.
- Your records, served. Read and write records through the APIs Apiome generates, validated against the schema on every request.
Principles
| Principle | What it means |
|---|---|
| Schema-shaped records | Every record is validated against the Apiome table that defines it. |
| Versioned by design | Schema versions and data evolve together; a published change never strands existing records. |
| API-first access | Data is reached through the APIs your Apiome project describes, not through drivers or connection strings. |
| Tenant isolation | Multi-tenant from the ground up, governed by Apiome workspaces and roles. |