Maintain
Hosting, support and improvement after go-live.
Go-live is the start, not the end
A system in production is how your organisation gets through the day, and it needs attention to stay that way. Bugs surface, vulnerabilities are published, frameworks reach end of life and cloud bills drift upward. Meanwhile the business keeps moving and asks for changes too small to justify a project.
Operational support
Close support in the first weeks after launch, then ongoing fixes. You talk to the people who built it.
Security and patching
Security review, and dependency upgrades before versions fall out of support.
Performance and hosting
Run on Microsoft Azure and sized to the usage we measure, with the infrastructure defined in code, so rebuilding an environment is a routine run.
Changes and improvements
New reports, integrations and small changes handled alongside support, without a formal project each time.
The integration we built is load-proven to 17 times peak load, and its weekly export of over 1.1 million records reports on every run. Read the integration case study.
How we work on any existing systems you have
What we hold ourselves to
What makes the difference between a support contract and someone who actually looks after your platform.
- The same people
- The same people look after your system month after month, so nobody has to relearn it each time it needs attention. Where we built the platform, that knowledge runs unbroken from the first day of development.
- Someone is watching
- Monitoring and alerting on everything we run, with a clear escalation path and an agreed way of working when something goes wrong. Incidents get written up, fixed, and where possible designed out.
- It gets better
- We review the platform with you regularly and bring our own recommendations to it. Support is a long-term arrangement, and it should leave the system better than it found it.
Before you hand a system over
Will you take on a system you did not build?
Yes. The first step is the same either way: we go through the platform, get monitoring and alerting in place, and give you an honest picture of the state it is actually in.
Who do we talk to when something breaks?
The same people, month after month, so nobody has to relearn your system each time it needs attention. Where we built it, that is the team who built it.
Is support just keeping the lights on?
No. Alongside the monitoring and patching there is planned work: performance, scaling ahead of demand, and the new reports, integrations and small changes your operation asks for, handled without a formal project each time.