Postgres — Guidal Docs

Guidal runs managed PostgreSQL. You get a database with credentials, automated backups and a private address reachable from services in the same project.

Create a database

bash

guidal db create demo-db --engine postgres

Provisioning takes a minute or two. Watch for it to become ready:

bash

guidal db list

Connect a service to it

Linking is the recommended path — it injects the connection string into the service as an environment variable, so credentials are never copied by hand and stay correct if they change:

bash

guidal db link demo-db --service api

To detach:

bash

guidal db unlink demo-db --service api

Connect from your own machine

bash

guidal db proxy demo-db

This opens a local tunnel, so psql, pgAdmin or any other client can connect to localhost as though the database were local:

bash

psql "postgresql://localhost:5432/demo_db"

The tunnel authenticates as you. What you are permitted to do inside the database is governed by the database role you connect with — the tunnel moves bytes, it does not widen your privileges.

To see credentials directly:

bash

guidal db credentials demo-db

This prints a live password

Avoid db credentials in shared terminals, screen shares and CI logs. Prefer db link for services and db proxy for interactive use — neither puts the password on your screen.

Backups

Every database is backed up automatically, on every plan. Retention depends on your plan:

Plan	Backup retention
Starter	7 days
Pro	14 days
Team	30 days

List and take backups:

bash

guidal db backups demo-db
guidal db backup demo-db

An on-demand backup before a risky migration is cheap insurance.

Restore

bash

guidal db restore demo-db

Restoring to a specific point in time — rather than to a backup — requires point-in-time recovery, available on Team. It lets you recover to a moment just before a bad migration or an accidental delete, rather than to the most recent nightly backup.

High availability

Team databases can run with a standby that takes over if the primary fails. On Starter and Pro a database runs as a single instance; a failure means downtime while it restarts, with data recovered from backups.

Monitor

bash

guidal db metrics demo-db

Watch connection count against your pool size, and storage growth against your plan's limit — running out of storage is the most common avoidable database incident.

Plan limits

Plan	Max databases	Storage
Starter	1	5 GB
Pro	3	25 GB
Team	10	100 GB

Storage is shared across databases, buckets and other stored data. See Plans, billing and limits.

Delete

bash

guidal db delete demo-db

This destroys the database and its data. Take a backup first if there is any chance you want it back.