Quickstart

Go from zero to a monitored, backed-up, governed database in five steps. You'll need a database you can reach and an account on the console.

1. 1

   Register or log in to your organization

   Create your organization (or sign in to an existing one). New organizations start with a Default workspace and an org-admin account.

2. 2

   Create a workspace

   Workspaces isolate environments — dev, staging, production — under one organization, each with its own connections, policies, and members. Create one from the workspace switcher in the sidebar, or start in the Default workspace.

   name:  Production
   env:   production

3. 3

   Register your first connection

   Add a database from Fleet → Add connection. Credentials are encrypted with AES-256-GCM the moment they’re saved — they’re never returned or logged.

   Engine:    PostgreSQL
   Host:      db.internal.acme.io
   Database:  orders
   SSL mode:  require

4. 4

   Set up monitoring

   Health, metrics, and slow queries start flowing immediately. Add an alert rule with a threshold and route it to Slack, email, a webhook, PagerDuty, Teams, or Opsgenie.

   metric:    connections.active
   operator:  gt
   threshold: 180
   channel:   #db-alerts (Slack)

5. 5

   Schedule a backup

   Create a backup policy with a cron schedule, a retention window, and a storage target — local, S3, Azure, GCS, SFTP, or an OAuth drive. A watchdog reaps any stuck job.

   schedule:   0 2 * * *   # 2am daily
   retention:  14 days
   storage:    s3://acme-backups/prod

6. 6

   Invite your team — least privilege

   Invite members with one of seven roles, and confine workspace-scoped roles to specific workspaces. Every privileged action lands in the immutable audit log.

   role:        dba
   workspaces:  [ production ]   # confined