Connect Tiger Cloud Postgres from a Desktop GUI (sslmode=require / verify-full)
Connect Tiger Cloud Postgres from a laptop GUI: copy Console or credentials-file details, keep sslmode=require or tighten to verify-full once the signed cert is ready, and use the direct port—not the pooler—with HiDataLinker, a free local-first PostgreSQL desktop client.
Tiger Cloud (you may still search for Timescale Cloud) is managed PostgreSQL, powered by TimescaleDB. This guide shows how to connect Tiger Cloud Postgres from a 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.
Tiger Cloud, Tiger Data, and Timescale are third-party marks; this guide is not affiliated with Tiger Data.
1. Get the connection details (Console or the credentials file)
You need hostname, port, username, password, and database. Official examples often use user tsdbadmin, database tsdb, and a host like <service-id>.<project-id>.tsdb.cloud.timescale.com—still copy the values from your service, especially the port. Do not assume 5432.
When you create the service, Download the config / <service name>-credentials.txt. Official docs say this is the only time the password appears in that file and connection string; if you lose it, reset it (Forgot your password? in Tiger Console). Later, open Services → your service → Service info > Connect > More details for everything except the password. See Find your connection details. Wait until the service is Ready. Do not confuse project client credentials (API or Terraform keys) with the database password, and do not follow local TimescaleDB quickstarts on localhost port 6543.
2. Keep sslmode=require, or tighten to verify-full
The official default service URL uses sslmode=require. Keep it (or the equivalent SSL mode in the client). Do not strip TLS just to “get connected.”
postgres://tsdbadmin@<HOST>:<PORT>/tsdb?sslmode=require
To verify the certificate, use verify-ca or verify-full and a trusted chain (the OS trust store, or a CA file). Official pgAdmin and DBeaver docs set this on the SSL tab. Signed certs come from Google or ZeroSSL, not a vendor CA download.
A new service starts with a self-signed certificate. A CA-signed certificate is usually issued within about 30 minutes (connections reset when the cert is swapped), so verify-full can fail until then—use require in that window. See strict SSL. Free services do not supply SSL certificates; do not expect verify-full on the free tier.
postgres://tsdbadmin@<HOST>:<PORT>/tsdb?sslmode=verify-full
Use the full hostname, not a raw IP: verify-full needs name matching, and TLS needs SNI.
3. Use the direct port, not the transaction pooler
For a desktop session—browse, SQL, schema work, or Dump / same-engine migrate—use the direct service port from Connect or the credentials file, not the transaction pooler.
If connection pooling is enabled (not on free services), the pooler uses the same host and a different port. Session pool: pooler port + database tsdb. Transaction pool: the same pooler port + database tsdb_transaction. Copy the exact string from the Connection pooling tab; do not guess ports.
If the TCP connection times out, check whether the service has an IP allow list and add your current public IP (Operations > Security > IP Allow List).
4. Connect with HiDataLinker
- Install from hidatalinker.onesolo.app.
- Open New Connection → paste the direct service URL (keep
sslmode=require, orverify-fullonce a signed cert is in place) or fill host, port, 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 direct 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 Tiger Console, not a Timescale hypertable designer, and not an in-app pooler or VPC admin.
Common failures (and the fix)
- Auth / missing password — Re-copy from the credentials file, or reset it in Console. Percent-encode special characters in the URI.
- Wrong port / pooler database —
tsdb_transactionor a pooler port will break dumps and session features. Switch to the direct port and databasetsdb(or the name in your details). verify-fullfails right after create — Wait about 30 minutes for the signed cert, or userequireuntil then. Free services have no signed cert.- Timeout — Service not Ready; an IP allow list is blocking you; or you followed a local TimescaleDB tutorial on
localhost:6543. - TLS to a raw IP — Use the full hostname for SNI and for
verify-fullname matching.
Soft next step
Need a Tiger Cloud desktop GUI that pastes the service URL, keeps sslmode=require (or verify-full after the signed cert), uses the direct port, 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.