Automation handles the routine and creates the emergencies
Maintenance Plugin vs Managed Service: What Automation Misses
Decide between a WordPress maintenance plugin and a managed service by what each one does when an update breaks the site at two in the morning. Automatic patching handles the routine and creates the emergencies. The table sets out what unattended tooling covers and where it reliably fails; the calculator puts a monthly figure on both routes, including the hours you spend on the failures.
A WordPress maintenance plugin automates the mechanical work: updates, backups, scans. A managed service adds the judgement that automation cannot supply - testing before promotion, deciding what to defer, and being accountable when a release breaks something.
What will this cost me?
Second and further sites are 20% off. Excludes the cost of one bad release.
30-day money-back guarantee · No setup fee · Cancel anytime
How the options compare
| Capability | Maintenance plugin | Managed service |
|---|---|---|
| Applying updates | Automatic, on schedule | Staged, then promoted |
| Testing before an update goes live | – | Checkout and forms exercised each cycle |
| Deciding what to defer | – | Judged against the site and its customisations |
| Reacting when a release breaks something | Alerts you | Rolls back and investigates |
| Restore tested rather than assumed | – | Monthly, with the result recorded |
| Accountability when it goes wrong | Yours | Contractual |
| Cost | $5-$25 per month | $39-$149 per month |
| Best suited to | A site you can rebuild in a day | A site that earns money |
They are not competing products
A maintenance plugin and a maintenance service are usually presented as alternatives. They are not. Nearly every service runs the same plugins, on the same schedule, producing the same reports.
What is being bought is different. A plugin sells execution: the patch gets applied, the backup runs, the scan completes. A service sells judgement: whether this update goes live today, what to do when it breaks the checkout, and who answers at two in the morning.
Framing it as tool versus service settles nothing. The useful question is whether the site needs the judgement.
Where unattended tooling reliably fails
Automation is excellent at the parts that are the same every week and useless at the parts that are not.
It cannot tell you the update broke something. The patch applied, the version number changed, the log records success. The checkout stopped completing three hours ago and nothing in the system knows.
It cannot decide to wait. A major version that breaks a customisation needs deferring – a decision requiring knowledge of the site that no plugin holds.
It cannot own the outcome. A licence is not an obligation. When an automatic update takes down a store on a Saturday, the recovery is yours.
The arithmetic that usually decides it
Run the calculator with honest numbers and the answer is normally unambiguous.
The variables are what an hour of downtime costs, how many hours a month you genuinely spend, and what your own time is worth. Most owners overestimate the second by a factor of four – the intention is four hours a month, the reality is under one, and the gap is where version drift accumulates.
Below roughly two hours a month of real attention, a plugin plus tested backups is proportionate. Above it, or on any site where downtime has a price, the arithmetic stops being close.
A plugin is the tooling. Whether anyone is watching what it reports is the separate question, and it is the same one as doing maintenance yourself versus paying for it.
What to judge it on
- What does the site lose per hour of downtime?Under a few pounds, and a plugin with good alerting is proportionate. In the hundreds, and the deciding factor is who responds at 2am rather than what applies the patch.
- Who tests after the update?This is the question automation cannot answer. An automatic update applies the patch and reports success on a site whose checkout no longer completes. Nothing in the tooling opens the page.
- How customised is the site?A stock theme with mainstream plugins updates cleanly almost always. Custom code, a page builder and a store multiply the ways an update changes something that was working.
- Who owns the outcome?A plugin licence carries no obligation to fix what an automatic update broke. That is not a criticism of plugins; it is the difference between a tool and a service.
- How many hours can you actually spend?The honest number, not the intended one. Most owners intend four hours a month and spend under one, which is the case a service exists for.
The short answer
- Use a pluginOn a brochure or portfolio site with a stock theme, few plugins and no transactions. Automatic patching plus tested off-site backups covers the realistic failure modes, and a broken week costs attention rather than money.
- Use a serviceOn anything taking orders, bookings or enquiries that matter. The value is not the patching - it is the testing before promotion and somebody accountable when a release goes wrong.
- Use bothThe common arrangement in practice. Tooling does the mechanical work; a person reads the results, tests what matters and decides what to defer. The tools on this page are what a service runs anyway.
Plans that include this
- Starter$39/monthor $390 a year — two months freeBlogs, portfolios and brochure sites
- UpdatesMonthly
- BackupsWeekly, 30-day retention
- Uptime5-minute checks
- Malware removalNot included
- Most chosenProfessional$79/monthor $790 a year — two months freeSmall businesses and lead-generation sites
- UpdatesWeekly + PHP version management
- BackupsDaily, 60-day retention
- Uptime1-minute checks
- Malware removalIncluded
- Business$149/monthor $1490 a year — two months freeStores, membership sites, anywhere downtime costs money
- UpdatesWeekly, tested on staging first
- BackupsDaily, 90-day, multi-location
- Uptime1-minute + 2-hour restore
- Malware removalIncluded
Questions people ask before calling
Can a plugin replace a maintenance service?
For the mechanical work, largely. For judgement, no. No plugin opens the checkout after an update to confirm it still completes, and that single check is most of what a service is buying you.
Are automatic updates safe?
For security point releases, safer than the alternative. For major versions and plugins, they are the leading cause of the breakages this page is about - an unattended break runs from whenever it landed until somebody notices.
What does a maintenance service do that I cannot?
Nothing you could not learn. The difference is that it happens every week whether or not the week is busy, which is the part that fails on self-managed sites.
Is a cheap service better than a good plugin?
Frequently not. A service at the bottom of the market runs the same automation and adds a report. Compare on whether updates are staged and tested, because that is the line between the two categories.
When it needs handing over
wordpress update serviceHand over WordPress updates and stop choosing between an unpatched site and a broken one. Core, plugins and themes are applied to a staging copy every…
More comparisons