Databases

Databases are first-class ACP SDK primitives. The database manager covers database lifecycle plus collection and document CRUD, which makes it a natural fit for app backends, operational tooling, and ACP-managed product state.

Pricing

Database pricing in Compute Tokens

Databases currently do not expose a separate minute-based metered resource rate in the public CT pricing model. You are billed for the computers, functions, web apps, auth modules, or agent runtimes that operate on the data surface.

Database surface

No standalone CT / minute runtime rate

Database usage is typically paired with other ACP compute or deployed surfaces.

What databases are for

Use databases when ACP should store product state, operational records, queue-like collections, or structured application data directly inside the same platform boundary as your threads and resources.

Attach the database to a project when the data belongs to one ACP system boundary.

Use collections as logical groupings before inserting documents.

Use the database manager from apps, functions, auth flows, or scheduled operations.

Full database lifecycle in JavaScript

The database manager covers database CRUD plus collection and document CRUD on the same surface.

These are the actual SDK methods on client.databases.

Use one lifecycle script like this in migration jobs and internal control planes.

Operate a database end to end