Managed PostgreSQL on one shared, private, auto-scaling pool. Each application and agent gets a separate logical database and login role.
How it scales
The shared pool scales capacity with aggregate load and keeps a shared readiness floor available. There is no engine, instance class, or dedicated cluster to choose. SetCloud absorbs the shared floor and proxy instead of allocating those standing costs to a client.
Pricing
Usage-based, drawn from your prepaid balance:
Compute above the readiness floor is allocated by activity; storage and I/O are measured separately. The live database rate card gives all three prices. Storage uses decimal GB and a 730-hour storage month. The shared floor and connection proxy are platform overhead.
Provision one
Attach Managed PostgreSQL on the deploy review screen, or add it from
Databases to start a deployment automatically. The generated connection
string is stored as a deployment secret and injected into applications as
DATABASE_URL. Agent deployments receive their scoped pooled connection as
SET_AGENT_POSTGRES_URL.
Your logical database belongs to one application. It has a scoped login, cross-database access is revoked, and network access is limited to SetCloud-managed workloads.
Lifecycle
Logical pooled databases are managed with their project or agent. The dashboard does not expose shared-cluster stop, start, resize, snapshot, failover, or delete controls because those operations would affect other tenants.
Connection errors?
- Confirm the app reads its connection settings from the environment, not from a hardcoded string.
- Redeploy after changing environment configuration.
- Check the application logs for the exact failure.
More: Databases quickstart.