Defense, backups and billing: built in, not bolted on.
Threat blocking, scheduled backups and per-site billing for every site you run, carried by the platform that hosts them, not a WP Umbrella bill on top. Uptime polling is the one thing it does not do yet, and the table below says so. Everything else here is the real dashboard with demo data. Click around; it responds.
Every site’s numbers in one cockpit.
Traffic, blocked threats, backups and billing, per site, in one place. No WP Umbrella subscription bolted onto your hosting. Go ahead: click the tabs.
Per site you get traffic, blocked threats, backups and billing in one place. Underneath, the cockpit reads request volume from cookieless metrics and threats blocked in the last 24 hours, and backups run as tracked action-runs on their own schedule. Continuous uptime and health polling is not part of this yet: a health check runs on demand and as the gate on every update, not on a scheduler. So you answer a client’s “what happened to my site?” with real numbers, and hand them a hosted payment link without a card ever touching the browser.
Live component: real product code, filled with demo data.
All your sites on one screen.
Every site you run with its provisioning state and recent activity: what happened where, without logging into five hosts. Select a card; the activity feed is real.
Every managed site’s provisioning state and recent activity sit in one view. Underneath, each site reports over a REST channel from a connector plugin (no SSH, no log scraping) and runs in its own isolated environment: its own namespace and database, no shared runtime, provisioned and reconciled by a Kubernetes operator from the order you placed. So one broken site can’t drag down another, and what the platform did to a site is on one screen instead of five.
Live component: real product code, filled with demo data.
Built in vs. a bolt-on subscription
A tool like WP Umbrella adds monitoring on top of whatever host you already pay for. TivadarCMS is the host, and carries the defense, backups and billing itself: one platform, one bill. The rows it cannot claim yet are marked as such.
| Capability | TivadarCMS | Bolt-on monitoring |
|---|---|---|
| Threat blocking included with hosting | Separate subscription | |
| Blocked-threat signals per site | ||
| Uptime polling & downtime alerts | Not yet | |
| Scheduled backups | ||
| Cookieless first-party analytics | Separate tool | |
| Billing your own clients through the platform | Not yet | Separate tool |
| One login for everything | Host + monitor separately |
Capability comparison against a typical monitoring add-on (such as WP Umbrella) running on top of separate hosting, as of 2026-07. Not a benchmark; verify current competitor features before relying on them.
Nothing reaches production untested.
The one thing that should never be a surprise: a change going live.
Every change (a plugin update, a theme tweak, a core upgrade) lands first on a clone of the live site, never the site itself. The clone runs an automated health check before anything is promoted, and promotion to production happens with zero downtime. So a bad update surfaces on a throwaway copy, not on your client’s homepage. You find the problem in a clone, not from the client who found it first.
Cookieless analytics, no add-on.
First-party visitor analytics captured by your own channels: KPIs, trends and a raw event feed. No Google Analytics, no consent-banner tax, no separate tool.
You get cookieless visitor analytics per channel you own: KPIs, trends, breakdowns and a raw event feed. Underneath, events are captured first-party and stored on your own infrastructure; nothing leaves the platform, so there’s no third-party tracker to disclose. So a consent banner never taxes your conversion rate, the data stays GDPR-native by construction rather than by policy, and you can put the numbers straight in front of a client.
Live component: real product code, filled with demo data.
Questions, answered.
- Do I still need WP Umbrella or a separate monitoring tool?
- For uptime polling and downtime alerts, yes: those are not part of the platform today. What is built in is the half that sits on the hosting: Sentinel blocks and logs threats per site, backups run on a schedule with a result you can read, and every update is promoted from a clone only once that clone comes up healthy. So the monitoring bill gets smaller, not zero, and we would rather say that than have you find out after signing.
- Is it overkill for just a few sites?
- Solo is €49/mo and covers one site. If you run a few, Studio is the one to look at (€149/mo for up to 10), and either way you get the same cockpit the agencies use.
- Where does my data live?
- 100% EU, with no US subprocessor in the serving path; the one US recipient is a manual IP lookup during an incident, listed on /trust. Analytics are first-party and cookieless: no Google Analytics, no consent-banner tax.
- Can I move an existing site in?
- Yes. An existing site is cloned onto the platform, and each connected site counts toward the plan. Self-serve signup is not open yet, so today that is arranged with us directly.
- What does it cost?
- Solo is €49/mo. Self-serve signup is not open yet, so an account is arranged with us directly.
The freelancer programme.
Freelancers are the segment that keeps showing up, and the programme is being shaped around what they say. Tell me what you run and what you would need from it.
Everything for your sites, in one place.
Self-serve signup is not open yet; the private beta is invitation-led. Hosting, defense and billing without a stack of subscriptions.