Know what your site is doing, in words you can act on
Maintena watches eleven signals across a WordPress site — uptime, certificates, performance, vulnerabilities, visual changes, traffic — and turns them into a single 0–100 health score with a plain-English explanation of what changed and what to do about it.
Trusted by
Built for teams who need to know their site is fine without checking.
The problems Maintena was built for
Failures nobody sees
A certificate lapses on a Saturday and the site shows a security warning until someone happens to visit.
Patches that arrive late
A plugin picks up a published vulnerability and sits unpatched for weeks, because nobody reads CVE feeds.
Layouts that break on release
A deploy shifts something visual and the first report comes from a customer rather than a dashboard.
Numbers without meaning
Uptime here, a performance score there, a vulnerability list elsewhere — each assuming you know how to read it.
Reports you cannot hand over
A client or an auditor asks what happened last quarter and the answer is scattered across four tools.
Care that does not scale
One site is manageable. Thirty sites, each with its own stack and release schedule, is not.
How Maintena Works
Point it at the site
Monitoring starts from the outside in — the same way a visitor, or an attacker, would see the site.
Eleven signals sample continuously
Uptime, certificates, performance, vulnerabilities and visual state, each on its own schedule.
Six of them become one number
The health score answers the only question most owners have on a given morning: does anything need me today?
Findings get explained
Each one says what changed, why it matters and what to do next — in plain English, not in metrics.
Act on it, or hand it over
Fix it from the dashboard, or move to a managed plan where a specialist does the work and the reporting.
What Maintena Watches
How We Built Maintena
Where the difficulty actually was
Collecting the data was never the hard part. Turning eleven noisy signals into one judgment an owner can act on was.
Signals sampled independently
Eleven signal types run on their own schedules rather than one sweep, so a certificate check never waits on a performance run.
The explanation layer
Getting a model to produce an actionable judgment — and, harder, to stay quiet when nothing is wrong — took more iteration than the pipeline did.
Quality measured, not asserted
An evaluation set tells us when explanation quality drifts. Specialists on managed plans keep that set honest.
Built on what we already knew
The product exists because we maintained WordPress estates for years and learned which signals predict failure and which are noise.
What This Proves
- AI applied to a real operational problem
- Continuous monitoring at estate scale
- Explanations a non-technical owner can act on
- Audit-ready reporting for regulated buyers
- A product we run, not just ship
Who Maintena Is For
Getting Started With Maintena
Self-serve at one price per site, cancel anytime. Managed plans put a specialist on maintenance and growth. Larger estates and bespoke requirements are handled as enterprise.
Signals Monitored
Feed the Health Score
Continuous Watch
The services this proves out
We built Maintena with the same team and the same practices we bring to client work.
Engage & Acknowledge from the Digital Sphere
FAQS
Common questions about Maintena.
It means the explanation layer is the product, not a chatbot bolted onto a dashboard. Monitoring tools have reported uptime and vulnerabilities for twenty years. Maintena’s job is to read those signals together and say, in a sentence, whether this one matters to your site and what to do — including saying nothing when nothing is wrong.
Six of the eleven monitored signals roll into the 0–100 number. The remaining signals are reported alongside it rather than folded in, because averaging a traffic dip into a security score produces a number nobody can act on.
The uptime, certificate, performance and visual signals are platform-agnostic. The vulnerability matching is WordPress-specific, because it reconciles plugin and theme versions against published CVEs. We say WordPress because that is where the product is strongest.
Yes — that is why the reporting exists as PDF rather than only as a dashboard. Public-sector and regulated teams use them as audit-ready evidence of uptime, patching and content control over a period.
Self-serve gives you the monitoring and the explanations, and you act on them. On a managed plan a specialist does the work — patching, fixes and growth items — and the report tells you what they did.
Want something like Maintena?
The engineering behind our own products is the engineering we bring to yours. Tell us what you are trying to build.