What the platform does for you

Choose engine, version, region, compute, memory and NVMe storage. The platform builds the instance, generates credentials and hands back a working endpoint — no operator touches a config file.

Every database gets a managed endpoint, an encrypted connection and securely generated credentials. Passwords are encrypted at rest and revealed only to authorised users, with each reveal recorded.

Scheduled and on-demand backups with configurable retention. Every backup is restore-tested into a throwaway instance before it is marked verified, because an untested backup is not a backup.

Restore supported engines to a chosen moment using continuous transaction log archiving.

Snapshot restore is available today. Continuous WAL archiving is Phase 2.

Primary and replica architecture with health checks and automatic failover for mission-critical workloads.

Streaming replication ships today. Automatic failover needs the consensus layer — Phase 2.

Add streaming replicas to take reporting and analytics traffic off your primary. Replicas are read-only and their lag is reported live.

PostgreSQL today. MySQL and MariaDB replication is Phase 3.

CPU, memory, storage, connections, query latency, cache efficiency and replication lag — collected from the engine itself, not guessed from the host.

Move between plans with a controlled workflow. Your data volume is preserved across the change; only the compute envelope is replaced.

Per-database IP allow-lists enforced at the host firewall, role-based access for your team, secret management and an immutable audit trail.

Every lifecycle action — create, resize, back up, restore, replicate, analyse — is available through the API with scoped keys, so provisioning can live in your pipeline.