Patching, hardening, monitoring and restores handled by a named engineer — with a monthly report you can actually read.
Managed ops is not a support queue with a nicer name. It is an engineer who owns your server and gets paged before you notice.
The unglamorous work that stops incidents happening in the first place.
You get a human, not a ticket number, and we act before asking permission for the obvious.
Both include the daily work above. The difference is response commitment and how much application-level work is included.
One server, business hours escalation.
Revenue-critical servers that cannot wait until Monday.
Priced per server, billed monthly, cancel with 30 days notice. Prices exclude 18% GST.
Worth stating plainly, because vagueness here is how hosting companies pick fights with clients later.
| Task | Included | Notes |
|---|---|---|
| OS, web server, PHP, database patching | Yes | Tested before rollout |
| Security hardening, WAF, malware cleanup | Yes | Reinfection hardening included |
| Restores and disaster recovery | Yes | We perform them, you get told after |
| Plugin and theme updates (WordPress) | Yes | On staging first where staging exists |
| Writing or fixing your application code | No | Separate engagement with the srchout dev team |
| Third-party API failures | Escalation only | We identify and report; the vendor fixes |
| Content, SEO and marketing work | No | Different team, different contract |
No sales-speak — the real constraints.
Yes, without a rebuild. We audit the server first and give you a short list of what we would change before touching anything.
You keep it. Managed ops does not mean locked out — it means someone else is responsible for the boring parts. We do ask to be told about changes you make, so we are not debugging your work blind.
On the 24/7 tier, yes, and it is measured. We publish our actual response times monthly rather than only the promise.
Send us the server details and we will tell you what we would fix in the first week, before you commit to anything.