All integrations
Databases
Neon
Browse tables and run read-only SQL on a Neon branch. Optionally list your users table on Users.
What you see
Databases
On the Data page as soon as Neon is connected.Sign-in, optional
On the Users page once you fill in Users table.
How to connect
Paste a key
A Neon API key (a project-scoped one is enough). Baseboard asks Neon for the role's connection string each time, so a reset password needs no reconnect. Queries still run read-only. Get a key The key is checked against Neon before it’s saved, then sealed so only the broker that calls Neon can open it.From a terminal
The CLI asks for the same key at a hidden prompt, so an agent running it never sees the key.$ npx baseboard-cli connect neon --project k57abc
Settings
- Project IDrequired
- From Project settings.For example
polished-lake-12345678 - Branch IDoptional
- Optional. Without it, the project's default branch.For example
br-cool-sky-12345678 - Databaserequired
- For example
neondb - Rolerequired
- A role that can read your tables (plus UPDATE on the banned column for bans). Neon has no read-only roles; Baseboard reads in read-only transactions.For example
neondb_owner - Users tableoptional
- Name your users table to list its rows as accounts on Users.For example
users - Id columnoptional
- For example
id - Email columnoptional
- For example
email - Created-at columnoptional
- For example
created_at - Last sign-in columnoptional
- For example
last_sign_in_at - Banned columnoptional
- A boolean column. With it, bans can be requested from Users.For example
banned
Connect Neon and the rest of your stack in one place.
Free covers one project with three connections. Everyone starts read-only.