Bolt Cloud databases are Supabase-backed PostgreSQL, so Jobo writes to them over
the standard Postgres wire protocol — the same canonical table, upsert semantics,
and sync behavior as the PostgreSQL
destination.
Bolt does not expose a connection string for a database it still manages for
you. Before you can connect this destination, you need to either claim your
database in Supabase or point Bolt at a Supabase project you already own.
Both are one-time steps — see below.
Get your connection details
Open Advanced database settings in Bolt
In your Bolt project, go to Database → Advanced.
Claim the database in Supabase
Choose claim your database in Supabase. This hands the underlying
Postgres instance to a Supabase project you control, which is what gives you
external connection credentials, a SQL editor, and monitoring.If you would rather use a Supabase project you already have, use connect an
external Supabase project instead. Bolt warns that this replaces the
current connection and may cause data loss, so do it before your app holds
data you care about.
Copy the pooler credentials
In the Supabase dashboard, open Connect → Session pooler and copy the
host, port, database, and username. The password is the database password
from Project Settings → Database.Prefer the pooler host over the direct db.<ref>.supabase.co host — the
direct host is IPv6-only.
Connection Configuration
Example Configuration
The target table is created automatically on first sync if it doesn’t exist,
and Jobo upserts on job ID — so re-running a push updates rows in place instead
of duplicating them. Point the destination at a dedicated table rather than one
your Bolt app writes to itself, since Force resync drops and recreates it.
Reading the data from your Bolt app
Once the first push completes, the table is a normal Postgres table in your
project. Query it from your Bolt app exactly like any other table — through the
Supabase client, or over the REST API Supabase generates for it.
Your credentials are encrypted at rest with AES-256. See
Security for details, and
Sync behavior for how incremental
pushes, full resyncs, and expiry are handled. 
