PostgreSQL
Choose it for concurrent writers, richer SQL, PostgreSQL types and extensions, and applications expected to grow.
- Guest
- 256MiB Firecracker
- Free / Plus / Pro
- 1 / 3 / 10 databases
Limited invite-only technical preview
A Postgres database that brings its operating context with it.
Start with real Postgres plus the guide, documents, and skills that explain how to use it. Choose a portable SQLite workspace when the workload is smaller and mostly single-writer. Share either engine with precise roles, and let it sleep without leaving recent mutations stranded on one machine.
For agent power users, researchers, and operators · Public signup remains closed
live agent sessionconnected
Agentresearch workflow
market-researchPostgres · revision 12
DATABASE.mdpurpose · schema · rules
docs/sources.mdcitations · freshness
skills/reconcile/SKILL.mdrepeatable workflow
Two engines, one product
Postgres by default. SQLite when it fits.
Engine choice is explicit and immutable. Identity, context, collaboration, adapters, sleep, durability, and deletion stay on the same OnDemandDB plane.
SQLite workspace
Choose it for agent scratchpads, research tables, prototypes, compact catalogs, and a verified native file you can export.
- Guest
- 96MiB Firecracker
- Free / Plus / Pro
- 3 / 10 / 15 workspaces
One database, three product pillars
The data, its meaning, and the people working with it.
Every adapter reaches one control plane. Authority and durability do not change because an agent arrived through a different client.
01 · Context
Stop rediscovering the database.
Version DATABASE.md, supporting documents, and portable Markdown skills beside the data. Retrieve them explicitly, with hashes, ETags, and provenance.
Explore context →02 · CollaborationShare work without sharing control.
Owners, architects, writers, and readers get fixed capabilities enforced at the control plane and inside the selected engine.
See the role model →03 · DurabilitySleep compute, keep protecting writes.
Encrypted engine bases and WAL flow to R2 while a database is hot. The execution boundary blocks mutations if verified protection falls too far behind.
Follow the bytes →Agent-shaped work
From a prompt to governed state.
An agent asks for context, works within its role, and writes through a bounded SQL transaction. The database keeps the shared operating memory for the next agent.
Connect the hosted MCP endpoint →agent session
› Continue the market-research database
✓ get_database_context revision 12 · ETag verified
✓ run_sql writer role · 12 rows inserted
✓ durability protected in R2 · lag 41s
The schema rules were already there. I followed them.Shipped technical preview
Specific claims, visible limits.
One Firecracker VM per database
PostgreSQL and SQLite use separate measured guest profiles.
SQL-idle sleep
The next SQL call restores the selected engine. Context reads do not wake it.
Maximum unprotected-write interval
When verified R2 protection lags, the engine keeps reads open and rejects mutations.
Encrypted recovery history
Verified bases and a contiguous WAL chain support isolated restore drills.
The boundary: today this runs on one Helsinki host. It is not HA, automatic failover, synchronous commit, or zero RPO.
Bring one database or workspace your agents will keep using.
Apply for a manually reviewed place. Free includes context, collaboration, and the same durability path as the paid plans.
Apply for preview →