1. 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.

  2. 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.

  3. 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.

  4. 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

Where each host keeps it
ProviderWhere to look
SupabaseProject 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.
NeonDashboard → Connection Details. Copy the pooled or direct string; both work.
RailwayThe Postgres service → Variables → DATABASE_URL.
RenderThe database → Info → External Database URL.
HerokuSettings → Config Vars → DATABASE_URL. It rotates, so copy it fresh.
Your own serverAssemble 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.

example
postgres://ledar_reader:••••@db.example.com:5432/appdb?sslmode=require