Bring your own database

If your policy is that customer data lives on infrastructure you control, you can connect your own Postgres and have the workspace's operational tables live there.

What moves and what does not

Moves — operational data: Hub messages, CRM records, agent work, deliverables.

Stays central — platform data: the model catalog, billing, compliance records, and credentials. These are not yours alone and cannot be written to a customer database.

That split is enforced by the routing layer, not by convention.

Steps

1. Provision a Postgres you control, or use the guided provisioning flow.
2. Open Settings → Your Database (owner/admin).
3. Connect it and confirm it reports healthy.
4. Verify a newly created record lands where you expect.

You're done when the connection reports healthy and new data appears in your database.

Gotchas

• Connecting is not a migration. Plan what happens to existing data before you switch.
• You now own availability. If your database is unreachable, your workspace's operational data is unreachable.
• Back it up. Foreman does not back up a database it does not own.