Maintenance & Support

Applications rot when nobody owns dependency updates, certificate renewals, content emergencies, or the 'tiny' feature that blocks marketing. Maintenance is a contracted capacity: hours, response, and a backlog you can see. We patch runtimes, keep Next.js and API libraries current enough to stay secure, and ship agreed small changes without opening a new project every time.

Onboarding an app we did not build starts with a health pass: can we run it locally, are secrets in a vault, is there a pipeline, is backup real. If the app is unsafe to support we say so and price a hardening sprint. We will not sign an SLA on a laptop-only deploy.

Incidents follow the same severity language as our infra support. Application and infrastructure support can be combined when you want one ticket path. Store listings, CMS, and analytics property access are listed in scope so they are not a surprise.

You get a monthly note: what shipped, what is overdue, what should become a project. Maintenance is how a launch remains a product instead of a static artefact. Dependency and runtime updates are scheduled around your freeze calendar, and we will refuse an SLA if the only deploy path is still a laptop and an FTP password from 2019.