Run 20+ client sites from one dashboard.
Stop stitching a host, ManageWP, Stripe and a spreadsheet together. Everything below is the real dashboard: live components with demo data, not screenshots. Click around; it responds.
Run 20+ client sites from one screen.
Your whole book of business: provisioning state and recent activity per client site, at a glance. Select a card; the activity feed is real component behavior.
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.
Every client site gets a cockpit.
Drill in yourself or hand a client a link: traffic, subsystem health, blocked threats, backups and billing, per site, in one place. 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.
One platform vs. a stitched stack
Most agencies run a separate host, a fleet tool like ManageWP, a payment tool and a spreadsheet. TivadarCMS is the one platform that also hosts the sites it manages.
| Capability | TivadarCMS | Stitched stack |
|---|---|---|
| Manage every client site in one dashboard | Per-host logins | |
| Hosting and site defense in one platform | Separate host + tool | |
| Consolidated client billing & e-invoicing | Not yet | Separate tool |
| Cookieless analytics per client | Add-on / Google Analytics | |
| Provisioned from your order | Manual setup | |
| One login across disciplines | Multiple logins |
Capability comparison against a typical assembled agency stack (separate host + a fleet tool such as ManageWP + a payment tool + spreadsheets), 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.
Privacy-first analytics for every client.
Cookieless visitor analytics per channel you own: KPIs, trends and a raw feed you can put in front of a client. No Google Analytics, no consent-banner tax.
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.
One login, every client, every discipline.
Hosting, domains, analytics and the shared databases and caches underneath them, behind one launcher, role-scoped so owners, developers and finance each see only their slice.
You move from a client’s hosting to their domains to their traffic behind a single login: each workspace a focused tool, not another tab. Underneath, every workspace is a role-scoped view onto the same account in one authenticated session, with access granted per role. So an owner, a developer and a finance user each land in exactly their tool, with no second login, no shared password, and no one sees what their role doesn’t grant.
Live component: real product code, filled with demo data.
Questions, answered.
- Is this a ManageWP alternative?
- It overlaps with fleet management, but goes further: the same platform also hosts and bills the sites, so defense, provisioning and invoicing aren’t three separate subscriptions stitched together.
- Can I white-label and consolidate client billing?
- Not yet. Both are built and deliberately held back from this release. They belong to the Agency tier when they are switched on; nothing on your side changes when they are.
- How many client sites can one dashboard hold?
- There’s no per-dashboard cap. Each connected site counts toward your plan and can be disconnected any time.
- Where does client 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 cookieless and first-party per client channel, so there’s no third-party tracker to disclose.
- What does the Agency plan cost?
- Agency is €349/mo, or €13.96 per site at 25 sites. Reach out to become a partner; self-serve signup is not open yet.
Talk about moving a portfolio.
Tell me what you run today: how many client sites, on what, and what breaks most often. You get an answer from the engineer who built the platform, not a sales sequence.
Run your whole agency on this.
Self-serve signup is not open yet; the private beta is invitation-led. The dashboard above is the one you’d run, with your clients’ sites in it.