Neon + CHION

Ask your Neon Postgres in plain English
Verified, read-only SQL — yours to export

Verified read-only SQL
NL→SQL agent for Neon Postgres
Reusable AI SQL skills you export to Claude Code, Cursor & Codex

Connect Chion to any Neon branch read-only and ask "weekly active users on main?" in plain English — it writes verified SQL, runs it as a read-only SELECT, and renders the chart, so you can point it at production without fear.

Verified SQL in under 10 seconds · read-only SELECT · 1,000-row cap · AES-256 vault

Start your 7-day trial Read the connection guide

Chion turns your Neon serverless Postgres into an AI SQL analyst for conversational analytics — connect read-only, ask in plain English, and turn every verified query into a reusable skill with the SQL skills generator. Credentials are wrapped in an AES-256-GCM vault, every query runs as a read-only SELECT capped at 1,000 rows, and the row-level security on the role you provide is honored on every call. It is the AI SQL workforce your team can point at a Neon branch in two minutes.

Point Chion at a Neon branch in two minutes

What changes when your PostgreSQL is serverless and branch-based.

Analyze a staging branch without touching production

Each Neon branch has its own host. Create one Chion connection per branch — typically a staging branch off main — so analytics on staging never touch production data.

Read-only by code, not by promise

Read-only by code, not by promise — every query is a verified SELECT capped at 1,000 rows.

Cold starts on scale-to-zero

Neon compute scales to zero after inactivity, so the first query after idle takes 1–3 seconds to wake. Subsequent queries run at full speed; enable "Always on" if you need predictable first-query latency.

Pooled vs direct connections

Toggle connection pooling in the Connect modal. Chion works with either the pooled or the direct endpoint; pick pooling for high-concurrency branches.

Copy-on-write resets and PITR

Branches are copy-on-write. A branch reset reverts to the parent's state at branch-creation time; use point-in-time restore on the parent for a more recent snapshot, then refresh the connection in Chion.

Runs inside Neon's free tier — read-only queries stay small

Chion's read-only queries are small and fit within free-tier compute and storage limits. See how Chion compiles a verified SQL pipeline and the read-only security model.

Every answer becomes a portable SQL skill — no lock-in

Every answer becomes a portable SQL skill you export to Claude Code, Cursor, or Codex — no lock-in.

Example question & SQL

See what Chion generates from a plain-English question.

You ask

"Show me signup trends by week for the last 3 months"

Chion generates

SELECT
  date_trunc('week', created_at) AS week,
  COUNT(*) AS signups
FROM users
WHERE created_at >= now() - interval '3 months'
GROUP BY 1
ORDER BY 1;

Create a read-only Postgres role

Run this once before you connect. Chion enforces read-only at the SQL validator, but a least-privilege role is the canonical pattern.

CREATE ROLE chion_read LOGIN PASSWORD '<strong-password>';
GRANT CONNECT ON DATABASE <dbname> TO chion_read;
GRANT USAGE ON SCHEMA public TO chion_read;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO chion_read;
ALTER DEFAULT PRIVILEGES IN SCHEMA public
  GRANT SELECT ON TABLES TO chion_read;

Replace <dbname> with your database name. The ALTER DEFAULT PRIVILEGES line ensures new tables are auto-readable.

Connection string format

Reference for parsing. Chion accepts the six fields directly, no string concatenation needed.

postgresql://chion_read:<password>@ep-<id>.<region>.aws.neon.tech/neondb?sslmode=require

Read-only by code. Verified by Chion's 13-step SQL pipeline.

Finding your Neon credentials

Project Dashboard → Connect button

Field	Where to Find	Default
Server (Host)	Connect modal → displayed in connection string	ep-<name>-<id>.us-east-2.aws.neon.tech
Port	Connect modal	5432
Database	Connect modal · selectable dropdown	neondb
Schema	Not in UI; default is public	public
User (Role)	Connect modal · selectable dropdown	neondb_owner
Password	Shown in the connection string in the Connect modal	(always visible in modal)

Quick steps

1.Log in at console.neon.tech
2.Select your project
3.Click the Connect button on the Project Dashboard
4.The "Connect to your database" modal opens
5.Select your Branch, Compute, Database, and Role from dropdowns
6.All connection parameters including password are displayed in the connection string
7.Toggle Connection pooling on/off to switch between pooled and direct connections

Password is always visible in the Connect modal; no need to reset.

Open Neon console

Neon troubleshooting

Common issues and how to fix them.

Serverless cold-start delay

Neon computes scale to zero after inactivity. The first query after a cold start may take 1–3 seconds while the compute wakes up. Subsequent queries run at normal speed. To avoid cold starts, enable Neon's "Always on" compute setting.

Branch confusion: wrong data

Neon uses branches. Make sure you selected the correct branch in the Connect modal before copying credentials. Each branch has its own endpoint hostname.

Connection pooling toggle

In the Neon Connect modal, toggle "Connection pooling" on for pooled connections or off for direct. Chion works with both modes.

Branch reset lost recent data

Neon branches use copy-on-write. Resetting a branch reverts it to the parent's state at branch-creation time. Use point-in-time restore (PITR) on the parent if you need a more recent state.

Official Neon documentation

Authoritative references from the provider. Opens in a new tab.

Neon connection strings
How to construct and parse Neon connection URIs.
Neon branching
Branch creation, copy-on-write semantics, and reset behavior.
Point-in-time restore
How PITR interacts with branches and connected applications.
PostgreSQL CREATE ROLE
Reference for the read-only role used by Chion.

Your credentials are encrypted

All connection credentials are encrypted with AES-256-GCM and stored in an isolated vault. Chion connects with read-only permissions. No INSERT, UPDATE, or DELETE is ever possible. Row-level security policies are honored on every query.

Read our security model

Frequently asked questions

Common questions about using Chion with Neon.

Can I connect Chion to a Neon branch?

Yes. Each Neon branch has its own endpoint. Select the branch you want in the Connect modal and copy those credentials into Chion.

Does Chion work with Neon's free tier?

Yes. Chion's read-only queries are lightweight and work within Neon's free-tier compute and storage limits.

What is the default database name on Neon?

The default database is "neondb". You can verify this in the Connect modal's database dropdown.

Does Chion support Neon point-in-time restore?

Indirectly. PITR happens on Neon's side; Chion just queries whatever state the branch is in. After a PITR, refresh the connection in Chion if results look stale.

Can I use Neon branches for staging vs production?

Yes, and it is the recommended pattern. Create a "staging" branch off "main", connect Chion to staging for testing, then point at the main branch for production analytics. Each branch has its own credentials.

Ready to connect your Neon database?

Open Chion, enter your credentials, and start asking questions in plain English.

Start your 7-day trial

Ask your Neon Postgres in plain EnglishVerified, read-only SQL — yours to export