Managed Databases — Clustering, Automated Backups, and SSL on Every Plan

Deploy SQL and NoSQL databases from the dashboard with SSL encryption, clustering, IP-restricted access, and built-in admin panels.

7 Engines Supported

MySQL, MariaDB, PostgreSQL, and Percona for relational workloads. Redis for caching. OpenSearch for analytics.

SSL & Backups Included

14 days of automated backups and built-in SSL encryption at no extra cost.

One-Click Clustering

Enable replication and failover with a single toggle from the control panel.

Auto-Scaling Resources

Resources scale vertically as load increases — up and back down within limits you set.

24/7Engineer support
14Daily backups
8+Runtimes
< 10 minAvg support response

Pick the right database engine for your workload

Choose the engine that matches your query pattern, clustering needs, and how much platform automation you want on day one.

SQL databases

  • MySQL — the default for WordPress, Laravel, and LAMP stacks. Primary-Secondary and multi-primary clustering available.
  • MariaDB — MySQL-compatible with Galera clustering for synchronous multi-primary replication. Pick this when you need failover across multiple write nodes.
  • PostgreSQL — for apps that need JSONB columns, full-text search, or PostGIS geospatial queries. Primary-Secondary replication available.
  • PerconaDB — MySQL-compatible with XtraDB clustering and built-in query diagnostics. Primary-Secondary and multi-primary replication available.

NoSQL databases

  • Redis — in-memory key-value store for cache layers, session stores, and Pub/Sub message brokering.
  • OpenSearch — distributed search and analytics engine (Apache 2.0). Use with Logstash and Beats for log aggregation and observability.
  • Couchbase — document-oriented NoSQL with SQL++ (N1QL) query support, for apps that combine document flexibility with familiar SQL-like queries.

Manage, back up, and recover without leaving the dashboard

Replication modes

Pick the mode that matches your access pattern: Primary-Secondary for read-heavy workloads, Primary-Primary for distributed writes, or Galera/XtraDB for multi-primary replication where every node has the same data at commit time.

Compare clustering topologies

Automated backups

14 days of daily restore points included. Optional Backup/Restore add-on supports custom cron schedules, configurable retention, and remote storage targets.

SSL/TLS encryption

Encrypts data in transit between application and database nodes. The platform generates and configures certificates per node automatically.

Admin panels

phpMyAdmin for MySQL/MariaDB/Percona, phpPgAdmin for PostgreSQL, Redis CLI, and OpenSearch Dashboards are all accessible from the dashboard.

Recovery & Diagnostics

Cluster Recovery detects replication breaks and restores operability automatically. Corruption Diagnostic checks index and table integrity. Slow-query logs help you find the queries that need optimization.

Start standalone, then scale to a cluster when traffic demands it

Every database starts as a standalone node. That is usually enough for dev, staging, or single-region production, with 14 daily restore points as the recovery path. Stop a dev or staging database when it is idle and costs drop to zero; only retained storage continues billing.

When uptime or read throughput matters more, enable clustering from the dashboard. ProxySQL sends SELECTs to replicas and writes to the primary, so your app keeps one endpoint. Add nodes or change replication modes and that endpoint stays the same, with no connection-string rewrites or redeploy.

Clustering adds:

Automated replication

Enable replication from the dashboard and the platform creates replica nodes, configures replication, and connects ProxySQL automatically.

Automated failover

ProxySQL detects a failed primary and redirects traffic to a healthy replica within seconds.

Read scaling

Spread SELECT queries across replicas without application-level sharding.

Zero-downtime topology changes

Add nodes or switch replication modes while the database keeps serving traffic. New nodes are discovered and added to the cluster automatically.

Compare clustering topologies and replication modes

Find the right database pattern for your app

Most applications fit one of these patterns. Start here, then narrow it down from there.

Relational / transactional

Web apps, e-commerce, SaaS, and any workload built on structured tables and transactions. All four SQL engines support clustering with automated failover through ProxySQL.

Caching & sessions

Redis for in-memory reads. Reduce query load on your primary SQL database and speed up response times. Add Pub/Sub or Streams for message brokering.

Search & analytics

OpenSearch for full-text search, log aggregation, and analytics dashboards. Use it with Logstash and Beats for observability pipelines.

Explore clustering options

Common Questions

Which database engines can I deploy?

SQL: MySQL, MariaDB, PostgreSQL, and PerconaDB. NoSQL: Redis, OpenSearch, and Couchbase. All are available from the control panel topology wizard.

Are backups included?

Every database gets 14 days of daily restore points. 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, 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?

Access phpMyAdmin or pgAdmin for database management. Use SSH or the file manager for direct config edits.

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.

Start your 14-day free trial

Deploy in minutes with managed autoscaling and clustering built in.

No credit card required.