Monitoring & incident response
Uptime, performance, and error monitoring with defined response SLAs. You hear about problems from us, with a fix underway.
Service 05
Support & Maintenance
Systems age. Ours are looked after.
Software does not stay finished. Dependencies rot, traffic grows, regulations change, and the person who knew how the deploy works leaves. Our support engagements exist so none of that becomes your emergency: we monitor, patch, and improve your systems month over month, and when something does break at a bad hour, the person answering already knows your stack.
What this covers
Maintenance & updates
Security patches, dependency upgrades, and database care on a schedule, so updates are routine instead of a risky annual event.
Continuous improvement
Reserved engineering hours each month for the backlog: small features, performance work, and the fixes that never quite get scheduled.
Knowledge & documentation
Runbooks, architecture notes, and onboarding docs kept current, so your business is never one resignation away from a crisis.
How it runs
- 01
Take stock
A technical audit of the systems entering support: risks, missing monitoring, and anything one bad day away from an outage.
- 02
Stabilize
The first weeks go to closing the risky gaps: backups verified, monitoring wired, deploys made repeatable.
- 03
Run
Steady-state operations under SLA, with a monthly report you can read in five minutes: what happened, what we did, what is next.
- 04
Improve
Reserved hours go to the roadmap, prioritized with you each month, so the system gets better while it is being kept safe.
Where this is grounded
We support what we build, and we take on inherited systems after an honest technical audit. The lab is why we can: having built booking platforms, POS systems, and a patient portal end to end, we know what keeping each of them healthy actually involves. Inherited codebases are welcome; the audit tells us both what we are taking on.
Common questions
Do you support systems that PeoCode did not build?
Yes. Inherited systems start with a technical audit so we understand the risks before committing to SLAs, and so you get a written picture of your own system's health either way.
What do your SLAs look like?
Response times are tiered by severity, with critical incidents answered around the clock on the plans that need it. SLAs are written into the agreement, and our monthly report shows actual response times against them.
What does support and maintenance cost?
Plans are monthly retainers sized by system criticality and reserved engineering hours, from light-touch monitoring to a fractional engineering team. Month-to-month, no long lock-ins.
Can support hours be used for new features?
Yes. Reserved hours not needed for incidents go to the improvement backlog, which you re-prioritize with us each month. Most months, most of the hours build things.
Next step
Talk to us about support & maintenance.
Describe the systems involved and what is not working. A senior engineer reads every inquiry and replies within one business day.