Cloud docs
Connecting to your Layerbase Cloud database
Every Layerbase Cloud database comes with a connection string, a hostname, and TLS. Any standard client for your engine works, the same one you would point at a local Postgres or Mongo.
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.
The dashboard always has the freshest credentials. If you ever rotate your password, the new value shows up there immediately.
TLS is required, on by default
All Layerbase Cloud connections are encrypted. For PostgreSQL, CockroachDB, SQLite, DuckDB, and QuestDB this means appending ?sslmode=require to the connection string. For MongoDB and FerretDB it means tls=true. MySQL and MariaDB clients usually just need the host plus a TLS flag.
HTTP-native engines (Qdrant, Meilisearch, InfluxDB, CouchDB, SurrealDB, Weaviate, libSQL) reach you over HTTPS on port 443. No flag needed, just a valid bearer token from the dashboard.
Use any standard client
psql, mysql, mongosh, redis-cli, ioredis, mongoose, drizzle, prisma, pg, mysql2, the official engine SDK, your ORM, your favorite IDE: they all work. Layerbase Cloud terminates connections at the engine's native wire protocol.
For serverless and edge runtimes, Redis-family databases also speak the Upstash REST API, and MySQL-family databases speak the PlanetScale serverless driver. Same database, alternate protocol, picked via the hostname suffix.
Engine-specific quirks
The in-dashboard connection panel has working examples for the most common client per engine, and the open-source SpinDB CLI docs cover the wire-level details if you want to dig deeper.