Maintenance
The work that stops outages from happening.
Nobody notices maintenance except in its absence. It is the least visible thing we sell and the reason our clients' sites are boring to talk about.
Two layers, one agreement
A website is an application sitting on a server, and both drift out of date on their own. Plugins get security advisories. Operating systems reach end of life. Certificates expire on a date nobody wrote down. None of that announces itself until it breaks something.
We maintain both layers under one agreement, which matters because the usual failure is a gap between two vendors — the web shop says it is the host's problem and the host says it is the application's.
What you actually get
- Updates applied deliberately, tested rather than auto-applied and hoped for.
- Monitoring, so we find out before you do.
- Backups that are verified, not just scheduled — see automated backups.
- A person to call who already knows your setup.
The question worth asking about a retainer
Not what is included. Whether we will still be here, and still paying attention, in year three. Every maintenance agreement is a bet on that, and it is the part nobody can demonstrate with a feature list.
So here is the evidence instead. We ran development for Star City Games for eight years, 2010 to 2018 — their ERP, warehouse systems, storefront, and the API behind their mobile app, and for Foxfire Mountain Adventure Park for fourteen years, 2010 to 2024, across five rebuilds of their site. We have hosted and maintained public election infrastructure for a Tennessee county through election nights where being down was not an option.
Long relationships are the only real proof that maintenance is being done properly, because the alternative shows up as an outage and a new vendor.
It is also the work we care enough about to have built a product around. The monitoring watching your site is Pingura — our own platform, which we build, sell to other people, and run your site on. It watches uptime, APIs, cron jobs, certificate and domain expiry, and infrastructure behind a firewall, from probes in five regions.
Knowing a certificate expires in eleven days is not a feature we buy from somebody else. It is the thing we get up and work on.
Two tracks
Take one or both.
Website maintenance
The application layer: CMS and plugin updates, content changes, broken links, forms that stopped sending, and the slow accumulation of small problems that makes a site feel neglected.
- CMS & plugin updates
- Content changes
- Uptime monitoring
- Form testing
Server maintenance
The layer underneath: OS patching, web server and database configuration, certificate renewals, disk and memory headroom, and log review before a warning becomes an outage.
- OS & package patching
- TLS certificates
- Capacity headroom
- Log review
Start here
Want someone watching it?
Tell us what you're running and we'll tell you what maintaining it properly involves.
