WordPress in depth
Orbit Webmaster is a WordPress operations platform that happens to hold the rest of your portfolio too. The depth is here: the connector, the directories, the fiche, the safe path, the portal.
Install the Orbit WordPress plugin on the client site. Authenticate with a unique connection token. From that moment the site can:
The plugin does not contain the product. If you remove it, the site disconnects. History, contracts, and snapshots stay in Orbit.
Connector
Name, URL, client, type, tags, hosting environment.
A thin plugin. No product logic inside WordPress.
Hashed and encrypted. Rotate or revoke at any time.
Core, PHP, plugins, themes, users, builders, health, SSL.
A snapshot includes WordPress and PHP versions, every plugin (active, inactive, must-use, drop-in), themes, users, custom post types and taxonomies, ACF groups, page builders, health recommendations, SSL and DNS. A site with 8,000 posts is operationally different from a site with 12 pages. Orbit keeps that difference.
Functional roles Orbit resolves when they are actually present: builder, custom fields, SEO, security, multilingual, cache, forms, e-commerce, backup, consent, SMTP, analytics, image optimisation, membership/LMS, CRM, redirects.
The watch zone only nags the essentials: security, backup, cache, GDPR. It will not invent an LMS warning on a brochure site.
Redundancy is a first-class signal. Two SEO plugins is not “fully covered.” It is a conflict.
Deactivated plugins still sit on disk. WordPress security practice is to delete them. Orbit treats inactive plugins as a cleanup queue, with “keep intentionally” when you mean it, and a bulk remove that snapshots first.
Must-use and drop-ins are listed. They are not toyed with through the normal deactivate flow.
The Plugin Directory and Theme Directory are global, curated, and reused across agencies. Your preferences sit on top and never fork the global data.
Unknown plugins and themes go to a review queue. AI may suggest a classification. A human confirms before it becomes knowledge.
The model Orbit is built around:
This is the opposite of “update all on live, hope the rollback works.”
The portal is not a second SaaS. It is a menu in their admin, white-labelled by beingtheir WordPress. Contract, hours, tasks, reports, requests. No execute button on the client side.
Static sites still belong here — they just connect with GitHub instead of this plugin.
Request access and we will walk your portfolio through the connector, the fiche, and the safe update path.
