Managed MySQL with failover and point-in-time recovery.COMING SOON
A database you do not have to babysit: MySQL 8 on NVMe, a standby that takes over automatically when the primary fails, continuous backups you can restore to any moment in the retention window, and metrics in the same console as your servers.
What happens when the primary dies.
- 01
Your app uses one endpoint
A hostname that always points at the current primary. Your configuration never changes.
- 02
A standby replicates every change
In the same region, on separate hardware, kept current continuously.
- 03
The primary fails
The standby is promoted automatically and the endpoint follows it. Your application reconnects and carries on.
- 04
Continuous backups
Every change is captured, so you can restore the database to any moment in the retention window, into a new instance, without touching the running one.
- 05
Observed in the console
Connections, queries, storage and replication lag on the same page as your servers, with the same API.
Boring, replicated, recoverable.
MySQL 8 on NVMe
Current MySQL on the same NVMe class as our compute, tuned for the instance size.
COMING SOONReplica promoted automatically
A standby in the same region takes over when the primary fails; the endpoint does not change.
COMING SOONRestore to a moment
Continuous backups let you restore to any point in the retention window, into a new instance.
COMING SOONE-commerce
An order table that survives a failed host without anyone noticing.
Multi-tenant applications
One managed database per customer or per region, provisioned from the API.
Undo a bad migration
Restore to the minute before the deploy, compare, and move on.
What can I use today?
MySQL on any cloud server, or on Hosting plans with phpMyAdmin included. Platform databases at Joy are already backed up hourly and replicated to a second region; the managed product brings that to your databases.