ReDock Web compared with WP Umbrella
WP Umbrella is the closest thing on this list to a like-for-like rival, and on the care-plan mechanics it is ahead in several places. Incremental backups with a 50 day retention, safe updates that do compare screenshots, PHP error monitoring with stack traces, and uptime checks from five regions are all things ReDock Web does not have or does not do as well. Where the two differ in kind is the AI side and the record. Their AI offering is a Claude Code plugin that runs on your own machine against their public API. ReDock Web puts the door on the server, with a consent screen, four levels, seven policy switches and a refusal log, which is a different answer to a different question. Their pricing is also simpler than ours: one per-site price and two add-ons.
- https://wp-umbrella.com/features/ the feature list, in their own words
- https://wp-umbrella.com/pricing/ the trial, the per-site price and the two add-ons
- https://wp-umbrella.com/features/wordpress-uptime-performance/ the uptime interval and the monitoring locations
- https://wp-umbrella.com/features/safe-updates/ the backup before an update, the screenshots and the automatic rollback
- https://wp-umbrella.com/features/wordpress-backups-restoration/ frequency, storage, incremental backups and retention
- https://wp-umbrella.com/features/wordpress-security/ hardening, vulnerability scanning and the security add-on
- https://wp-umbrella.com/features/claude-plugin-for-wordpress/ what their Claude offering is, and where it runs
| ReDock Web | WP Umbrella | |
|---|---|---|
| Connecting sites | The ReDock Connect plugin on each site. One at a time, or paste a list of up to 100 addresses and hand out an eight-character code per site. The site keeps its own key and revokes it from its own wp-admin. | "Install our plugin on your site and enter your API key." |
| Bulk plugin updates | One job across up to 100 sites, watchable and cancellable, with each site reporting its own sentence on its own row and a retry that runs only the sites that failed. | "Bulk and scheduled updates," with "Full update history." |
| A snapshot before an update | Taken on the site, as a step of every plugin update. No snapshot, no update: a site that cannot make one is skipped rather than updated. | Yes, and it is a whole-site one: "Before an update runs, WP Umbrella takes a backup of the site's files." |
| Safe updates with an automatic restore | Safe update fetches five pages from outside before the update and again after, with no key and no sign-in, and puts the site back to its snapshot when a page that was answering returns a server error or nothing a theme had drawn. | Yes. "If a problem is detected, the update is rolled back automatically using the pre-update backup," and you "can also review any update and trigger a rollback manually at any time." |
| Visual comparison on updates | No. Nothing here compares screenshots. The check compares whether the pages answered, and the job page says exactly that. | Yes. "Before the update starts, WP Umbrella checks the compatibility requirements and takes a screenshot of your page," then "Once the update is complete, we check the status code and take another screenshot to compare against the previous version." |
| Plugin rollback to a version | One press on the plugin's row puts back the version the snapshot holds. The restore is queued through the same queue and recorded under your name. | "Update validation and rollback visibility," and a manual rollback on any update, restoring from the pre-update backup rather than from a copy of the one plugin. |
| WordPress core updates | Yes, and only on a site that finished a full archive of its own in the last day; the rest are refused rather than updated. Core is not put back automatically: the job says what changed, names the archive to restore from, and emails the owners. | Yes, with updates run through "visual regression testing, cache clearing, and database upgrade verification." |
| Uptime monitoring, and how often | One ordinary page request to the site's own public address, carrying no key, every minute, every five minutes or every fifteen, chosen once for the workspace. A site is down after two visits in a row with no answer. Ninety days of hourly history. | "Uptime checks run from every 1 minute to every 60 minutes," from "monitoring locations in the EU, US East, US West, Asia, and Australia," with alerts "by email or Slack." |
| A health state, and how it is expressed | A list of reasons in sentences, never a score: the site did not answer, the key was refused, PHP at end of life, WordPress behind, the schedule stalled with the overdue tasks listed, a certificate expiring or issued for the wrong name, mail that stopped sending, a client key nobody accepted. | Separate readings rather than one named state: uptime, performance on desktop and mobile, SSL certificate checks, domain expiration tracking and "Automatic PHP error monitoring" with "Grouped errors with stack traces." |
| Client reports | A month per client group or per workspace, built from records made as the work happened, as a print view, CSV or JSON, with an email on the first of the month when you switch it on. | "Automated maintenance reports," generated on a schedule you choose, as an email and optionally an attached PDF. |
| White-label reports | Your name, logo and two colours on the client's own copy, sent under a name you choose. A colour pair below the WCAG 2.1 AA contrast ratio is refused with the measured figure. | "White-label PDFs" and "Custom branding," with reports sent from your own domain. |
| Two-factor and hardening | Six protections and two-factor enforcement per site on one card, with the enrolment count shown before you enforce, and an alert naming the day a protection was switched off outside ReDock. | Yes, on every plan: "hide your WordPress version, block user enumeration, mask login error messages, disable the file editor, add security headers, rate-limit login attempts, disable XML-RPC, and protect your uploads folder." Two-factor for the managed sites is not mentioned on the pages read. |
| File integrity against WordPress.org | Every core file compared daily with the checksum WordPress.org publishes for that site's own version and language, plus plugins from the directory, with every finding named by path. | Not stated on their site |
| Vulnerability checks | Every hour, every plugin and theme on every connected site is compared with the published vulnerability records, and an affected plugin is marked on the site with the version that fixes it. A site whose plugin list could not be read says so rather than reading clean. Vulnerability records are sourced from Wordfence Intelligence and MITRE. | "WP Umbrella scans every site in your portfolio every 6 hours for known vulnerabilities affecting WordPress core, plugins, and themes," "powered by Patchstack." |
| Backups | A full archive of each site every day, copied to your own Google Drive, one folder per site, the last fourteen kept; ReDock stores none of it. Plus a snapshot of a plugin before every update, with a one-press restore. | Yes, included in the per-site price: hourly as an add-on, otherwise daily, weekly, monthly and manual, incremental for both files and database, "stored on WP Umbrella-owned infrastructure in Europe," kept 50 days, restorable in full or in part "with a single click." |
| An activity log, and how long it is kept | Every call with the site, the tool, who asked, the level it ran at and how it ended, refusals included. Kept 400 days, filterable six ways, exported as CSV or JSON. | "Activity logs" on the feature list, and a "Security-Driven Activity Log" in the Security add-on. No retention period is stated on the pages read. |
| Roles | Owner, Admin, Member and Viewer per workspace, plus client groups that file sites under the customer. A viewer opens every site and every record and presses nothing. | "Team roles and permissions," with unlimited team members. |
| Single sign-on | OpenID Connect per workspace, for an email domain the owner proves with a DNS record. Google Workspace, Microsoft Entra, Okta or any OIDC provider. | Not stated on their site |
| An API | Scoped API tokens for a workspace or a single site, through the same door, the same policy and the same records as an app that signed in. | "API access" and "Webhook support," with reports customisable through the API. |
| An AI door for AI apps | A hosted MCP server at app.redock.xyz/mcp for Claude, Claude Code, Cursor or any MCP client, with OAuth consent, four levels, a per-site address, and revocation that bites on the next call. | Not an MCP server. "A zero-dependency Claude Code plugin, available on GitHub," which "targets Claude Code" and will not work with Cursor or Windsurf. It is "Local-first by design," and "Your Public API token stays on your local machine." |
| AI policy controls | Seven switches per workspace, tightenable per site. Off means the call is refused at the door and the app is told to ask a person, with the refusal on the activity page. | Not stated. The Claude Code plugin runs locally against a public API token, and no server-side controls over what an AI app may do are described on the pages read. |
| A client's own sign-in | Not live. A client gets a viewer seat in your workspace, or the monthly document with no account at all. Their own sign-in is being built. | Not stated on their site |
| Self-hosted or hosted | Hosted, at app.redock.xyz. There is no self-hosted option. | Hosted, with backups on their own infrastructure in Europe. |
| Free tier | One connected site and one seat, free forever with no card, carrying the whole of ReDock Web and the whole desktop app. | No free tier. A 14 day trial with full feature access, "No credit card required to start." |
| Starting price | Light is $8 a month for 3 sites and 1 seat. Pro is $19 for 10 sites and 5 seats. Studio is $49 for 25 sites and 25 seats. Billed monthly, with extra sites past a plan's count at $1 each a month. | One per-site price, EUR 1.99 or $2.19 per site per month, plus a Security add-on at EUR 2 per site per month and Hourly Backups at EUR 2.49 per site per month. Yearly prepayment takes 10% off. |
What they have that we do not
- Backups, incremental for files and database, kept 50 days and restorable in whole or in part from their dashboard. ReDock Web makes one full archive a day into your own Google Drive, kept fourteen days, and restores a plugin, not a whole site, in one press.
- Visual screenshot comparison on updates, before and after. ReDock Web compares whether pages answered, not what they looked like.
- PHP error monitoring with grouped errors and stack traces.
- Uptime checks from five regions rather than from one place.
- Performance monitoring, domain expiry tracking and scheduled link and image checks.
- A simpler price: one per-site figure and two optional add-ons, rather than four plans with site counts.
What we have that they do not
- A hosted MCP door for Claude, Claude Code, Cursor or any MCP client, with an OAuth consent screen, four levels and per-app revocation. Theirs is a Claude Code plugin on your own machine, and it says on their own page that it will not work with other agents.
- Seven AI policy switches per workspace, tightenable per site, enforced at the door with every refusal recorded and exportable.
- A snapshot of the specific plugin taken as a step of every update, with a one-press restore of that version.
- A health state made of reasons in sentences rather than a set of separate readings, including a stalled schedule with the overdue tasks listed and a Run now on each.
- Daily file integrity against the checksums WordPress.org publishes, with each finding named by path.
- Two-factor enforcement per site, with the enrolment count shown before you enforce, and an alert when a protection is switched off outside the dashboard.
- Four roles including a viewer seat you can give a client, plus single sign-on through OpenID Connect for a domain proved by a DNS record.
- An activity log kept 400 days, with the refusals visible and CSV and JSON export.
- A free tier that connects one site forever, and a free desktop app for macOS and Windows on every plan.
Their pricing page says the monthly price "only depends on how many sites you manage, plus two optional per-site add-ons (Security and Hourly Backups) for the sites that need them": EUR 1.99 or $2.19 per site per month, with Security at EUR 2 and Hourly Backups at EUR 2.49 per site per month, and 10% off for paying yearly.
Read on 11 September 2026 at https://wp-umbrella.com/pricing/Can I import my sites from WP Umbrella?
No. There is no importer. Each site is connected by installing the ReDock Connect plugin and entering a code, and a list of up to 100 can be onboarded in one batch with a code per site.
They include backups in the price. Do you?
ReDock Web does back sites up, in a different way. Every day it makes a full archive of each connected site, files and database, and copies it to your own Google Drive, one folder per site, keeping the last fourteen; ReDock stores none of it. Restoring a whole site means downloading that copy and putting it back the way your host restores a backup, where WP Umbrella restores in whole or in part from its own dashboard. Before every plugin update ReDock Web also takes a snapshot of that plugin, with a one-press restore.
Both of you offer something for Claude. What is the difference?
Where the rules live. Their Claude Code plugin runs on your own machine with a public API token, and their own page says it targets Claude Code and will not work with other agents. ReDock Web serves a hosted MCP door that any MCP client can reach, and the consent screen, the four levels, the seven policy switches and the refusal record all sit on the server, so an app that is told no never reaches the site.
Judge it on one site.
One connected site is free forever, with no card, and it carries the whole of ReDock Web. Connect a site you already run and see whether the parts this page says we do well are the parts you needed.
Free for one site · the desktop app is free on every plan