03 - Maintenance & support

Calm operations. Faster support.

Updates, security, performance and incidents - with people you can reach, clear response times and monitoring that raises the alarm before customers call.

SLA Monitoring Hotfix Security

What the package covers

Maintenance is not a parking space for tickets, it is active operations.

Updates & patches

Framework, plugin and OS updates planned and tested. No “surprise updates” on Friday at 5 pm.

Security

Hardening, dependency checks and prompt response to CVEs - prioritised by the risk to your system.

Monitoring & alerting

Uptime, error rates and business checks. Alerts that make sense - and a human at the other end.

Incident & hotfix

Defined SLAs, escalation paths and post-mortems. So the same fault does not come back three times.

An SLA that holds up in daily work

We agree response and recovery times that match your risk - not a marketing slide.

  • A named contact and a backup person
  • Maintenance windows and a change log
  • Monthly status instead of silent tickets
  • Handover from project to operations without losing knowledge

Ideal after go-live

Whether we built the system or are taking over an existing one: we start with a health check and a priority list.

Health check Runbooks On-call

Frequently asked questions

Short and honest - as in the kickoff.

Do you take over systems built by others?

Yes. We start with a health check, risks and a priority list - no matter who built the system.

Which SLAs do you offer?

Response and recovery times that match your risk, in writing. Not a marketing slide.

Do you only work with your own stacks?

Focus: Symfony, Laravel, Shopware, Bitrix, Vue, WordPress and related PHP and JS landscapes.

How do we get started with maintenance?

A short conversation, then a health check with a fixed scope. A project request is enough to start.

Ready for your next release?

Briefly describe what you need - we will come back with a concrete proposal.