Maintenance and support

Planned technical support for websites and business-critical applications

Support works when priorities, response expectations and system ownership are explicit. Choose planned maintenance, a retained support allocation or a separately scoped incident response.

Support matched to operational risk

Maintenance

Dependency updates, backups, certificate checks, monitoring and small planned improvements.

Retained support

A reserved monthly allocation for known systems, with agreed response targets and a prioritised queue.

Incident response

Time-critical investigation for outages or credible security events, subject to availability and explicit emergency rates.

Urgency is assessed by impact, not message volume

A production outage, active compromise or material data risk is treated differently from an urgent content change. The support agreement defines severity, communication and escalation before an incident occurs.

  • Known systems and responsible contacts
  • Severity definitions and target response windows
  • Included hours and out-of-scope rates
  • Backup, rollback and incident documentation

Discuss support coverage