Apiome Database:
Your Data Shaped by Apiome
Api-DB is the Apiome Database service. Design your tables in Apiome — Api-DB stores every record, shaped exactly the way your schema says it should be.
Apiome Database Solution, launching in 2027.
table customers
- idpkuuid
- emailuniquestring
- planenum
- created_attimestamp
- 9f2c…e1ada@example.compro
- 4b7a…03grace@example.orgteam
- c81d…9aalan@example.netfree
- e05f…7ckat@example.compro
How it works
One schema. Zero drift.
Apiome defines the tables. Api-DB stores the data for them. The two are designed as one system.
- 01
Shape it in Apiome
Define tables, fields, relations and constraints in the Apiome schema designer — the same model that drives your APIs.
- 02
Api-DB provisions it
Every table you publish gets durable, versioned storage. No migrations to hand-write, no drift between schema and data.
- 03
Your records, served
Read and write records through the APIs Apiome generates, validated against the schema on every request.
Features
The data layer for all of Apiome
Every Apiome feature that stores data stores it in Api-DB.
Schema-shaped records
Every record is validated against the Apiome table that defines it — types, keys and constraints included.
Versioned by design
Schema versions and data evolve together, so a published change never strands the records behind it.
API-first access
No drivers, no connection strings. Your data is reached through the same APIs your Apiome project already describes.
Tenant isolation
Multi-tenant from the ground up, with access governed by the same workspaces and roles you use in Apiome.
Built for every feature
Apiome has a very large and growing feature set. Api-DB is the single store behind all of it.
Scale without ceremony
From a prototype's first row to production volumes, on storage chosen for durability and throughput.
Under the hood
Choosing the right engine
We're researching the storage engine behind Api-DB now, benchmarking candidates for durability, throughput and cost before we commit.
Rust-native engine
A memory-safe, embeddable engine with predictable latency and low operating cost.
Object-storage (S3) backed
Durable, near-infinitely scalable storage with compute separated from data.
Hybrid architectures
A fast transactional tier in front of an object-storage foundation — the best of both.
Apiome Database Solution,
launching in 2027.
Sign up for early access.