Managed MySQL on AWS

Managed MySQL, fully run for you.

Dedicated managed MySQL instances on AWS, with point-in-time recovery, ProxySQL pooling, Multi-AZ standby, and direct my.cnf-level parameter control. Bring your own AWS account, or run it in ours. Pay only for what you run, and manage all of it from your AI editor.

Deploy MySQL free See pricing
MySQL 8.0 and 8.4 / AWS, worldwide / From $5/mo / Pay-as-you-go
Powered by AWS

The reliable home for your data.

Amazon Web Services (AWS)
Dedicated instances, run for you

Dedicated PostgreSQL, MySQL, Redis and ClickHouse on AWS, with BYOC into your own account. Multi-AZ on all four, PITR on Postgres and MySQL.

In our AWS account or your own with BYOC. You get AWS uptime and performance; we handle the ops.

What you get

Everything managed MySQL needs.
Nothing you have to babysit.

Instant provisioning

A 5-step wizard: pick MySQL 8.0 or 8.4, cloud and region, instance size and storage, backup policy, review and deploy. Live in minutes.

Point-in-time recovery

Continuous archives let you restore to any minute in the retention window, into a fresh instance, so a bad migration is a recovery, not a disaster.

ProxySQL connection pooling

Managed ProxySQL with connection multiplexing sits in front of your instance. Included, no separate proxy to bolt on.

Multi-AZ high availability

A standby in a second availability zone with automatic failover, for production resilience without manual setup.

Backups and policies

Manual snapshots plus automated backup policies with the retention you choose. Restore on demand.

Duplicate an instance

Spin up an independent copy of a database for testing, staging, or analytics without touching production.

Scaling, scheduled or reactive

Resize on demand, or set start/stop and reactive schedules so you pay for capacity only when you use it.

Direct parameter control

Tune innodb_buffer_pool_size, max_connections, and other core parameters directly. No locked-down parameter groups.

Users, roles, monitoring

Database users with read-only, read-write, or admin roles and password rotation, plus live metrics (QPS, buffer pool hit ratio) and email and Slack alerts.

Locked down by default

IP whitelisting, delete protection, and public access only if you enable it. Your database is not on the open internet by accident.

Encrypted in transit and at rest

Connections use TLS, and your data is encrypted at rest on EBS with AWS KMS keys, so snapshots and backups are encrypted too.

Security and trust

Your data: encrypted, isolated,
and always under your control.

Security is not a separate tier here. Every managed instance ships locked down by default, encrypted end to end, and yours to export or run in your own cloud.

Live system status See how we secure and run your data

Encrypted in transit and at rest

TLS on the wire, AWS KMS on disk. Snapshots and backups are encrypted too.

Single-tenant, isolated hardware

Your instance runs on hardware that is yours alone, not a shared multi-tenant pool.

Private by default

IP whitelisting and delete protection are on. Public access only if you turn it on.

Multi-AZ, PITR, and backups

Automatic failover on every engine, point-in-time restore on PostgreSQL and MySQL, automated backups on all.

Your data stays yours (BYOC)

Run it in your own AWS account. Standard engines, nothing proprietary, yours to keep.

Pick by the job

Two ways to run MySQL
on Selfhost.dev.

Managed instance ยท this page

When the database is the thing

A dedicated instance on AWS that has to stay up, scale, and recover, and that any app can point at, wherever it runs. This is the full control surface: PITR, ProxySQL pooling, Multi-AZ, users and roles, alerts, scaling schedules, and parameter tuning.

Deploy a managed MySQL
One-click ยท in a Project

When it ships beside your app

A Project is Selfhost.dev's managed application hosting: a server we run where you deploy apps from GitHub. Add MySQL to it in one click and it lives on the same server as your code, billed with the server by the hour. Perfect for a WordPress or Laravel stack that wants its database next door.

See how Projects work

Both are provisioned and run for you. The managed instance carries the production machinery (point-in-time recovery, pooling, failover, per-database users and alerts); the Project database trades that depth for one-click simplicity next to your code. Many teams run both, on one bill.

Built for the MySQL world

Your stack already speaks MySQL.
Point it here.

Laravel

The default pairing. Point your production Laravel app at a managed endpoint with pooling and PITR behind it. Deploy Laravel.

WordPress

Give a serious WordPress site a database that backs itself up and fails over. Self-host WordPress.

Legacy and CMS apps

Drupal, Magento, and the long tail of software that expects MySQL, without you running the database host.

Anything with a driver

It is standard MySQL on a standard endpoint. Rails, Django, Node, Go, Java: if it has a MySQL driver, it connects.

Bring your own cloud

Our management.
Your AWS account.

Run managed MySQL inside your own AWS account with BYOC. You keep full ownership of the infrastructure, the VPC, and the data residency, while Selfhost.dev handles provisioning, backups, failover, and upgrades. New to the model? Here's what BYOC is and when it makes sense.

  • ✓ Connect via access keys or an IAM role
  • ✓ Your VPC, your security groups, your region
  • ✓ No enterprise contract required
Transparent pricing
BillingBy the hour, prepaid credits
Tiers and subscriptionsNone
Entry instancefrom $5/mo

Everything pauses at a zero balance, so there is never a surprise invoice. Build your exact bill.

AI-native management

Manage MySQL with AI.
Right from your editor.

Create instances, run backups, tune parameters, configure alerts, and inspect performance from Claude, Cursor, Windsurf, or any MCP client. 150+ MCP tools across 23 modules, every one mapped to a real API call, with destructive operations gated behind explicit confirmation.

Explore the MCP server

Frequently Asked Questions

What is Selfhost.dev managed MySQL?
A dedicated MySQL instance (8.0 or 8.4) on AWS that Selfhost.dev provisions and runs for you: point-in-time recovery, ProxySQL connection pooling, Multi-AZ failover, automated backups, encryption at rest, database users and roles, live metrics with alerts, and direct parameter control. It launched alongside managed PostgreSQL with the same instance surface and the same pay-as-you-go pricing.
Does managed MySQL support point-in-time recovery?
Yes. Continuous archives let you restore to any minute in your retention window. A restore creates a fresh instance, so you can verify the recovered data before switching traffic over, and production stays untouched while you do.
Is connection pooling included?
Yes. Managed ProxySQL with connection multiplexing is included and configured from the console, the MySQL counterpart to PgBouncer on the PostgreSQL side. There is no separate proxy product to bolt on or pay extra for.
Can I tune MySQL parameters?
Yes. You tune core parameters like innodb_buffer_pool_size and max_connections directly from the console, not through a locked-down parameter group. You also manage database users and roles (read-only, read-write, admin) with password rotation.
How much does managed MySQL cost?
Pay-as-you-go, metered by the hour against prepaid credits: the smallest instance works out to about $5/mo all in, and everything pauses at a zero balance. No tiers, no subscriptions, no surprise invoice. Build your exact bill.
Is there a free trial or free tier?
There is no always-free managed MySQL tier, but signing up gets you a $1 welcome credit, no card needed, which runs the smallest managed instance for about 5 days. From there it is pay-as-you-go from about $5/mo, with no subscription to cancel.
Can I run managed MySQL in my own AWS account?
Yes. BYOC runs the instance inside your own AWS account, connected via access keys or an IAM role, while Selfhost.dev handles provisioning, backups, failover, and upgrades. You keep ownership of the infrastructure and data residency.
What is the difference between managed MySQL and MySQL in a Project?
Managed MySQL is a dedicated instance with the production machinery: point-in-time recovery, ProxySQL pooling, Multi-AZ failover, users and roles, alerts, and scaling. MySQL in a Project is a one-click database on the server where your app runs, ideal when the database just needs to sit next to your code. Both are run for you; pick by how critical the data is.
Is it good for WordPress or Laravel?
Yes. Point a WordPress or Laravel deployment at the managed endpoint when the site is serious enough to want backups, PITR, and failover behind it. For smaller sites, the one-click MySQL inside the same Project as the app works too.
How do I migrate an existing MySQL database?
It is standard MySQL, so standard tooling works: mysqldump or a replication-based cutover into your new instance endpoint. Nothing proprietary to convert, and nothing proprietary holding you here later either.

MySQL, fully run for you.
Live in minutes.

Start a database free

Your $1 welcome credit runs the smallest instance for about 5 days.