Store product data inside agent workspaces.
Let humans or agents create, seed, bind, and manage databases for web apps, functions, auth flows, agent runtimes, and operational product data.
Start now
Create databases, collections, and documents for product state, records, queues, and app data.
Insert, list, read, update, and delete JSON documents from SDK scripts, apps, functions, or agents.
Bind databases to web apps, functions, auth modules, secrets, and agent runtimes in one workspace.
Inspect analytics, collections, documents, and bindings so data stays visible as products evolve.
Pricing
Databases are the structured product data surface for apps, functions, auth flows, and agent workflows.
| Database surface | No standalone CT / live minute runtime rate The database itself is typically paired with other ACP compute or deployed surfaces. |
|---|---|
| Connected compute | Normal resource usage applies Computers, web apps, functions, auth modules, and runtimes keep their own pricing model. |
| Data operations | Driven by connected resources Reads and writes are usually generated by apps, functions, SDK scripts, or agents using the database. |
SDK functionality
The JavaScript and Python SDKs expose database lifecycle, collections, documents, analytics, and bindings so data work can be scripted, operated in Develop, or delegated to agents.
| Lifecycle | Create, list, get, update, and delete database resources from JavaScript or Python. |
|---|---|
| Collections | List, create, and delete collections so product data stays organized around clear domains. |
| Documents | List, create, read, update, and delete JSON documents for app state, reports, events, and agent artifacts. |
| Operations | Read analytics and operational metadata to understand how the database is being used over time. |
| Bindings | Connect databases to apps, functions, auth modules, secrets, and agent runtimes from the same resource workflow. |
How to set it up
Start from the workflow that fits the product: script the database with the SDK, operate directly in Develop, or ask an agent to create and seed the data surface.
Via SDK
Create databases, collections, documents, bindings, and inspection workflows from JavaScript or Python.
On the platform
Create a Database resource in Develop, add collections and documents, connect apps or functions, and inspect data.
By agent
Ask a project agent to design a schema, seed data, bind the database, and update documents as work progresses.
How to provision
Provisioning a database turns a product data model into a live workspace resource that apps, functions, and agents can use.
| Design the shape | Define the database purpose, collections, document shape, identifiers, and ownership boundaries. |
|---|---|
| Create the database | Provision the database resource and create the collections that the app, function, auth flow, or agent needs. |
| Seed initial records | Insert representative documents for smoke tests, demos, migrations, or agent-generated product state. |
| Bind consumers | Attach web apps, functions, auth modules, secrets, and runtimes that should read or write the database. |
| Verify reads and writes | Run list, get, create, and update checks before relying on the data surface in product traffic. |
How to manage
Databases are operational product resources. Keep structure, documents, analytics, and connected consumers visible as the product changes.
| Collections | Review collections and document counts so the structure of the product data stays understandable. |
|---|---|
| Documents | List, inspect, create, update, and delete documents from SDK scripts, apps, functions, or agents. |
| Analytics | Inspect database activity patterns to understand how the resource is used over time. |
| Bindings | Review connected apps, functions, auth modules, secrets, and runtimes before changing data contracts. |
| Migrations | Use SDK scripts or agents to apply repeatable schema and seed-data changes across environments. |