Loading
Monthly upkeep of production systems: updates, security patches, monitoring, incidents and a written report.
Software that is finished still rots: dependencies collect vulnerabilities, runtimes reach end of life, certificates expire, a queue quietly fills up. Maintenance is a standing engagement to keep a live system current and observed: dependency and runtime upgrades, security patches, monitoring and alerting, incident response, and the small evolutions that would otherwise wait for a project. Every month you get a written report of what changed and what to do next.
Dependencies, runtimes, certificates, backups, alarms and access, listed and dated.
What is covered, what counts as an incident, how work is requested and prioritized.
Scheduled updates, patches and checks, deployed and reviewed like normal changes.
A written monthly report, then the plan for the period that follows.
Agreed per client and written down: usually dependency and runtime updates, security patches, monitoring, incident response, backup verification and a budget for small evolutions.
Any request gets a reply within 24 hours. Priority and handling for incidents are set in the agreement, based on what the system does and when it matters.
Yes. It starts as a takeover: read the code, document how it deploys and runs, fix what is dangerous, then move to the regular cycle.
It depends on the size of the system and the scope you want covered, so we quote after the inventory. A small service and a marketplace are not the same job, which is why there is no rate card here.
Tell us what you are working on. Reply within 24 hours, one-page diagnostic within 48.