Managed Databases quickstart

Provision one isolated PostgreSQL database on SetCloud’s shared managed pool. The connection string arrives in your app as an environment variable.

Prerequisites

• A SetCloud account with billing set up.
• A project ready to deploy — see the deployments quickstart.

1. Choose a database at deploy time

In the deploy wizard or the dashboard’s Databases page, choose:

• Managed PostgreSQL — shared auto-scaling capacity with an always-ready floor maintained by SetCloud. There are no engine or instance-size choices.

2. Use DATABASE_URL

The full connection string is injected into your app as DATABASE_URL — never printed in logs, never in your repo.

import pg from 'pg';

const pool = new pg.Pool({ connectionString: process.env.DATABASE_URL });
const { rows } = await pool.query('SELECT now()');

3. Check it in the dashboard

The Databases page shows one pooled logical database alongside the project or agent that owns it. Applications receive DATABASE_URL; agents receive the same connection through DATABASE_URL and SET_AGENT_POSTGRES_URL, so durable framework state does not appear as a second database product.

Costs

Compute above the platform-owned capacity floor, storage, and I/O bill from your credit balance. SetCloud absorbs the shared cluster’s always-ready floor. Rates are on the pricing page.

Next

• Secrets quickstart — for every other credential.
• Deployments quickstart — the flow that provisions this.