Run MySQL 8 as a managed service: reachable from your app, your laptop, and your CI pipeline over an encrypted connection - with automated backups, point-in-time recovery, and query observability built in.
Connect from the application server, a teammate's laptop, or CI. You choose private-only access or a public endpoint with an allowlist.
Place the database in the same region as your app and keep port 3306 off the public internet.
For laptops, CI, and external tools. Only approved IPs can reach the port, and SSL is mandatory.
Every connection is encrypted in transit. Certificates are verifiable, not self-signed.
Your databases, users, and grants are yours. We manage the server, storage, backups, and failover - you keep full SQL control.
Patching, backups, failover, and monitoring are handled. You still get root-level SQL control over your own schema.
Daily snapshots with 14-day point-in-time recovery. Restore to a new instance without overwriting production.
Add a replica for reporting or read-heavy endpoints without duplicating the write path.
Built-in pooling keeps thousands of application connections from exhausting MySQL.
Find the queries that hurt. Sort by duration, rows examined, and frequency.
CPU, memory, connections, IOPS, replication lag, and disk growth in one dashboard.
Add vCPU, memory, or storage without a manual migration or a maintenance window.
Keep the database alive when an app server is rebuilt, scaled, or replaced. That is the point of a remote DB.
Multi-tenant apps that need a stable database endpoint while app servers scale.
Run heavy read queries on a replica instead of slowing down checkout.
Move the WordPress database off the web server for better isolation and backups.
Give every preview environment a real MySQL instance, then tear it down.
Moving an existing schema is a four-step job. The old database stays untouched until the new one has been verified.
Take a consistent logical backup with mysqldump --single-transaction so writes are not locked during the export.
Import into the new instance. Charset, collation, and SQL mode are matched before the import starts.
Compare row counts and checksums table by table. Test the application against the new connection string.
Change one environment variable. Keep the old database read-only until you are satisfied, then retire it.
We can run the migration for you. For larger databases, we schedule a maintenance window, take a fresh backup, and compare row counts and checksums before the application is switched.
Slow queries, connection pressure, and replication lag are visible in the dashboard - not discovered by a customer at checkout.
Every instance ships with automated snapshots and point-in-time recovery. Restores go to a new instance, so you can inspect the data before switching production over.
Choose the compute and storage you need. Query volume is not metered, so a busy month does not create a second invoice.
Pick vCPU and memory for your workload. Scale up without a migration window when traffic grows.
NVMe-backed storage billed per GB. Growth is visible in the dashboard before it becomes a problem.
Daily snapshots and 14-day PITR are included. Extended retention is available as an add-on.
Need a specific size, replica, or migration plan? Talk to an engineer.
Your database sits behind a network boundary. It answers your application servers, refuses unencrypted connections, and keeps encrypted backups in a separate failure domain.
Private networking is the default: your database only answers the application servers you attach to it. If you need a public endpoint, it is restricted to an IP allowlist and refuses plaintext connections. Backups and PITR logs are encrypted in a separate failure domain, and restores never overwrite production.
Port 3306 is not exposed unless you deliberately enable the public endpoint. Application servers connect over a private link.
The public endpoint only accepts approved IPs, and plaintext connections are rejected. Certificates can be verified.
AES-256 at rest and per-application users with only the grants they actually need.
Connection logs, failed-login visibility, and automated MySQL security releases applied by us.
Daily automated snapshots, 14-day point-in-time recovery, and on-demand snapshots before a migration. Restores go to a new instance, so you can inspect the data before switching production.
Feedback from teams that moved their database out of the application server.
Access, backups, scaling, and what stays in your control.
Still have questions? Our security team is available 24/7.
Contact Support