Your managed database bills the same way as everything else on the platform: usage-based, deducted from your prepaid credits, no separate subscription.
What’s metered
Three meters, all on the current published rate card at /pricing:
- Compute — capacity used while the database is actually handling queries, billed per capacity-unit-hour.
- Storage — data at rest, billed per GB-month.
- I/O — the read/write requests the database serves.
There’s no instance size to pick and no dedicated cloud database service to resell.
The always-ready floor
The shared pool keeps a shared readiness floor so the next request does not wait for a database cold start. SetCloud subtracts that floor before allocating compute usage to client databases. Clients pay their share of compute above the floor, their measured storage, and their read/write I/O; the platform also absorbs the shared connection proxy.
On your invoice
Database usage appears as a single Managed Databases line on your monthly statement. Each project or agent has one scoped logical database; agent checkpoints and application data do not create a second billable database row.
More: