~/products/databases

// foundation/databases

Production database, fully managed.

Managed PostgreSQL for your apps

Provision isolated PostgreSQL from the dashboard or attach it during a deploy. Every logical database uses the same private, auto-scaling pool, with scoped credentials injected into its project and an always-ready floor funded by SetCloud.

app.js
const db = new Pool({
  connectionString: process.env.DATABASE_URL
});
// generated, vaulted, and injected by SetCloud

// 01 — attach at deploy

The database ships with the app.

Add a database while you deploy, and the platform creates it, generates the login credentials, stores them in your secrets vault, and passes the connection details into your app automatically. You never copy and paste a connection string anywhere.

  • + Add a database in the deploy flow or attach one to an existing project
  • + Credentials generated and stored in your vault
  • + Connection details supplied to your app before the first request
  • + Seven-day pool backups, encryption, and scaling handled for you

// 02 — pooled capacity

Scales with your traffic.

The shared pool grows and shrinks with aggregate demand — no engine, instance class, or dedicated cluster to pick. It keeps a small floor available at all times, and SetCloud subtracts that platform capacity before allocating client compute usage.

  • + Capacity scales up and down with demand, automatically
  • + Always-ready 0.5-capacity-unit floor funded by SetCloud
  • + No cloud database SKU to choose or resize

// 03 — pricing

Pay only for what you use.

No dedicated-instance fee. You pay for allocated compute above the platform floor, measured storage, and read/write I/O. The shared connection proxy and readiness floor remain SetCloud overhead. Everything draws from the same prepaid balance as the rest of the platform.

  • + Compute is allocated by activity, above the shared readiness floor
  • + Stored data bills by measured size and time
  • + Read and write operations use the current I/O rate

// 04 — operations

Project-level visibility without shared-cluster controls.

The Databases page lists application and agent workflow databases with their owning project, logical name, environment variable, region, and deployment state. Shared-cluster stop, start, resize, failover, snapshot, and delete controls stay unavailable because those operations would affect every tenant on the pool.

  • + Application and workflow databases in one view
  • + Project-scoped database and login isolation
  • + Shared infrastructure protected from tenant lifecycle actions

Current pricing

USD rates from the current billing catalog. Regional references vary with attributed usage.

Loading current rates…

Provision a database now.

Usage-based compute above the shared floor, storage, and I/O.