Connect Koyeb Serverless PostgreSQL from a Desktop GUI (sslmode=require)
Connect Koyeb serverless PostgreSQL from a laptop GUI: copy the Connection Details string, add sslmode=require (the psql URL often omits it), use port 5432 and koyeb-adm/koyebdb on a fresh service, and paste the URL into HiDataLinker, a free local-first PostgreSQL desktop client.
Koyeb Database Services are serverless PostgreSQL you can stand up next to your apps. The Connection Details tab hands you a Koyeb PostgreSQL connection string, but the copied psql URL often has no TLS query string—while official library examples set sslmode=require. This guide shows how to use a Koyeb Postgres desktop GUI with HiDataLinker, a free MIT PostgreSQL and MySQL desktop client: local-first credentials, URL paste, Dump / same-engine migrate, and no seat or tab freemium wall.
Koyeb is a third-party service; this guide is not affiliated with Koyeb.
1. Copy the Connection Details string
In the Koyeb control panel, open Databases, select your Database Service, then the Connection Details tab. Choose the logical database from the dropdown. A new service starts with database koyebdb, owned by the default role koyeb-adm unless you renamed it at create time.
The psql option shows a standard URI. Official docs use an example like this (copy your host, role, password, and database—do not reuse the sample hostname):
postgres://koyeb-adm:PASSWORD@ep-xxxx.eu-central-1.pg.koyeb.app/koyebdb
Hosts look like ep-….{region}.pg.koyeb.app. The port is omitted because services use PostgreSQL’s default 5432—fill that in if your client asks for a port. The password is shielded by default; reveal it with the view icon, then copy. If the client wants discrete fields, use the .env option or parse the string.
2. Add sslmode=require before you paste
Official JavaScript examples set ssl: 'require'; the Django example sets OPTIONS: {'sslmode': 'require'}. Append the flag:
postgres://koyeb-adm:PASSWORD@ep-xxxx.eu-central-1.pg.koyeb.app/koyebdb?sslmode=require
Do not strip TLS just to “get connected.” Official pages do not document a customer CA download for this path, so stay on require rather than inventing a verify-full + CA click-path.
If you also keep a Prisma DATABASE_URL with pgbouncer=true, leave that flag for the app. For a desktop session—browse, SQL, or Dump / same-engine migrate—paste the standard Connection Details URI plus sslmode=require, on port 5432.
3. Connect with HiDataLinker
- Install from hidatalinker.onesolo.app.
- Open New Connection → paste the URI (keep
sslmode=require) or fill host, port 5432, user, password, and database. Percent-encode special characters in the password. See paste a DATABASE_URL. - Test, then connect. Profiles stay on your machine—local-first, no hosted workspace.
- Browse schemas, run SQL, and use Dump (
.sql) or same-engine PostgreSQL → PostgreSQL migrate on that connection.
Source: github.com/henrybit/HiDataLinker · Overview: /db-client
HiDataLinker is a thin Tauri desktop app for PostgreSQL and MySQL—paste DATABASE_URL, keep creds local, and avoid seat / connection / tab freemium walls. Honest v1: MySQL + PostgreSQL as marketed; not the Koyeb control panel, and not an in-app sleep, instance-type, or role manager.
Common failures (and the fix)
- TLS / unexpected SSL error — The copied
psqlstring had nosslmode. Add?sslmode=requireand retry. - Auth failed — The password may still have been hidden when you copied; reveal it and copy again, or reset it on the Roles tab (existing sessions keep the old password until they reconnect). Percent-encode special characters in the URI. Confirm the role and database:
koyeb-adm/koyebdbon a fresh service, or the names you actually created. - Wrong port — Do not invent a pooler port. Official connection strings omit the port because it is 5432.
- First query is slow after idle — Official docs: after 5 minutes of inactivity the compute sleeps and wakes on the first new query with a minor delay. Reconnect or retry; HiDataLinker does not manage Koyeb sleep or instance type.
- Neon-looking errors — Koyeb’s troubleshooting section points at Neon’s connection-errors documentation. Use the full
*.pg.koyeb.apphostname, not a raw IP, so TLS SNI can work. This is still your Koyeb Database Service—not the Neon Console, and not the-poolerhostname from our Neon desktop GUI guide.
Soft next step
Need a Koyeb Postgres desktop GUI that pastes the Koyeb PostgreSQL connection string, keeps sslmode=require, uses 5432 with koyeb-adm / koyebdb (or your own names), and stays local-first?
- Download: https://hidatalinker.onesolo.app/
- Source: https://github.com/henrybit/HiDataLinker
The same hosted-Postgres pattern shows up on Neon (a different -pooler hostname) and Render Postgres.