-
Open your database provider’s dashboard
The string is always in the project or database settings, usually under a heading like Connection, Connect or Database URL.
-
Copy the connection string, not the individual fields
Most providers offer both. The single string is less error-prone than reassembling five fields by hand.
-
Swap in the read-only role
Replace the username and password with the read-only role you created, keeping the host, port and database name.
-
Paste it into LEDAR
The app proves the connection is read-only before it reads anything, so a wrong role is caught immediately rather than halfway through a scan.
By provider
| Provider | Where to look |
|---|---|
| Supabase | Project Settings → Database → Connection string. Prefer the direct connection over the pooled one for scanning; a pooler can hide session-level settings the read-only check looks at. |
| Neon | Dashboard → Connection Details. Copy the pooled or direct string; both work. |
| Railway | The Postgres service → Variables → DATABASE_URL. |
| Render | The database → Info → External Database URL. |
| Heroku | Settings → Config Vars → DATABASE_URL. It rotates, so copy it fresh. |
| Your own server | Assemble it: postgres://user:password@host:5432/database |
If SSL is required
Most managed providers require TLS. If a connection is refused for that reason, append ?sslmode=require to the string.
postgres://ledar_reader:••••@db.example.com:5432/appdb?sslmode=require