01 Service / Managed Services
We monitor, maintain and support business websites — including sites we did not build. The work is practical: detect problems, investigate them, fix what can be fixed and keep the site current.
01 / MANAGED SERVICES
Most business websites are not finished at launch. Software ages, certificates expire, forms break, content management systems need updating and hosting environments change. Managed Services exists to keep those systems working and to give someone clear responsibility when they do not.
We can take over an existing website, establish a baseline, and provide ongoing availability monitoring, security monitoring, maintenance and technical support. Customers do not need to have commissioned a new website from us to work with us.
Monitoring and maintenance reduce uncertainty; they do not guarantee uninterrupted service. We explain what is monitored, how alerts are handled and where responsibility sits before the arrangement begins.
Fig. 01 — A typical structure for this work. Each engagement is shaped to its context.
A capability list, not a fixed package. We agree the scope together once the problem is clear.
We check that the website responds and that key pages return the expected result. A failed check raises an alert, and initial investigation narrows the cause to the application, DNS, the server, the network or an upstream dependency. Monitoring detects interruption; it does not prevent it.
Proprietary PHP-based monitoring compares file hashes and watches for changes that should not happen. Alerts identify what changed and when so it can be investigated. Monitoring, investigation and remediation are separate activities, and no monitoring arrangement guarantees complete security.
Routine updates, compatibility checks and small fixes. We keep the site working with current PHP, server and browser versions and deal with the failures that become outages when left alone.
Ongoing technical responsibility for the whole site: releases, maintenance, monitoring, support and coordination with the hosting provider. You get a named technical route instead of an unowned system.
Practical help for the people who run and use the site: broken forms, email delivery, access problems, content and configuration issues, and questions about what changed.
We review the codebase, hosting, DNS, backups, access and dependencies before taking responsibility. The site does not need to have been built by us, and it does not need to be replaced to be supported.