How do I connect to my Steada database?

Provision a database in the dashboard, create a first-reveal credential, then point a standard Redis client at your database endpoint (your-database.valkey.beta.steada.dev:6380) over TLS. Authenticate with the credential and verify against the public CA certificate. A quick redis-cli --tls PING confirms the path before you send real traffic.

Is Steada production-ready?

The production data plane is live: each database runs in its own isolated, memory-capped container with TLS on a per-database endpoint, and the durable tier adds AOF persistence with scheduled, restore-verified backups. Steada does not yet claim a formal SLA or completed compliance certification, so keep regulated data and source-of-truth state without an independent recovery path off the platform for now.

Connect

Connect over TLS with a scoped credential.

Every Steada database gets its own TLS endpoint and first-reveal credentials. Standard Redis clients connect unchanged: point them at your database endpoint on port 6380, authenticate with the credential, and verify the public CA certificate.

The short answer

Provision a database in the dashboard, create a credential (shown once — store it in your secret manager), and point a standard Redis client at <your-database>.valkey.beta.steada.dev:6380 over TLS. Run a redis-cli --tls PING smoke test first, keep your current backend behind a flag for rollback, and start with cache or rate-limit workloads with TTLs.

Endpoint <your-database>.valkey.beta.steada.dev:6380 — shown per database in the dashboard.

Protocol Valkey RESP over TLS with credential authentication.

Access Port 6380 is public with TLS SNI routing per database; everything else stays firewall-restricted.

Credentials First-reveal secrets, stored only as hashes. Rotate and revoke from the dashboard Access section.

Durability Ephemeral cache by default; the durable tier adds AOF persistence and scheduled backups with restore evidence.

Isolation Each database runs in its own memory-capped container with per-database limits.

redis-cli smoke test

redis-cli --tls -h <your-database>.valkey.beta.steada.dev -p 6380 -a "$STEADA_CREDENTIAL" PING

Verify before real traffic

redis-cli --tls -h <your-database>.valkey.beta.steada.dev -p 6380 -a "$STEADA_CREDENTIAL" <<'EOF'
SET smoke-test ok EX 60
GET smoke-test
TTL smoke-test
EOF

Before connecting traffic

Provision the database and wait for it to report ready in the dashboard.
Create a scoped credential and store it in your secret manager — it is shown once.
Use TLS and set explicit connection timeouts in your client.
Use the public CA certificate for normal TLS verification.
Prefix keys per service (for example app:<service>:<purpose>:<id>).
Start with cache, session, or rate-limit workloads with TTLs, and keep your current backend behind a feature flag for rollback.
Keep regulated data and unrecoverable source-of-truth state off the platform — no formal SLA or completed compliance certification is claimed yet.

Frequently asked questions

How do I connect to my Steada database?: Provision a database in the dashboard, create a first-reveal credential, then point a standard Redis client at your database endpoint (your-database.valkey.beta.steada.dev:6380) over TLS. Authenticate with the credential and verify against the public CA certificate. A quick redis-cli --tls PING confirms the path before you send real traffic.
Is Steada production-ready?: The production data plane is live: each database runs in its own isolated, memory-capped container with TLS on a per-database endpoint, and the durable tier adds AOF persistence with scheduled, restore-verified backups. Steada does not yet claim a formal SLA or completed compliance certification, so keep regulated data and source-of-truth state without an independent recovery path off the platform for now.

Language-specific snippets (Node.js, Python, Go) are generated per database in the dashboard connection guide. Connection background: the Valkey project and Redis client docs. Compatibility boundaries: compatibility guide.

Last reviewed 2026-07-14