Maintenance & Support

Maintenance and support plans

What happens after deployment matters most. Scope-based plans let you hand over as much of your open-source databases and cloud environment (including managed databases) as your team needs.

Plans

Plan options

These examples show how scope differs. Response times, check frequency, number of instances and price are fixed in the contract (SLA) after a diagnosis.

Advisory

Advisory

You have in-house DBAs/developers and want expert review

  • Email and remote technical questions
  • Design and change-plan reviews
  • Version and patch recommendations
  • Periodic status review (by agreement)
  • Cloud account & cost reviews (by agreement)

Standard

Standard

You want a stable operating routine

  • Regular health checks and reports
  • Backup and restore-test verification
  • Performance trend analysis and recommendations
  • Remote analysis and recovery support during incidents
  • Support for planned changes
  • Cloud resource & managed DB checks

Managed

Managed

You want us to run your databases like a dedicated team

  • Run monitoring and alerting
  • Incident response in agreed hours (24×7 option by agreement)
  • Patching and upgrades
  • Capacity and performance management
  • Monthly operations report
  • Cloud infrastructure operations (MSP) can be included
Common to every plan: work logs, approval before change, up-to-date runbooks. One-off projects (diagnosis, tuning, migration, upgrade) are also available.

Health check

Example health-check items

  • Availability: replication state and lag, failover configuration
  • Backup: success, retention, restore-test results
  • Capacity: disk, table and index growth; retention working
  • Performance: top queries, wait events, connection and lock trends
  • Security: account/privilege changes, auth methods, patch level, certificate expiry
  • Logs: errors and warnings, crashes and restarts
  • Versions: end-of-support dates, recommended minor updates
  • Recommendations: actions ranked by risk and priority

Incident

Incident response flow

  1. Intake

    Raised by a monitoring alert or by you; impact assessed

  2. First response

    Service first — failover, restart or load shedding per the agreed procedure

  3. Root cause

    Logs, metrics and change history analysed to find the root cause

  4. Prevention

    Configuration, architecture or process improvements plus an incident report

FAQ

Frequently asked questions

How is plan pricing set?

It depends on the number and size of databases, HA topology, response hours, check frequency and included work. After a diagnosis we provide a quote and a draft SLA.

Do you support managed cloud databases (RDS, Aurora …)?

Yes. Taking into account what the managed service already covers (automated backups, patching etc.), we focus on performance, queries, configuration and cost optimisation.

Is support remote only?

Secure remote access is the default; on-site support can be arranged. Access methods follow your security policy.

Can cloud infrastructure operations (MSP) be part of a plan?

Yes. The Managed plan can include cloud monitoring, patching, backup and cost reviews; scope is chosen from the eight areas on the Cloud MSP page.

Does a migration project roll straight into support?

Yes. After stabilization we move into support based on the migration deliverables (runbook, verification report, handover documents).

Shall we start by reviewing your cloud and databases as they are today?

Tell us your clouds, database versions, topology and concerns, and we will propose an assessment scope and approach.