Skip to content
Develozy

Website & app maintenance

The unglamorous work that decides whether a launch is still working in year three.

Overview

A site is not finished at launch; it starts decaying at launch. Dependencies drift, certificates lapse, a framework major lands, Google changes what it measures. Maintenance is a standing commitment to keep the thing fast, patched and online — not a retainer that quietly bills for nothing.

What you get

  • Security patching and dependency upgrades
  • Uptime and error monitoring, with someone actually on the alerts
  • Core Web Vitals tracked over time, not just at launch
  • Content and copy updates within the agreed monthly allowance
  • Backups and a tested restore path
  • A plain-language report each month — what changed and why

What this isn't

  • Not a hosting reseller markup — you own your infrastructure accounts
  • Not an open-ended feature retainer; new builds are scoped separately

The problem

The problem Website & app maintenance solves

Nobody notices maintenance until the certificate expires on a Saturday, or a dependency with a published CVE has been sitting in production for eight months, or the contact form has been silently failing since a provider changed an API. By then the cost is not the fix. It is the enquiries that never arrived and nobody counted.

How it runs

Four phases, and what you get from each.

Monthly, on a 12 / 24 / 36-month term

  1. Audit

    We inventory what you actually have: dependency ages and known vulnerabilities, hosting and DNS, where the secrets live, what monitoring exists, and what breaks if one person leaves.

    Written audit with a prioritised risk list

    3–5 days

  2. Stabilise

    Clear the backlog before starting the routine: patch what is exploitable, fix what is already broken, add uptime and error monitoring, and prove the backup can actually be restored.

    Patched build, monitoring live, tested restore

    1–2 weeks

  3. Routine

    A monthly cycle of dependency upgrades, security patching, Core Web Vitals tracking and your content updates. Alerts route to a person, not an unread inbox.

    Monthly plain-language report of what changed and why

    Ongoing

  4. Review

    Quarterly, we look at the trend rather than the month: performance drift, upcoming framework majors, and whether anything should be rebuilt rather than maintained further.

    Quarterly review and a costed recommendation

    Every 3 months

Levels

Three builds, not one price.

  • Essential

    A brochure or marketing site that must stay online, current and secure.

    • Security patching and dependency upgrades
    • Uptime monitoring and SSL renewal
    • Backups with a tested restore path
    • 1 content update per month

  • Standard

    A site your business actively runs on, with content and campaigns changing.

    • Everything in Essential
    • Error tracking with triage, not just alerts
    • Core Web Vitals tracked month over month
    • Priority queue for urgent changes
    • Monthly written report

  • Critical

    A product or platform where downtime costs real money.

    • Everything in Standard
    • Uptime SLA with a defined response window
    • Named handler who knows your stack
    • Staging environment for every change
    • Quarterly architecture review

Where we've done this

Shipped, not theoretical.

Questions

Asked before, answered here.

Also relevant

Rarely bought alone.

Have a project in mind? Let's get to work.

Our team is here to deliver tailored solutions that drive results. Tell us what you are building and we will come back with a route to it.

Let's talk