Introducing ToggleWP Cloud (beta)
ToggleWP Cloud (beta) will be a hosted hub for ToggleWP. You manage all your client sites from one dashboard, without running a WordPress hub site yourself. This guide covers what the dashboard does and how it differs from running your own plugin based hub on a separate WordPress install.
The screenshots use demo data: a made-up agency with eleven client sites. Site names and addresses are fictional. The vulnerability matches are real Wordfence Intelligence records, matched against the plugin versions the demo sites report.
Hosted hub or your own WordPress hub
Client sites use the same ToggleWP plugin either way. They pair, sync settings and report status in exactly the same way, and can’t tell the two hubs apart. What changes is where the hub runs and who maintains it.
| Your own WordPress hub | ToggleWP Cloud | |
|---|---|---|
| Something extra to look after | A whole WordPress site: core, theme and plugin updates, PHP version, hosting, SSL, backups, and its own security. | Nothing. The hub isn’t a WordPress site, so there’s no extra install to update or secure. |
| If the hub site has a problem | A broken update, an expired certificate or a hosting outage stops every client site syncing until you fix it. | The service is run and backed up for you. |
| Scheduled work | Runs on WP-Cron, which only fires when someone visits the hub site, unless you’ve set up a real cron job. | Runs on a timer in the hub service: feed updates, mailbox checks, alerts and digests. |
| Vulnerability checks | Plugin and theme lists are sent to the Website Toolkit crawler to be checked. | Checked on the hub against its own copy of the Wordfence Intelligence feed. Results come back straight away, and the lists aren’t sent anywhere else. |
| Email delivery alerts | Sent by the hub site, so they depend on it working. | Sent by the hub service, which doesn’t depend on a WordPress site staying up. |
| Who can log in | WordPress users on the hub site. | Agency accounts with owner, admin and read-only roles, plus an activity log of logins and changes. |
| Secrets (AI keys, mailbox passwords) | Stored in the hub site’s database. | Encrypted at rest and never shown again after saving. |
Some things stay the same. Content checks still use your Website Toolkit allowance, and the ToggleWP modules on client sites behave identically.
Moving existing sites isn’t automatic. To move a site from a WordPress based hub, generate a pairing code here and pair the site again.
Sites
All sites
Every client site in one list, showing:
- its connection status and Feature Set,
- its WordPress version,
- when it last synced.
From here you can edit, re-pair, revoke or delete a site.
- Connected: paired and syncing.
- Disconnected by site: the site disconnected itself, for example because ToggleWP was deactivated there. It shows up so you notice.
- Awaiting pairing: added here, but no pairing code has been redeemed yet.
- Revoked: you cut the site off. Its credentials stopped working immediately, and the site’s entry is kept so you can re-pair it later.
Adding a site
Enter a name, choose a Feature Set and click Add site. The hub shows its URL and a single-use pairing code that lasts 15 minutes. On the client site, enter both under ToggleWP → Settings Sync. Add several… takes a list of names, or a CSV, and creates a code for each.
Re-pairing a site: Re-pair issues a new code. The site’s old credentials keep working until the new code is used, so a site you’re re-pairing doesn’t drop out in the meantime.
Portfolio
The Portfolio page gives you the state of every site on one screen, built from what each site reports when it syncs. It shows:
- renewals due in the next 30 and 7 days,
- login anomalies,
- email health score,
- open vulnerabilities,
- AI token use against each site’s allowance,
- an onboarding checklist for sites that aren’t fully set up.
Filters along the top narrow the list to sites with alerts, renewals due, login anomalies, email issues, pending onboarding or no sync yet.
A monthly digest of this page can be emailed to you on the 1st of each month. Turn it on at the bottom of the page.
Feature Sets
A Feature Set is the list of ToggleWP modules a site gets: for example a care plan, a security bundle or a basic utility set. Assign one to each site. Changing a set changes every site using it on their next sync. You can also add extra modules to a single site.
Each set has its own sync schedule, from hourly to weekly. The colour of each module shows what’s going on:
- Green: its settings are managed from the hub.
- Grey: switched on, but each site keeps its own settings.
- Red: a site reported it couldn’t switch the module on.
Policies
Policies are module settings you set once and push to every site that has that module.
- Managing a module: its fields override each site’s own values on the next sync.
- Modules you don’t manage: left alone.
- Stop managing: sites keep whatever values they currently have.
Allowed admin domains also lives on this page. Domains you list here are added to every site’s own list, for the admin-domain restriction in Security & Authentication.
Plugin Manager
Every plugin your sites report, in one table: which sites have it and which versions. For each plugin you can:
- Hide it from everyone except site admins.
- Protect it from being deactivated.
- Notify you by email when it’s deactivated.
- Hide auto-updates for it.
- Add an admin note that’s shown next to it on each site, such as “Updates tested on staging first”.
The same page manages Curated suggestions: plugins you recommend, shown in their own tab of each site’s plugin installer. UI Clean-up (next to Plugin Manager) manages one list of admin notices and CSS selectors to hide across all sites.
Vulnerabilities
Each site with the Vulnerability Monitor sends its list of plugins, themes and versions to the hub. The hub matches that list against the Wordfence Intelligence feed as it arrives, and sends the results back to the site straight away.
The hub keeps checking after that:
- Daily: the feed is downloaded again, and every site is rechecked.
- As Wordfence publishes: new entries arrive by webhook, and affected sites are rechecked.
- When matches change: the affected sites are told, and you get one digest email listing the sites with new findings.
Click a site’s open count to see each finding. Each one shows:
- its severity and CVSS score,
- the installed version and the version that fixes it,
- the CVE,
- a link to the Wordfence record.
Installed software turns it round: every plugin and theme across all your sites, which versions are in use, and where. Use it to answer “which of our sites run plugin X, and which version?” without logging in to each site.
Under Settings you choose who gets the agency digest. You can also have each site email its own admins about findings above a severity you choose.
Content checks
Content checks run in the Website Toolkit crawler using your agency’s allowance, exactly as they do from a WordPress hub. This page shows:
- the allowance left this month,
- a 90-day summary per site: checks run, passed, with issues, and when last checked,
- the full log of checks.
Quotas & log sets a monthly check limit per site, or pauses a site. Use it to stop one busy site using up the whole agency allowance. Owners are emailed when the allowance drops to 10%, 5% and zero.
Email delivery
Sites with the Email Health Monitor regularly send a tagged test email (a “probe”) to a mailbox the hub checks. The probe log shows each probe as:
- Matched: it arrived.
- Awaiting arrival: still on its way.
- Never arrived: it didn’t turn up in time.
When a site’s probes stop arriving, the hub alerts you by email, Slack or Discord, at most once per site every 6 hours.
The alerts are sent by the hub, so a site with broken outgoing email is reported even though it can’t send mail itself. You can use the shared probe mailbox or connect one of your own under Settings & mailbox. Email Health groups sets alert levels for each email category across all sites.
AI Assistant
Client sites with the AI Assistant module generate content through the hub, using your own AI provider key: Anthropic, OpenAI or Google. Your team can also use a browser extension with personal access tokens. Usage is counted against a monthly token allowance, and optionally a daily one, for each site and each extension account.
From the AI Assistant pages you can:
- Usage: see each site’s daily use, and reset its count.
- Settings: choose the provider and model, set the default allowance, switch features on or off (chat, long-form, voice profiles, page review), and write the writing guidelines added to every request.
- Templates: add your own content templates, or adjust the built-in ones.
- Edit (per site): change a site’s allowance, model or brand instructions.
- Browser extension: manage extension accounts and their tokens.
Provider keys are stored encrypted and never shown again after saving.
Settings
White label and report cards
White label sets the plugin name, description and author shown in each site’s plugin list.
Client report card is a monthly email that each site sends to its own contact. It can include:
- renewals,
- logins,
- AI usage,
- email health.
Set the wording once here. Set each site’s recipient on All sites → Edit.
Team, Account and Activity log
- Team: invite colleagues as owners, admins (can make changes) or members (read-only). Invites and password resets are one-time links.
- Account: change your own password and see your hub URL. A banner across the dashboard warns you when the account is within 14 days of expiring.
- Activity log: every login, failed login and change made in the dashboard, plus sites pairing and disconnecting. Owners and admins can search it and filter it by type. Entries are kept for 30 days.
What’s next?
The ToggleWP Cloud is currently under development, and I am hoping to have it available during November for users on the beta programme.