Runbooks we use ourselves
Deploy, backup and restore, rollback, incident response and disaster recovery — the same playbooks we use on our own production platform.
Your software, kept running — by a team that runs its own
We fix bugs, maintain, monitor and patch your systems, and look after your cloud. Choose per-ticket support, pay for actual hours, or 24/7 operations with an SLA. We run MaxStack Platform in production ourselves, and bring the same runbooks to your system.
For businesses with software in daily use, a small or no IT team, or a previous vendor who is slow — or gone.

No one to call when it breaks
An issue stops sales or operations, and no one is ready to respond.
Fixes that break something else
A quick patch in one place causes a new problem somewhere else.
The original vendor is gone
The system works today, but no one knows the code well enough to change or rescue it.
Calm, controlled support with clear reporting — no surprises.
Deploy, backup and restore, rollback, incident response and disaster recovery — the same playbooks we use on our own production platform.
We reproduce the issue first, make the smallest safe change and retest around it.
Monitoring, backups and security patches catch problems before your users do.
Issues are triaged by business impact, with response times agreed in your SLA.
Per ticket, or only the hours we actually work — with a monthly report.
Every fix comes with the cause, the change and how to prevent it next time.
Everything it takes to keep your software healthy after launch.
From first contact to steady, reported support.

Step 1
If we didn’t build the system, we start with a System health check so we know what we’re taking on.
Step 2
Together we set the scope, priorities, response times and how you’re billed.
Step 3
We set up access, monitoring, backups and runbooks for your system.
Step 4
Tickets are triaged, reproduced, fixed safely and verified before release.
Step 5
You get a report of the work done and the hours used, plus what we recommend next.
Three ways to work with us. Prices and response times are agreed in your SLA — or quoted after the health check if we’re taking over your system.
For occasional issues
Quoted per ticket
Start any time
Monthly hours for fixes and maintenance
Hours agreed per month
Monthly report
For systems that can’t go down
Quoted by SLA
Response times in your SLA
If the system needs to change — new features, upgrades, a rebuild — that’s Development. If it needs to keep running well — fixes, maintenance, monitoring, patches — that’s Operations. You can use both.
Yes. We start with a System health check so we both know the risks, then agree an SLA. We’ll need access to the source code, the servers and any documentation that exists.
It depends on your system and the level of cover you need. Prices and response times are agreed in your SLA before we start. If we’re taking over your system, we quote after the health check.
We agree the hours per month with you, and you only pay for the hours we actually work. Each month you get a report of what was done and the hours used.
Tell us what you run and what’s worrying you — we’ll suggest the right level of support.