Finding your database
Open Databases in the dashboard. The page shows one pooled database for each application or agent, including its owner, logical database name, region, status, and injected environment-variable name. It never returns a connection string, password, cloud account id, or shared-cluster identifier.
Automatic injection
When a database is attached to an application, its connection string is
generated and stored as a deployment secret. Adding it from Databases starts
a deployment automatically; that deployment receives DATABASE_URL. Agent
deployments receive the same connection through both DATABASE_URL and the
agent-specific SET_AGENT_POSTGRES_URL alias for their framework checkpointer.
There is nothing to copy and nothing to paste:
import pg from 'pg';
const pool = new pg.Pool({ connectionString: process.env.DATABASE_URL });Managed database removal follows project teardown. There is no standalone detach or shared-cluster delete control.
Private networking
The pooled database and connection proxy accept traffic only from SetCloud-managed workload networking. A laptop or public GUI client cannot connect directly. Run migrations and one-off administration from the linked deployment. Do not log DATABASE_URL or expose it through a temporary application route.
More: