Browse docs
Cloud docs
Connecting to QuestDB on Layerbase Cloud
QuestDB exposes a PostgreSQL-compatible SQL endpoint for time-series queries, plus a dedicated HTTPS endpoint that speaks InfluxDB Line Protocol for high-throughput ingest.
Best for: IoT data, market data, metrics, append-heavy event streams, and time-series analytics.
Open your database in the dashboard
Go to /cloud, click the database you just created, and the connection panel shows the host, port, username, password, and a ready-to-paste connection string for the engine.
Use the generated SQL connection string from Quick Connect.
You can also download the whole set instead of copying values one at a time: the Connect dialog offers a Download .env file, ready to drop into a project under the environment variable your engine's clients expect, and a Download .txt with the labeled parameters. Both files contain the password in plain text, so keep them out of version control.
TLS is required, on by default
Append ?sslmode=require to the connection string.
PostgreSQL-compatible endpoint on port 5432, plus InfluxDB Line Protocol over HTTP on port 443
Use any standard client
QuestDB works with the normal client family for that engine. Start with the dashboard snippet, then move the same URL and credentials into your app environment.
If your client has separate direct, pooled, TLS, or HTTP options, prefer the exact variant shown in Quick Connect.
psql "postgresql://layerbase:password@your-host.cloud.layerbase.dev:5432/qdb?sslmode=require"QuestDB notes
- Use QuestDB SQL features for time-series queries after connecting through PostgreSQL clients.
- For high-throughput ingest, write InfluxDB Line Protocol over HTTP to the dedicated ILP hostname (your database hostname with -ilp on the first label) on port 443, authenticated with the same username and password as the SQL endpoint. The dashboard Connect dialog carries the URL, a ready-to-paste client config string, and Python and curl snippets.
- Raw ILP over TCP is not exposed, and the ILP hostname serves only the write paths: no SQL, no QuestDB web console. See the ILP ingest guide at /docs/engines/questdb.