Skip to main content

Managed database

MySQL operations without the maintenance burden

Assistance operates MySQL and MariaDB environments for teams that need dependable relational storage, predictable support, and a clear line between platform operations and application ownership.

HA options. PITR targets by plan. ProxySQL or managed pooling where appropriate.

Request database assessmentView infrastructure add-ons

Stable MySQL foundations

Provisioning, replication, backups, patching, monitoring, and maintenance are operated inside an agreed add-on boundary.

Migration-friendly

Move from self-hosted MySQL, MariaDB, RDS, Azure Database, or Cloud SQL with a rehearsed cutover plan.

Application-aware operations

We tune capacity, connection handling, backups, and failover around the behavior of your application.

Service playbook

From problem to operating evidence

Main content is structured like a case study: context first, scoped work next, then the operating changes and evidence a team can use after handoff.

Service briefBest-fit use casesWhat Assistance operatesOwnership boundaryDeployment options

Managed MySQL is a supporting infrastructure add-on for teams running web platforms, commerce systems, CMS workloads, internal business applications, and existing MySQL/MariaDB estates that need stronger operations without a disruptive platform rewrite.

Case-study lens

Scoped

Problem, responsibility, and handoff boundaries before implementation.

Evidence

Dashboards, runbooks, reviews, and operating records over borrowed logos.

Outcomes

Conservative summaries focused on observable operational improvement.

EvidenceSection 01

Best-fit use cases

Runbooks, dashboards, reviews, and handoff material make the work auditable.

Use caseWhy Managed MySQL fits
Existing MySQL applicationKeep the database engine your application expects while improving operations and reliability
CMS and commerce platformsFamiliar ecosystem for WordPress, Drupal, Magento, custom commerce, and LAMP-style systems
Business applicationsPredictable relational storage for ERP, CRM, inventory, and order-processing workloads
Legacy modernizationStabilize operations before broader application modernization
Development and stagingCost-effective managed databases on Assistance-operated physical servers
Operating modelSection 02

What Assistance operates

Responsibilities, response paths, and technical changes are made explicit before work starts.

AreaIncluded managed service responsibility
ProvisioningMySQL or MariaDB setup, topology selection, storage sizing, network placement, and secure baseline configuration
ReliabilityReplication, HA/failover design where required, backup policies, restore procedures, and operational runbooks
MaintenancePatch planning, minor version updates, lifecycle guidance, maintenance windows, and rollback plans
PerformanceSlow-query visibility, InnoDB tuning review, connection management, read replica guidance, and capacity review
SecurityTLS, encryption options, user/role recommendations, audit logging options, and credential rotation support
ObservabilityDashboards and alerts for availability, replication lag, storage, connections, locks, and backup health
SupportSeverity-based support and escalation for managed database platform incidents

Your team owns application releases, schema migrations, query patterns, and business data rules. Assistance can review and advise, but application-level correctness and release compatibility remain customer responsibilities unless a broader service is scoped.

OutcomeSection 03

Ownership boundary

Expected changes are framed as practical operating improvements, not unsupported guarantees.

ResponsibilityAssistance ownsCustomer owns
Runtime operationsConfigure, monitor, patch, back up, restore, and operate MySQL/MariaDBApplication use of the database and client compatibility
Schema changesRisk review and rollout advice when scopedMigration scripts, data validation, rollback logic, ORM changes
AvailabilityReplication/failover mechanics inside agreed topologyApplication retry behavior, transaction handling, and deployment timing
Data retentionImplement agreed backup and retention policyLegal/business retention rules and data classification
AccessService accounts, least-privilege guidance, rotation procedureUser approval, identity source, application secret usage
EvidenceSection 04

Deployment options

Runbooks, dashboards, reviews, and handoff material make the work auditable.

OptionWhen to use it
Assistance physical serversDevelopment, staging, CI dependencies, and predictable internal workloads with flat-rate economics
Customer cloud accountProduction systems that must live near application services or inside existing compliance controls
Managed cloud service operationsAssistance operates RDS, Azure Database for MySQL, Cloud SQL, or equivalent service in your account where appropriate
Migration engagementMove from self-hosted, hosted, or cloud-native MySQL into the agreed managed operating model
Operating modelSection 05

Reliability and support model

Responsibilities, response paths, and technical changes are made explicit before work starts.

TopicManaged MySQL approach
AvailabilityTarget and measurement window defined by deployment tier, topology, and support plan
BackupsAutomated backups with retention and point-in-time recovery targets defined during onboarding
FailoverDocumented replica promotion and routing behavior for HA deployments
RecoveryRestore testing or evidence checks included when recovery assurance is required
ResponseP1 response targets are scoped in the support agreement; critical response is available for covered production services
OutcomeSection 06

Onboarding

Expected changes are framed as practical operating improvements, not unsupported guarantees.

Assessment step

1. Workload review

We inspect current database version, size, write/read patterns, slow-query history, replication status, backup posture, downtime tolerance, compliance requirements, and target environment.

Operating step

2. Managed design

Assistance proposes topology, sizing, replication, backup retention, recovery objectives, maintenance windows, access model, monitoring, and migration path.

What changes

3. Build or migrate

We provision the managed MySQL environment and support migration through dump/restore, replication-based cutover, or staged environment promotion depending on risk and downtime tolerance.

What changes

4. Operate

After handover, we monitor service health, replication, storage, backups, and performance indicators. Support paths and runbooks are kept aligned with the live environment.

ScopeSection 07

Supported capabilities

The work is broken into visible capabilities, acceptance points, and handoff artifacts.

  • MySQL 8.0 and supported lifecycle versions by agreement
  • MariaDB for compatible workloads where it is the better operational fit
  • Replication and read replicas
  • ProxySQL or connection-pooling/routing patterns where appropriate
  • Slow-query logging and performance schema review
  • Backup retention and PITR targets scoped by plan
ScopeSection 08

Not included by default

The work is broken into visible capabilities, acceptance points, and handoff artifacts.

  • Rewriting application SQL or business logic
  • Guaranteeing compatibility with unreviewed schema migrations
  • Owning CMS/plugin code or third-party application behavior
  • Unlimited retention, replica count, or cross-region topology outside the plan
  • Compliance certification work that requires a separate audit engagement
Next stepSection 09

Related add-ons

Decision points and common questions are made explicit so follow-up work is scoped cleanly.

Next stepSection 10

Getting started

Decision points and common questions are made explicit so follow-up work is scoped cleanly.

Start with a MySQL assessment. We will review workload, migration risk, backup needs, ownership boundaries, and the support tier required for production. Request database assessment →

Next stepSection 11

Frequently asked questions

Decision points and common questions are made explicit so follow-up work is scoped cleanly.

Can you manage MariaDB as well as MySQL? Yes. We support MariaDB where it is compatible with the workload and a better fit for licensing, features, or existing application expectations.

Can you migrate from RDS or Cloud SQL? Yes. We assess source configuration, data size, replication options, downtime tolerance, and rollback requirements before choosing the migration method.

Do you provide 99.99% uptime by default? No generic uptime promise is applied by default. Availability targets are scoped to topology, provider dependencies, customer responsibilities, and the selected support plan.

Do you tune application queries? We include database-level performance visibility and recommendations. Deeper application query rewrites or schema refactors are scoped as project work.

Can MySQL run on Assistance physical servers? Yes. This is often useful for development, staging, CI dependencies, and predictable internal workloads where flat-rate economics matter.

Ready to get started?

Book a quote review or talk to an engineer.

Get pricing

Pricing

Flexible scopes available. if you need custom terms or bundled service pricing.

Small

€220€/month

Single instance for development or low-traffic applications.

  • Single MySQL instance
  • Daily automated backups
  • Monitoring & alerting
  • SSL/TLS encryption
  • High availability
  • Read replicas
Most popular

Medium

€450€/month

Production workloads with enhanced resources.

  • Enhanced resources
  • Daily backups, 30-day retention
  • Full monitoring stack
  • SSL/TLS encryption
  • High availability
  • Read replicas available

Large (HA)

€900€/month

High-availability with automatic failover and replicas.

  • HA cluster with automatic failover
  • Continuous backups, PITR
  • Advanced monitoring & alerting
  • SSL/TLS + encryption at rest
  • High availability
  • Multiple read replicas

Pricing calculator

Select the services you need to estimate your monthly cost.

Databases

from 250 €/mo
from 220 €/mo
from 450 €/mo
from 550 €/mo
from 350 €/mo

Observability & Ops

from 175 €/mo
from 250 €/mo
from 200 €/mo
from 250 €/mo

Estimated monthly total

0 €/mo

Does not include server infrastructure costs (compute, storage, egress).

Talk to a senior engineer

Need a clearer path for Managed MySQL?

We'll help you understand fit, scope, pricing, and the fastest practical next step for your team.

No obligation • Senior engineer review • Recommendations grounded in your current stack