Connecting

Once an instance reaches running, its Connection panel holds everything you need: host, port, database name, user, password, and a ready-to-copy connection URI.

Public and private instances

You choose the reachability when you create the instance:

• Public — the instance gets its own DNS name (<name>-<last-4-of-id>.db.sahabti.com) and a dedicated public port. The edge terminates the connection and opens a new one into your private network, so nothing else on the platform is exposed alongside it. This is the default.
• Private — no DNS record, no public port. Only workloads on the same workspace network can reach it.

A public instance is reachable from your laptop, your CI, and your app with no VPN or tunnel to set up.

TLS

PostgreSQL and MySQL are configured with TLS on and the platform certificate installed, which is why their connection URIs carry sslmode=require / ssl-mode=REQUIRED. Valkey's URI uses the rediss:// scheme. MariaDB, Memcached, and RabbitMQ currently come up without TLS configured — treat those endpoints as unencrypted and keep them private if that matters for your data.

Per engine

Copy the exact values from the Connection panel; the commands below show the shape.

PostgreSQL

psql "host=orders-c3d4.db.sahabti.com port=40012 dbname=orders user=orders sslmode=require"

MySQL

mysql -h orders-c3d4.db.sahabti.com -P 40013 -u orders -p --ssl-mode=REQUIRED orders

MariaDB

mariadb -h orders-c3d4.db.sahabti.com -P 40014 -u orders -p orders

Valkey

valkey-cli -h cache-c3d4.db.sahabti.com -p 40015 -a "$PASSWORD" --tls

Memcached — no authentication; keep it private unless you have a reason not to.

nc cache-c3d4.db.sahabti.com 40016

RabbitMQ

amqp://app:[email protected]:40017

Credentials

For SQL engines you can set the database name, user, and password at create time; leave the password blank and one is generated. Passwords are shown on the Connection panel, so anyone with access to the workspace can read them — that's what roles are for.

Rotating a credential from the dashboard isn't available yet. Change it inside the engine (ALTER USER, SET PASSWORD) and keep your own copy; the panel still shows the value the instance was provisioned with.

Backups

There is no managed backup or restore yet. Because a public instance is reachable from anywhere, your engine's own tooling works against it in the meantime:

pg_dump "host=orders-c3d4.db.sahabti.com port=40012 dbname=orders user=orders sslmode=require" > orders.sql

Deleting an instance is permanent, so take a dump before you do.

Next steps

• API tokens — read connection details from a script instead of the dashboard