WPControl
Multi-site WordPress management SaaS for freelancers and agencies, with full source code to customize and run as your own SaaS.
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.
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?
- Multi-site dashboard + health
- Plugin/theme tracking
- Uptime monitoring
- WooCommerce analytics
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.
- AI chat agent (AI chat with configurable model routing and built-in fallbacks)
- Bulk operations (async)
- Automation engine (Create, run, and manage workspace automations from the dashboard)
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.
- Email + PDF reports (Generate PDF reports and deliver download links by email)
- White-label reports (White-label PDF reports with email link delivery)
- Team & client grouping
The six actions are exactly:
There is no backup, no restore and no maintenance-mode action. If someone asks for one, the answer is that this product does not do it.
Run statuses: pending, in_progress, completed, failed. A run held for confirmation stays pending and queues nothing.
Monitoring depends on a scheduled job actually firing every minute. On a host whose scheduler cannot run that often, checks simply do not happen — and nothing errors to say so, which is why deployment guidance calls this out specifically.
Per-workspace alert rules are not available in this release. The four toggles on the uptime screen render visibly disabled, and each one states what is shipped today. There is no table storing per-workspace alert rules and no endpoint to write one; adding them needs both. The rules under the admin panel's own alerts area are a different, platform-wide surface.
Two properties are deliberate:
Revenue is stored in the currency it was captured in. Totals are not summed across differing currencies — a mixed-currency total would be a made-up number.
Requires Pro or above.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Hover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 54 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 67 tables, as text
active_boosts · admin_notifications · ai_action_audit · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · bulk_operation_runs · bulk_operation_targets · chat_conversations · chat_messages · connected_sites · credit_balances · credit_transactions · currencies · data_exports · data_imports · faq_categories · faq_items · feature_flags · inbound_webhook_events · inbound_webhooks · languages · marketing_audience_members · marketing_audiences · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · product_purchases · products · provider_prices · push_devices · report_runs · report_templates · roles · scheduled_tasks · seo_meta · site_groups · site_plugins · site_themes · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · uptime_checks · uptime_events · user_sessions · users · webhook_logs · webhooks · woocommerce_snapshots
The chassis, and anything particular to this product. 3 required, 3 optional.
Runs Next 16.2.10 and React 19.2.3; this release does not pin a Node engine version in `package.json`.
The Supabase client is present in the application.
Five jobs are declared in `vercel.json`; another host must wire the same schedules.
Providers ship for Brevo, Mailgun, Resend, SendGrid, and SMTP.
Optional service settings are present for Upstash.
Optional service settings are present for Sentry.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.
