PostgreSQL
AvailableDatabases
Connect to PostgreSQL for advanced analytics, geospatial data, and complex queries on structured data.
Why connect PostgreSQL?
Connecting PostgreSQL means your team stops exporting it by hand and starts working with it directly inside Viz and Dex.
- Query live data in PostgreSQL without exporting it or standing up a new pipeline
- Keep dashboards and dbt models in sync with PostgreSQL instead of a stale nightly copy
- Give teams governed, self-serve access to PostgreSQL under the same RBAC and audit trail as everything else
Works with your stack
PostgreSQL connects to the Exmergo products your team already uses.
How it works
Connecting PostgreSQL to
Exmergo VizAdd the connector
Open Data Sources in Viz and select PostgreSQL. Authenticate with the credentials PostgreSQL provides, no engineering ticket required.
Sync on your schedule
Viz reads directly from PostgreSQL and keeps dashboards current, so there's no manual export to maintain.
Ask, chart, share
Ask Viz questions about your PostgreSQL data in plain English and get charts back in seconds, ready to share with your team.
Connecting PostgreSQL to
Exmergo DexCost guard: load limitPoint Dex at PostgreSQL
Install Dex in Claude Code by running /plugin marketplace add exmergo/exmergo-agent-plugins and /plugin install dex@exmergo, then run /dex:explore against PostgreSQL. Dex connects with your PostgreSQL credentials directly, so they, and your raw data, never enter the model's context.
$ /plugin marketplace add exmergo/exmergo-agent-plugins
$ /plugin install dex@exmergo
$ /dex:explore
Explore before touching anything
/dex:explore profiles the schema it finds in PostgreSQL and proposes what to model before writing a single line of dbt.
$ /dex:explore
Author governed dbt models
/dex:transform writes and maintains the dbt models and tests that turn raw PostgreSQL data into trusted, reusable tables in your project.
$ /dex:transform
Stay inside a cost guard
Dex enforces a cost guard on every query it runs against PostgreSQL, so exploration never turns into a surprise bill.
Catch drift automatically
/dex:maintain flags it when PostgreSQL's schema changes and proposes the fix, instead of letting your dbt project silently drift out of sync.
$ /dex:maintain