# WPControl

> Multi-site WordPress management SaaS for freelancers and agencies, with full source code to customize and run as your own SaaS.

Source page: https://saascode.ai/products/wpcontrol
Machine-readable record: https://saascode.ai/products/wpcontrol.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $199 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

WPControl is a multi-site WordPress management product with a plain-language command layer. Its buyer is a freelancer or agency maintaining somewhere between 5 and 200 client WordPress sites. It exists to collapse work that would otherwise mean logging into each site one at a time.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/wpcontrol — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://wpcontrol.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

4 roles seeded on the demo (of the 5 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Site operator** (`editor`) — `editor@demo.com` / `see the page`
  Runs site work and reports without managing people.
- **Reporting viewer** (`viewer`) — `viewer@demo.com` / `see the page`
  Reviews fleet health, analytics, usage, and reports.
- **Workspace owner** (`admin`) — `user@demo.com` / `see the page`
  Manages sites, automations, teammates, and client groups.
- **Platform owner** (`super_admin`) — `admin@demo.com` / `see the page`
  Runs the instance across workspaces and platform controls.

Or open a role directly: https://saascode.ai/demo/wpcontrol?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 5** — distinct roles accepted by the role CHECK constraint: admin, editor, member, super_admin, viewer
- **tables: 67** — distinct CREATE TABLE statements across every applied migration
- **migrations: 109** — .sql files in supabase/migrations
- **page modules: 88** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 152,532** — lines of code (comments and blank lines excluded) across 993 TypeScript files (136,357) and 132 SQL files (16,175); node_modules and .next excluded
- **api route files: 226** — files named route.ts under src/app/api
- **http operations: 302** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 67 tables, 109 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-08-06

## Complete capability inventory

12 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Connected sites, health scores and the WordPress connector

- **Multi-site dashboard + health** *(seller-authored)* — See every connected site's status, WordPress and PHP version, update inventory, uptime, and computed health score in one console. The shared view turns scattered site checks into a fleet-wide operating picture, while each score remains tied to recent uptime history rather than a fixed value.
- **Plugin/theme tracking** — For each site WPControl tracks plugins and themes with their version, whether an update is available, and whether they are active. Inventory refreshes on a sync, which happens after a handshake, on demand, and as one of the bulk actions.
- **Team & client grouping** *(seller-authored)* — Organize sites into client groups and give workspace teammates access at the right role. Groups keep fleet filtering and bulk-operation targets aligned with each client, while the workspace owner controls who can manage sites, run operations, or stay read-only.

### The AI command layer, bulk operations and safety gates

- **AI chat agent (AI chat with configurable model routing and built-in fallbacks)** *(seller-authored)* — AI chat with configurable model routing and built-in fallbacks
- **Bulk operations (async)** — A bulk operation is one parent run that fans out to one child job per site. Each child carries its own status, so a run of 60 sites reports 58 completed and 2 failed rather than a single verdict.
- **AI off-switch (GDPR)** *(seller-authored)* — Turn AI features off for an entire workspace when its data policy requires it. The control applies before store data reaches an AI provider, while monitoring, reporting, and the rest of the non-AI product continue to operate normally.

### Uptime monitoring, reports, automations and WooCommerce analytics

- **Uptime monitoring** — Sites are probed on a minute interval. Each check records whether the site answered and how long it took, and a run of failures opens a down event that closes when the site recovers. The /uptime screen shows the response-time series per site plus the event history, and those same checks are what the health score is averaged from.
- **Email + PDF reports (Generate PDF reports and deliver download links by email)** *(seller-authored)* — Generate PDF reports and deliver download links by email
- **Automation engine (Create, run, and manage workspace automations from the dashboard)** *(seller-authored)* — Create, run, and manage workspace automations from the dashboard
- **WooCommerce analytics** — For connected sites running WooCommerce, WPControl pulls periodic read-only snapshots and presents cross-store analytics: revenue, orders, products and customers per store.
- **White-label reports (White-label PDF reports with email link delivery)** *(seller-authored)* — White-label PDF reports with email link delivery

### Plans, site caps and AI usage metering

- **API access** *(seller-authored)* — Connect outside workflows and agent tools to WPControl through the Scale-tier workflow API and tool bridge. The shipped access layer lets a buyer extend fleet operations beyond the built-in interface while retaining the product's role and plan boundaries.

## What each system gives the operator

*stated.*

- **Connected sites, health scores and the WordPress connector** — Run every client site from one clear, current operating picture.
- **The AI command layer, bulk operations and safety gates** — Turn one intent into controlled work across the entire WordPress fleet.
- **Uptime monitoring, reports, automations and WooCommerce analytics** — Keep client sites watched, reported, and moving without repetitive manual checks.
- **Plans, site caps and AI usage metering** — Offer extensible fleet operations as a higher-value tier for your own customers.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Know which client site needs attention before the next support message arrives.

Managing client WordPress sites becomes expensive when attention is driven by whoever complains first. Updates, degraded performance, and stale inventories hide across separate logins, so routine checks become a recurring sweep that still misses the quiet failures. The agency loses time proving what happened, staff work from different snapshots, and a client can discover a problem before the team responsible for it. A useful fleet view changes the operating question from which dashboard should I open to where does the business need to act today?

### Move the whole fleet forward without turning one mistake into two hundred.

A change that is harmless on one website becomes a business risk when it is repeated across dozens of client properties. Manual work makes the result depend on memory: one site is skipped, another receives the wrong action, and nobody can reconstruct the sequence when a client asks. The opposite extreme is just as dangerous: instant automation with no point to stop and reconsider. Agencies need speed without surrendering control, because every saved hour loses its value the moment a broad action creates a weekend of recovery work.

### Keep every client informed without rebuilding the same report by hand.

Client reporting often begins as a useful service and ends as recurring production work. Data is copied into a deck, brand details are corrected again, and delivery depends on the one person who remembers which customer expects what. As the account list grows, the agency must choose between spending more time on updates that prove its value or sending thinner reports that make the work less visible. The real cost is not the document itself; it is turning evidence of ongoing care into a monthly interruption that scales directly with the number of clients.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — Runs Next 16.2.10 and React 19.2.3; this release does not pin a Node engine version in `package.json`.
- **Supabase** (required) — The Supabase client is present in the application.
- **Scheduled jobs** (required) — Five jobs are declared in `vercel.json`; another host must wire the same schedules.
- **Email delivery** (optional) — Providers ship for Brevo, Mailgun, Resend, SendGrid, and SMTP.
- **Upstash** (optional) — Optional service settings are present for Upstash.
- **Sentry** (optional) — Optional service settings are present for Sentry.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 152,532 lines across the application and its database, 67 tables defined by 109 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The WPControl demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 4 of them: Site operator, Reporting viewer, Workspace owner, Platform owner. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 88 page modules and 302 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, Scheduled jobs. Optional: Email delivery, Upstash, Sentry. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 109 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $199?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [WPControl: Multi-Site WordPress Management for Agencies](https://saascode.ai/inside/wpcontrol-multi-site-wordpress-management.md)
- [WordPress management software in 2026: what can you verify before signup?](https://saascode.ai/inside/wordpress-management-software-verification-guide-2026.md)
- [WPControl vs MainWP: three parties, two different products](https://saascode.ai/inside/wpcontrol-vs-mainwp-platform-owner-agency-site.md)

## Links

- Catalog page: https://saascode.ai/products/wpcontrol
- Product record: https://saascode.ai/inside/products/wpcontrol
- Live demo: https://wpcontrol.saascode.ai
- Every product: https://saascode.ai/llms.txt