The web's workhorse, watched 24/7.

Managed MySQL for commerce and content platforms — HA pairs, point-in-time restore and read replicas when traffic grows.

HA pairsPITRRead replicas

Talk to us All Databases

Capabilities

MySQL at platform grade

Enterprise-ready MySQL with built-in resilience, security and performance at every layer.

Automatic failover

HA pairs promote in seconds when a node misbehaves.

Seconds, not pages →

Point-in-time restore

Binlog-based recovery to the minute, drill-verified.

Binlog to the minute →

Read scaling

Replicas absorb read-heavy traffic without app rewrites.

Replicas for the read path →

Version upgrades

Minor and major upgrades planned and executed by us.

Planned, tested, reversible →

Performance tuning

Slow queries and parameters tuned from live telemetry.

Latency watched for you →

Private endpoints

Databases live on your virtual networks only.

Never internet-facing →

Encrypted connections

TLS enforced with per-database credentials.

Data encrypted in flight →

Schema-safe releases

Online DDL guidance keeps deployments non-blocking.

Deploys without locks →

Proxy & pooling

Connection pooling absorbs bursty application fleets.

Thousands of clients, calmly →

Monitoring included

Metrics and alerts flow into Obersva as standard.

Nothing extra to wire →

Resilient by designBuilt to continue, even when hardware fails.

Predictable performanceConsistent I/O for the apps that matter.

Efficient at scaleOne flat fee. Scale without waste.

Backed by humansReal experts. Real support. Every time.

Compare the shapes

Single, highly available, or read-scaled

Operated MySQL in every shape — the difference is how much downtime and how much read traffic you can absorb.

ProductionEdgeComing soon

SHAPE 01

Single Instance

Managed and backed up

One instance with automated backup, patching and point-in-time restore — sized for development, staging and internal applications.

Best for

Dev & stagingInternal appsSmall CMS estates

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

Standard4 vCPU · 16 GB RAM · PITR 7 daysSign in →Standard Plus8 vCPU · 32 GB RAM · PITR 14 daysSign in →CustomAny shape, storage and retention windowSign in →

SHAPE 02Production default

HA Pair

Commerce-grade uptime

Primary and standby across zones with automatic failover — for storefronts and platforms where minutes of downtime cost orders.

Best for

Commerce platformsCMS estatesSaaS backends

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

HAPrimary + standby · automatic failoverSign in →HA PlusCross-zone standby · PITR 30 daysSign in →CustomAny topology and failover policySign in →

SHAPE 03

Read-Scaled

Replicas for peak traffic

HA plus read replicas so catalogue browsing, search and reporting never contend with checkout writes.

Best for

Peak-season commerceRead-heavy APIsReporting

Where it runs

Dubai AZ1RiyadhBahrainMumbaiDubai AZ2Nairobi

Plans

ScaledHA pair + 1 read replicaSign in →Scaled PlusHA pair + 3 read replicas · proxy routingSign in →CustomAny replica count and routing policySign in →

Two ways to run it

Managed instance, or database operations

Both include patching, backup and monitoring — the difference is who owns query performance.

Managed InstancePlatform levelWe run the engine, replication and backups; your team owns schema and queries.

Patching and minor upgrades handled

Tested point-in-time restore

Replication health monitored

Best for:Teams with database skills

Explore Managed Instance plans

Database OperationsEngine levelDatabase Operations tunes queries and indexes, plans capacity and runs major upgrades with you.

Slow-query and index review

Peak-season readiness planning

Major-version upgrade programmes

Best for:Commerce estates with seasonal peaks

Explore Database Operations plans

Who decides, who runs it

What each group gets from MySQL

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“The storefront database is somebody's job”

The engine behind revenue is monitored and operated to an agreed standard rather than watched by whoever is available.

GovernedSovereignPredictable

FAQs

Which MySQL versions do you run?

Current supported major versions, with upgrades planned around your release calendar.

How is failover handled?

HA shapes promote the standby automatically, typically in seconds, and alert your team with the reason.

Can we add replicas for a peak and remove them after?

Yes — replica counts are adjusted at re-baselines you approve, so seasonal shapes are planned rather than improvised.

Do you help with slow queries?

Under Database Operations, yes — query and index review is part of the service rather than a consulting project.

Is the endpoint public?

Only if you ask. By default instances sit on your virtual networks with private endpoints.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together