Sign in Start free
About

Built inside an agency, for the agencies the big tools forgot

WPClientHub exists because we ran a WordPress agency and got tired of choosing between tools that wanted to be our host, our vendor lock-in, or our percentage.

Every WordPress agency eventually assembles the same Frankenstein stack: one tool for updates, another for backups, a monitor bolted on, reports assembled by hand in a doc template the night before they’re due, and invoices in a system that has never heard of any of it. It works — the way a shopping cart with one bad wheel works.

The established platforms each solve part of it, and each carries a structural catch. The biggest one is really a hosting company, and its management hub is the funnel — every feature quietly asks why you aren’t hosting with them. Another belongs to one of the world’s largest hosts. The cloud tools warehouse your clients’ backups on their storage, which is why your bill scales with every site you add and why leaving them means abandoning your backup history.

We wanted the boring, obvious thing: one command center that manages the sites, supports the clients, bills them, and proves the work — without ever competing with us, metering our growth, or holding our data. It didn’t exist. So we built it — starting with a small group of design-partner agencies running it on real client sites, and it has since grown a help desk with a client portal on your own domain, AI diagnosis with the evidence attached, offsite backups to storage you own, one-click restore, and alert routes into Slack.

WPClientHub is live today. The roadmap on our pricing page is honest about what’s shipped and what’s coming — everything above the amber line works now, on every tier it’s ticked on. Come kick the tires, free for your first three sites.

Principles

The four commitments we won’t trade away

Host-neutral, forever

We will never sell hosting, so we will never compete with you or your host, never nudge a migration, never have a reason to care where your sites live. Cloudways, Kinsta, Hetzner, shared cPanel — if WordPress runs there, we manage it.

Your data stays on your side

Every backup archive is built on the client’s own server and stays there. We hold metadata: manifests, checksums, schedules. If you leave tomorrow you lose nothing, because there was never anything of yours here to lose.

No percentage of your revenue

Client billing runs on your own Stripe account, or straight to your bank — never through us — with no platform fee on any tier. Your care-plan book is your business; charging rent on it would make us a partner you never chose.

Honesty over polish

Health scores show their math. AI answers show their evidence and say “needs a person” when they aren’t sure. Unshipped features are listed under a line on the pricing page that says they are not shipped — never as a tick on a tier. When a module does less than the category usually implies, the feature page says so in the same breath as the pitch. Marketing stats here are product facts, not invented customer counts.

Under the hood

The stack we build on

Boring, proven technology arranged around one truth: this product is mostly thousands of background jobs against thousands of unpredictable servers.

Laravel · PHP 8.4 · PostgreSQL · RedisControl plane — org-scoped multi-tenancy, queued jobs with per-host backoff, and the same language as the WordPress ecosystem we serve
React + Inertia + TypeScriptA fast 2026-grade UI — because half this market is visibly stuck in 2015
Original connector pluginPer-site Ed25519 keypairs, signed requests, no WordPress passwords stored — PHP 7.4+ friendly
Standalone uptime probeA lightweight agent outside the app — one region today, built to fan out, every result stamped with where it came from — whose second failed check is what opens an incident
Claude by AnthropicDiagnoses and Ask AI run on Claude — a fast model to classify, a stronger one to reason — with the site’s own facts as evidence and a confidence score on every answer
Playwright workersReal-browser screenshots and pixel diffs behind every scheduled update
Your Stripe + PaddleYour client billing on your own Stripe account (a restricted key, no Connect) or direct invoices; our own subscriptions and credit top-ups through Paddle as merchant of record — money never flows through us
WPVulnerability feedA public, keyless vulnerability API, cached and matched against the exact version each site runs
Say hello

Talk to the people building it

Questions, corrections, war stories about shared hosting — we answer everything ourselves at hello@wpclienthub.com, or see the contact page.