Managed Database Hosting for Production Apps
Pick from seven managed engines (MySQL, PostgreSQL, Redis, and more) and the platform handles the rest. SSL, automated failover, admin tooling, and 14 daily backups come with every node.
Run MySQL, MariaDB, PostgreSQL, or Percona for relational data, plus Redis, OpenSearch, and Couchbase for cache, search, and documents.
Every database node ships with SSL encryption and 14 daily backups.
Switch on replication and automatic failover with a single toggle in the dashboard.
Database nodes take on more RAM and CPU under load and release it when traffic settles, within a limit you set.
Engine catalog · spec sheet
Seven Managed Engines
Every engine is platform-managed: provisioning, backups, SSL, and admin tooling are all handled for you. There is no OS access. If you need root, custom storage engines, or kernel modules, Cloud VPS is the right path.
- SQL
-
MySQL group replicationreplica · 1–NDefault for WordPress, Laravel, and LAMP stacks.
-
MariaDB galeramulti-primary · syncWrite-heavy apps that need MySQL compatibility and no single point of failure on writes.
-
PostgreSQL streaming repl.replica · WAL asyncJSONB columns, full-text search, PostGIS geospatial queries.
-
Percona Server xtradbmulti-primary · syncHigh-traffic MySQL workloads where you want built-in query diagnostics and tuning visibility.
- NoSQL
-
Redis in-memoryreplica-set · TCPKey-value store for caching, sessions, and Pub/Sub fan-out.
-
OpenSearch distributed searchsharded · multi-nodeLogs, search, and analytics. Pairs with Logstash and Beats.
-
Couchbase documentreplica-set · SQL++JSON document database with N1QL/SQL++ query support.
What the Platform Manages for You
The management experience is the same no matter which engine you pick. Backups, access controls, replication, routing, and admin tools all live in the same dashboard as your application nodes.
- 14 daily backups, every engine: dashboard restore replaces the node from the selected artifact. Custom cron cadence available as an add-on.
- SSL/TLS on every connection: platform-issued certificates on every node. No certificate management required.
- Built-in admin tools for each engine: phpMyAdmin (MySQL, MariaDB, Percona Server), phpPgAdmin (PostgreSQL), Redis CLI, OpenSearch Dashboards, and Couchbase Web Console. Optional IP restrictions are available without a bastion.
- Replication configured at provision: choose your replication mode when you provision and change it from the dashboard later. Options include Galera, XtraDB, MySQL group replication, PostgreSQL streaming WAL, Redis and Couchbase replica-sets, and OpenSearch sharding.
- One connection string, always: ProxySQL for the MySQL family, Pgpool-II for PostgreSQL, and native client routing for Redis, OpenSearch, and Couchbase. Your app sees one connection string regardless of cluster size. No query rewrites.
- Sub-five-second automated failover: on every clustered topology a replica or quorum survivor takes over, and the connection string stays the same.
- Node recovery and corruption detection: rejoin failed nodes and catch corruption before queries do, across the SQL clusters (Galera, XtraDB, group replication, streaming WAL) and the NoSQL replica-sets.
Start Standalone, Cluster on Demand
Start with a single managed node. Add read replicas with ProxySQL routing as traffic grows. When you need high availability, move to a Galera, XtraDB, or replica-set cluster. Automated failover kicks in within five seconds.
How clustering and failover work
Engine and topology details, ProxySQL and Pgpool-II routing, replication modes, reference architectures, and the consolidated clustering FAQ.
Common Database Questions
Which database engines can I deploy?
SQL: MySQL, MariaDB, PostgreSQL, and Percona Server. NoSQL: Redis, OpenSearch, and Couchbase. All are available from the control panel topology wizard.
Are backups included?
Every database node includes 14 daily backups. An optional Backup/Restore add-on lets you set custom schedules and store backups on remote storage.
Can I cluster my database for high availability?
Auto-clustering covers MySQL, MariaDB, PostgreSQL, Percona Server, Redis, and OpenSearch. Database Clusters has replication types and setup details.
How do I connect my application to the database?
After provisioning, you receive credentials by email. Connect with the provided hostname and port. For clustered databases, use the ProxySQL or Pgpool-II entry point for automatic load balancing.
What NoSQL options are available?
Redis for in-memory key-value caching and pub/sub, OpenSearch for full-text search and analytics, and Couchbase for document-oriented workloads. All are available from the topology wizard with optional auto-clustering.
Can I manage database settings and monitor performance?
Use phpMyAdmin (MySQL, MariaDB, Percona Server) or phpPgAdmin (PostgreSQL) directly from the platform dashboard. For config edits beyond what the UI exposes, SSH access is available as the database process user — not root. There is no OS-level or root access on any managed database node.
What happens to database charges if I stop application nodes?
Database resources keep running and continue billing until you stop or resize those database nodes. Stopping only web or app layers does not pause active database containers.
No matching questions found.
Test your stack on metered hosting
- Meters real usage: baseline plus actual use, not a fixed tier
- Turnkey clustering: traffic reroutes once clustering is enabled
- From Git push to live: in minutes, not hours
- Engineers on call: real support around the clock
Start a real trial environment
Deploy your app, test the ceiling, and estimate cost before you commit.