Managed MySQL
the engine your application already speaks
For what already runs on MySQL and you're not going to rewrite. You get a dedicated endpoint with TLS verify-ca, pick the version at order time, and manage databases and users from the panel — never seeing the VM.
$ mysql --ssl-mode=VERIFY_CA --ssl-ca=truocloud-ca.pem \
-h db-7f3c.node3.my.truo.cloud -P 25506 -u app -p app
mysql>
✓ connected, TLS verify-ca
VERSIONS
8.4 or 8.0
You pick the version at order time. MySQL 8.4 by default.
BETA
No managed backups
In this first version you handle backups yourself. We say it here because it changes how the service is run.
CONNECTION
Dedicated endpoint
Host and port exclusive to your service, reachable from any network, with no tunnel or VPN.
ENCRYPTION
TLS verify-ca
A per-service certificate you download from the panel, to validate the server on connect.
PLANS
The same sizes and the same price as PostgreSQL
RAM, CPU and disk fixed per plan, storage included. We don't charge differently by engine because the market doesn't either.
Managed MySQL is in beta: it doesn't include managed backups yet and it sits outside the availability commitment. If you need automatic backup today, use managed PostgreSQL.
db-2
Development and testing
$14.99
- •2 GB assigned RAM
- •2 vCPU
- •40 GB NVMe
- •Dedicated endpoint + TLS verify-ca
- •Managed backups: not yet
db-6
Production
$37.99
- •6 GB assigned RAM
- •4 vCPU
- •95 GB NVMe
- •Dedicated endpoint + TLS verify-ca
- •Managed backups: not yet
db-12
Demanding workloads
$73.99
- •12 GB assigned RAM
- •6 vCPU
- •190 GB NVMe
- •Dedicated endpoint + TLS verify-ca
- •Managed backups: not yet
db-24
High volume
$142.99
- •24 GB assigned RAM
- •10 vCPU
- •360 GB NVMe
- •Dedicated endpoint + TLS verify-ca
- •Managed backups: not yet
Prices in USD per month, with storage included in the plan. The annual cycle is 25% cheaper, two years 30% and three years 35%. MySQL is in beta: same price as PostgreSQL, but no managed backups yet and outside the availability commitment.
VERSIONS
You pick the version
Chosen at order time. We apply minor patches inside the version you picked.
Moving between versions is a data migration, not a button: if you need to move up, write to us and we plan it with you.
| Version | When to pick it |
|---|---|
| MySQL 8.4Default | The default and the recommendation for new projects. |
| MySQL 8.0 | To match the version of a server you already run in production. |
What you get today, and what you don't
MySQL runs on the same control plane, the same panel and the same infrastructure as PostgreSQL. What's missing is the backup engine, and until it exists the service is sold as beta.
If automatic backup is a requirement for your project, managed PostgreSQL includes it today: on-demand copies with 7-day retention, stored off the server. See managed PostgreSQL
- •
Yes: endpoint, TLS and panel
Dedicated endpoint, a per-service certificate, and databases and users managed from the panel.
- •
Yes: patching and monitoring
Engine maintenance and visibility into the service's state are on us.
- •
No: managed backups
The automatic backup PostgreSQL does have doesn't exist on MySQL yet. Today you handle it.
- •
No: availability commitment
While in beta, MySQL sits outside the availability commitment that covers the rest of the catalog.
USE CASES
When it makes sense
Managed MySQL is for what already exists on MySQL, not for starting from scratch on it.
Applications already on MySQL
Move the database to a managed service without touching the code or the schema.
Getting off your own server
Stop maintaining the engine, the patches and the certificates on a VM you administer.
Separating database from app
The database stops competing for CPU and memory with the web service running next to it.
Staging environments
A clone of your production with the same engine and version, without standing up another server.
PHP frameworks and ORMs
Laravel, Symfony, Django, Prisma or Sequelize connect with their usual configuration.
Internal services
Team tools and admin panels that were born on MySQL.
It's MySQL, with the tools you already use
It runs the upstream engine, so migrating is a dump and a restore: no custom dialect and no proprietary client.
- •
The clients you already use
The mysql client, MySQL Workbench, DBeaver, TablePlus and any driver that speaks the protocol.
- •
Migrate with mysqldump
Dump your current database and restore it against the new endpoint, with no tool in between.
- •
Reachable from any network
The endpoint is public and dedicated, so your application doesn't have to run on TruoCloud to use it.