An AI database client
for Postgres.

It writes the SQL. You decide what runs.

ask·sql·approve·run

pgen

prod.us-east-1

db.prod.internal:5432

Filter objects...

public

Tables12

customers1.2M

orders8.4M

iduuid

customer_iduuid →

total_centsint8

created_atts

line_items42M

Functions6

churn_score(uuid)

analytics

audit

ask anything about your database…

⌘K

-- the editor is yours; pgen writes here

⌘↵ to run - nothing reaches the database until you do

no rows - nothing has run

It reads your live schema.

No pasting your schema into a chat window. pgen reads the live catalog and sends the right slice straight to the model you picked. There is no pgen server in between.

prod.us-east-1

shop_prod

Filter objects...

public

Tables12

customers1.2M

invoices3.1M

orders8.4M

iduuid

customer_iduuid →

total_centsint8

created_atts

line_items42M

refunds96K

Functions6

churn_score(uuid)

recalc_totals(date)

analytics

audit

Sent with your questionread from the live catalog

Database: shop_prod (PostgreSQL 16.2)

Extensions: pgvector v0.7.0, postgis v3.4.2

schema public

customers (1.2M rows)

id uuid pk

email varchar

orders (8.4M rows)

customer_id uuid → customers.id

total_cents int8

created_at timestamptz

functions: churn_score(uuid)

types: order_status enum

Assistantshop_prod

which customers churned after the March price change?

customers, orders, churn_score()from the live schema

I joined orders to customers and scored each one with churn_score(). The query is in your editor. Nothing has run.

Ask about shop_prod…

Anthropic

Anthropicyour key

OpenAIyour key

Googleyour key

Ollamalocal, no key

OpenAI-compatibleyour URL

Keys stay in your system keychain.

Limits the model can’t turn off.

The safety layer was built before the assistant was. It treats SQL the model wrote exactly as it treats yours, and nothing in a prompt can switch it off.

prod.us-east-1read-only

1-- written by the assistant

2DROP TABLE customers;

× refusedread-only lockdefault_transaction_read_only = on

ERROR:

cannot execute DROP TABLE in a read-only transaction

0 rows · nothing changed

This sessionwhat the model asked for, and what pgen did

SELECT c.id, c.name, sum(o.total_cents) …rancapped at 1000 rows

UPDATE invoices SET sent_at = now() …heldproduction guard · needs your approval

DROP TABLE customersrefusedread-only lock

ALTER TABLE orders ADD COLUMN …heldproduction guard · awaiting your approval

‖Held by the production guard

UPDATE invoices SET sent_at = now() WHERE …

prod.us-east-1 is tagged Production, and the model wrote this statement. It runs only if you approve it.

CancelApprove and run

Between the model and pgen

Between pgen and Postgres

Download for macOS

A full Postgres client, with the assistant in its bones.

The editor, query plans, connections and history you'd expect from a serious client are all here. Open a table or a function and the assistant already knows what you're looking at.

Connections5

AllProductionStagingDevelopment

prod.us-east-1

Production · pg 16.2

analytics.warehouse

Production · pg 15.6

staging.eu-west

Staging · pg 16.2

local.docker

Development · pg 17.1

legacy-reports

Production · pg 13.8

orders.sqlrevenue.sqlchurn.sql

1SELECT o.id, o.status, c.name, o.total

2FROM ord

orderstable

order_itemstable

orders_by_monthview

orders · rows 1-50 of 1,204·1 cell edited

idstatuscustomertotal

1041shippedNorthwind Traders129.00

1042refundedContoso Ltd84.50

1043pendingFabrikam Inc212.40

1044shippedTailspin Toys56.10

1045shippedAdventure Works318.75

1046pendingLucerne Pub.42.00

Query planorders.sql

Add an index on orders.created_at to drop this scan.

⌘⇧Frefund12 hits

3 d agoSELECT count(*) FROM refunds WHERE created…

1 w agoSELECT reason, count(*) FROM refunds GROUP…

2 w agoWITH refund_totals AS (SELECT order_id, su…

Ask about your data…

orders.sql

Writing and reading

Around the query

Coming to the assistant.

Today the assistant writes SQL and you decide what runs. Here's what's coming next - all of it arriving behind the same approvals you already control.

It goes and looks things up
Bring up a table that didn't make it into the context and the assistant looks it up in the live catalog on its own - mid-conversation, before it answers.
Answers it already tested
The assistant can safely try a query before it gives it to you, so what lands in your editor is something it has already run - read-only, row-capped - and seen come back clean.
Find out why something is slow
Point it at a query that's dragging and get a straight answer about what's holding it up - without having to read a query plan yourself.
Know which index to add
Get a specific recommendation with the reasoning behind it, instead of guessing which column to index and hoping it helps.

Everywhere Postgres lives.

If it speaks the wire protocol, pgen connects. Cloud, container, or laptop - paste the URL and you're in.

point at a provider, or paste your own URL

postgres 12+·pgvector·postgis·timescaledb·extensions live in the server - if yours runs it, pgen speaks it·ssl · ssh tunnel · iam auth

Download pgen and connect.

Free, every feature, no account. Add your own API key when you want the assistant on, or run it against a local model and skip the key entirely.

Download for macOS Follow on X

An AI database client for Postgres.

Between the model and pgen

Between pgen and Postgres

Writing and reading

Around the query

It goes and looks things up

Answers it already tested

Find out why something is slow

Know which index to add

Download pgen and connect.

An AI database client
for Postgres.