Neon

Reads tables and views from a Neon serverless Postgres database. Queries run inside a read-only transaction, so Flitch can never write to your database.

Add a source

Neon authenticates with a connection string that carries the user, password, host, and database. Paste it once and Flitch parses the rest.

Prerequisites

A Neon project and a role with read access to the tables you want.
The connection string from the Neon console.

Create a read-only role (recommended)

In the Neon SQL editor, create a role limited to SELECT:

CREATE ROLE flitch_readonly LOGIN PASSWORD 'choose-a-strong-password';
GRANT CONNECT ON DATABASE neondb TO flitch_readonly;
GRANT USAGE ON SCHEMA public TO flitch_readonly;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO flitch_readonly;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO flitch_readonly;

Copy the connection string

In the Neon console, click Connect, choose the branch, database, and role, then copy the connection string. It already includes sslmode=require and channel binding:

postgresql://flitch_readonly:password@ep-xxx.region.aws.neon.tech/neondb?sslmode=require

Open the form

Go to Data → Add → Neon, and paste the connection string. Flitch shows a read-only preview (user, host, database) so you can confirm.

Pick datasets

Test the connection, then tick the tables and views to use as datasets.

Team-wide credential (optional)

Instead of pasting a string per connection, a team admin can store one shared Neon credential at Settings → Data connections. New Neon connections then default to the team credential, with no per-connection secret.

Refresh

Refresh is off by default. Every dashboard load runs a live query. Enable refresh to schedule a background refresh and serve from cache between runs. See Refresh.

Neon scales to zero when idle. The first query after a pause wakes the compute (a few seconds), then runs normally.

Troubleshooting

Authentication failed. Check the role and password in the connection string, and that the role can log in.

Connection timed out. Neon may be resuming from idle; retry. If your project restricts access by IP, allow the connector egress IP.

Permission denied on a table. Grant SELECT on that schema/table to the read-only role.

On this page