Managed MySQL database and MariaDB for enterprise workloads
MySQL and MariaDB with the replication model, backup method and upgrade path set for your estate: dedicated clusters in OSStend's cloud, inside your own cloud account, or co-managed in your data center, run 24/7.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ: 160+ customers, 10+ years
- ✓24/7 on-call engineers
An example design file for a billing service, with illustrative values:
# Managed MySQL service: mysql-billing engine: mysql topology: primary + 1 replica target: gcp/dedicated backups: pitr monitoring: included on_call: 24/7
MySQL hosting from OSStend is for MySQL and MariaDB estates that no longer fit a standard plan. Engineers choose the replication model, from asynchronous replicas to a Group Replication cluster, plan the climb to a supported version, migrate you in by replication with zero downtime as the goal, and run it 24/7.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
What OSStend tailors for MySQL
Each MySQL or MariaDB estate is designed around its replication model, its engine and version path and its backup method, with sizing taken from measured load. The design is written down and signed off before anything is built.
- Backups and point-in-time recovery
- Metrics to your Prometheus or Datadog
- AceMQ engineers on call 24/7
| Area | Set for your workload |
|---|---|
| Size and shape | Instance size, storage and replica count chosen from measured load: the InnoDB buffer pool against the working set, redo and binary log volume, and how many read replicas the application fans out to. |
| Topology | MySQL replication is asynchronous by default. Semisynchronous replication makes the source wait for at least one replica to acknowledge each transaction, and it reverts to asynchronous if none answers in time. InnoDB Cluster combines Group Replication, MySQL Router and MySQL Shell, needs at least three instances and fails over automatically. The design picks the model that fits your recovery target and write-latency budget, with zones and hybrid links where the workload needs them. |
| Engine and configs | MySQL or MariaDB, set per estate, with the server and InnoDB settings the workload needs and the character set and collation your data was written in. |
| Backups and recovery | Point-in-time recovery restores a full backup and then brings the server forward to the moment you choose. The design sets the backup tool, for example Percona XtraBackup, an open-source hot backup that keeps the database available, the binary log retention and the restore test schedule. |
| Versions and upgrades | MySQL does not let an upgrade skip an LTS series: 5.7 goes to 8.0 first, and only then to 8.4. Upgrades are planned around your change windows and never forced. |
| Where it runs | Dedicated clusters in OSStend's cloud, a VPC in your AWS, Azure or Google Cloud account, or hosts in your data center on Kubernetes or OpenShift. Air-gapped sites are covered too. |
| Monitoring | Metrics and alerts forwarded to your Datadog, Dynatrace, Splunk or Prometheus. On-call engineers watch replication lag, Group Replication member state where it is used, and the age of the last good backup. |
There is no fixed menu here: the settings, plugins and cluster size your workload needs are written into the design you sign off before anything is built, and that design is what OSStend runs.
The MySQL version clock has already moved. The mysql.com notice says Oracle's end of life for MySQL 8.0 was April 2026, with MySQL 8.0 now covered only by Sustaining Support, and it encourages users to upgrade to MySQL 8.4 LTS or 9.7 LTS (checked 9 Nov 2026). On 8.4 the mysql_native_password plugin is disabled by default and removed in 9.0.0, so accounts that still use it are moved to another plugin before the upgrade. MariaDB keeps its own calendar: community binaries for 10.6 ended on 6 July 2026, 10.11 runs to 16 February 2028, 11.8 to 4 June 2028 and 11.4 to 29 May 2029 (MariaDB maintenance policy, checked 9 Nov 2026).
Managed MariaDB: MariaDB cloud hosting next to MySQL
OSStend runs MariaDB as a managed database on the same terms as MySQL: a cluster designed for your workload, in our cloud, your cloud account or your data center, with the engine and version fixed in the design. MariaDB and MySQL share a heritage but are no longer interchangeable, so the engine is chosen on purpose, not by default.
| Question | What MariaDB documents | What it means for the design |
|---|---|---|
| Is MariaDB a drop-in replacement for MySQL? | MariaDB says versions up to 5.5 were drop-in replacements for the matching MySQL version, that 10.2 to 10.4 are limited drop-in replacements for MySQL 5.7 as far as InnoDB is concerned, and that differences keep growing with each version (MariaDB KB, checked 17 Nov 2026). | A move between the two is tested against your schema and queries before the engine is fixed. |
| Where do they differ most? | MariaDB stores JSON as text and compares it as strings, group replication is incompatible with Galera, and MariaDB GTIDs are not compatible with MySQL 5.6 (same page, checked 17 Nov 2026). | Replication and JSON-heavy workloads get an explicit check in the design review. |
| Which versions does the design target? | Community binaries for MariaDB 10.6 ended on 6 July 2026, 10.11 runs to 16 February 2028, 11.8 to 4 June 2028 and 11.4 to 29 May 2029 (MariaDB maintenance policy, checked 9 Nov 2026). | A 10.6 estate gets a target version and a date on your change calendar. |
How we compared: each row quotes only what MariaDB publishes, with the date we read it. For the MySQL side of the choice, see PostgreSQL vs MySQL. When a standard MariaDB plan from a cloud provider holds your database, it will cost less than a designed cluster.
Where turnkey MySQL services stop
Amazon RDS for MySQL documents what it holds back: no shell access to the instance, restricted access to some system procedures and tables, and an administrator account that works through a role. A workload that needs host-level tuning or its own backup tooling has to look elsewhere.
| Area | What a plan fixes | What OSStend designs instead |
|---|---|---|
| Host access | RDS does not provide shell access to DB instances and restricts some system procedures and tables (checked 9 Nov 2026). | Operator access for OSStend engineers on the cluster, so file-level backups and operating system tuning can be part of the design. |
| Privileges | From 8.0.36 the RDS administrator gets rds_superuser_role, activated with SET ROLE. Earlier versions get a fixed list of privileges (checked 9 Nov 2026). | Grants shaped to the workload and agreed in the design. |
| Version path | A plan follows the provider's own schedule for leaving MySQL 8.0 and for offering 8.4 or later. | The LTS climb, 8.0 to 8.4, rehearsed on a copy and run on your change calendar. |
| Where it runs | One provider's cloud: AWS for RDS, Google Cloud for Cloud SQL. | OSStend's cloud, your cloud account or your data center, on one contract. |
Plan menus differ by provider and change over time. The Amazon RDS alternative page compares documented limits with sources and dates.
Change data capture from MySQL: Debezium on the binlog
Debezium reads the MySQL binary log and publishes each row change as an event, so other systems can follow the database without polling it. OSStend runs that pipeline next to the database.
The managed Debezium service runs Debezium on Kafka Connect, MSK Connect or Debezium Server, with the binlog retention, offsets and upgrades handled by the same engineers who run MySQL. Background: change data capture explained.
Design. Move. Run. for MySQL
For MySQL, an engineer designs the replication model and the version path and you sign it off, OSStend builds the replica and owns the cutover, and named engineers then run the cluster 24/7.
Design
An engineer reviews your workload (query patterns, data size and growth, recovery targets, current version and where it must run) and writes the cluster design: engine, size, replication model and version path. You sign it off before anything is built.
Move
OSStend runs the migration off RDS, Cloud SQL or a self-run server and owns the cutover. The method is replication: the new cluster follows the source, and both sides stay live until you switch. A 5.7 source climbs through 8.0 on the way to 8.4, because MySQL allows no shortcut. Zero downtime is the plan.
Run
Named engineers run it 24/7: backups and binary log retention, upgrades on your calendar, replication lag and Group Replication health, scaling and incident response, with an SLA written into your contract.
Deployment and service levels
MySQL runs dedicated in OSStend's cloud, inside your own cloud account, or co-managed in your data center. The first two are fully managed; the third is co-managed, with OSStend engineers operating the database on infrastructure you own.
Dedicated in OSStend's cloud
Single-tenant MySQL or MariaDB clusters in the Google Cloud or AWS region you choose, with the primary and its replicas in separate zones.
Fully managedIn your cloud account
MySQL or MariaDB inside your VPC on AWS first, then Azure and Google Cloud, with the instances, the storage bill and the security boundary left in your account.
Fully managedIn your data center
Hosts you own, on Kubernetes, OpenShift or bare metal, air-gapped sites included, with OSStend engineers operating the database through an operator on your cluster.
Co-managed
Fully managed MySQL clusters carry an uptime commitment. A data center deployment carries a 24/7 response-time commitment instead, because you own the hardware. The service levels page sets out the tiers, and deployment shows each option in detail.
Uptime and response figures are set per plan and written into your contract. AceMQ, which operates OSStend, sets its support response targets from 15 minutes, by plan.
Proof from AceMQ's operating record
The replication, backup and upgrade work for MySQL is done by AceMQ's engineers. AceMQ operates OSStend with 160+ customers, 10+ years of running open-source infrastructure and engineers on call 24/7, matching what acemq.com says.
Customer names stay private unless AceMQ has written permission to share them, so the MySQL record here is anonymous. If you want a reference with a similar replication model, ask for it in the 45-minute review.
Pricing for managed MySQL
Managed MySQL is priced from four drivers: the replication model, the cluster size, the SLA tier and where it runs. An engineer prices the specific design after a workload review, with no free tier or card sign-up for MySQL.
- Replication model
- asynchronous replicas, semisynchronous replication or a Group Replication cluster each ask for a different number of instances.
- Cluster size
- instance size, storage and the number of replicas.
- SLA tier
- the uptime commitment on a fully managed cluster, or the 24/7 response-time commitment on a co-managed one.
- Where it runs
- OSStend's cloud, your cloud account or your data center, which sets who carries the infrastructure bill.
Tell the engineer the MySQL or MariaDB version, data size, binary log volume and where it must run, and the quote is for that cluster instead of a plan size.
The pricing page explains how the model applies to every engine.
When to contact OSStend, and when not to
Contact OSStend when your MySQL or MariaDB has to keep running while it changes version, topology or location, and a plan will not let you. When the plan you have already does the job, stay on it.
Contact us if
- ✓Your MySQL has outgrown a plan: more storage, more replicas or settings the plan does not expose.
- ✓You need MariaDB, or a version held on your own upgrade calendar.
- ✓You are still on 5.7 or 8.0 and need a rehearsed climb to a supported version.
- ✓You must run in your own cloud account, in more than one cloud or in your data center.
- ✓You are leaving Amazon RDS or Cloud SQL and want the migration run for you.
- ✓You keep your own MySQL and want the DBA work run for you: see database administration services.
Not a fit if
- ✕A standard RDS or Cloud SQL plan holds your MySQL without strain, and the plan is cheaper than a designed cluster.
- ✕You want a free tier, or to sign up with a card. For MySQL, OSStend begins with a conversation with an engineer.
- ✕You are choosing an engine for a new application and have not decided yet: compare it with managed PostgreSQL first, and read PostgreSQL vs MySQL. For MySQL against MariaDB, read MySQL vs MariaDB.
Questions about hosted and managed MySQL
These are the questions engineering and platform teams ask most before moving MySQL to a managed service.
What is a managed MySQL database?
A managed MySQL database is a MySQL server that a provider operates for you, including backups, replication, failover, patching and 24/7 incident response. OSStend's version is a dedicated cluster whose replication model and version path are designed for your workload, covering both MySQL and MariaDB.
What is the difference between hosted MySQL and managed MySQL?
Hosted MySQL, also sold as MySQL hosting, gives you a server or database instance to run yourself. Managed MySQL adds the operations: backups with binary log retention, replication monitoring, failover, patching and 24/7 on-call engineers. OSStend settles the topology first instead of selling a fixed plan.
Can managed MySQL run in my own cloud account?
Yes. The cluster sits in your VPC on AWS first, then Azure and Google Cloud, and the instances, the storage and the security boundary remain yours. In a data center the service is co-managed on Kubernetes, OpenShift or your own hosts.
Does OSStend run MariaDB as well as MySQL?
Yes. The engine and version are chosen in the cluster design and upgrades follow your change calendar. MariaDB's community binaries for 10.6 ended on 6 July 2026, 10.11 runs to 16 February 2028 and 11.4 to 29 May 2029, so a 10.6 estate needs a target version in the design (checked 9 Nov 2026).
Is MySQL 8.0 still supported?
Oracle's end of life for MySQL 8.0 was April 2026, and the mysql.com notice says users are encouraged to upgrade to MySQL 8.4 LTS or 9.7 LTS (checked 9 Nov 2026). The design sets the target version and a date on your change calendar, and a 5.7 source goes through 8.0 first.
How does failover work on managed MySQL?
That depends on the replication model in the design. With asynchronous or semisynchronous replicas a replica is promoted and the others are repointed to it. With InnoDB Cluster, Group Replication and MySQL Router fail over automatically from three instances. Asynchronous replication can lose the latest transactions on promotion, and the design states what your workload can accept.
How does a move from Amazon RDS or Cloud SQL avoid downtime?
The new cluster is built as a replica of the source and catches up while the application keeps writing to the old side. When lag is near zero and the checks pass, OSStend engineers cut writes over, and the old side stays available as a fallback until you release it. The Amazon RDS alternative page describes the path.
What does managed MySQL cost?
The price follows the replication model, the data size, the SLA tier and where the cluster runs. The pricing page sets out the model, and an engineer prices the specific design after a workload review.
Related pages
- ComparisonPostgreSQL vs MySQL for production workloadsPostgreSQL vs MySQL for production workloads: licence, extensions, JSON, replication and when each fits. Sourced and dated, by a team that runs both.
- AlternativeAmazon RDS alternatives in 2026Amazon RDS alternatives for PostgreSQL and MySQL: where RDS is the better choice, what the alternatives cost, and running dedicated clusters in any cloud.
- Change data captureManaged Debezium: change data capture run 24/7Managed change data capture with Debezium on Kafka Connect or Debezium Server, run 24/7 in OSStend's cloud, your cloud account or your data center.
- GuideChange data capture (CDC): methods and toolsChange data capture explained: log-based vs query-based CDC, the main CDC tools, Postgres CDC and replication slots, and when to pay someone to run it.
- Service levelsService levels: two tiers, a written SLAOSStend service levels: fully managed and co-managed tiers, what each one covers, who is on call and how incidents are handled, with a written SLA for each.
- DeploymentManaged databases: our cloud, yours or on-premManaged databases in OSStend's cloud, your AWS, Azure or Google Cloud account, or your data center. PostgreSQL, Kafka and RabbitMQ, run 24/7 by engineers.
Talk to an engineer about your MySQL workload
45 minutes with an engineer: bring your MySQL or MariaDB version, your replica set-up and your backup method, and the engineer sketches the design.
- ✓A design sketch for your workload, not a plan menu
- ✓A zero-downtime cutover path for what you run today
- ✓A price for that design, after the review