Owner
Full controlPortfolio quality, stack alignment, retainers that are not a rumour. Full control, including billing and integrations.
For agencies
Built for the people who have to hand a site over on Monday.
Orbit Webmaster is for web agencies with a maintenance practice — roughly ten sites and up. WordPress at the core. Static sites in the mix. A team that is not all sitting in the same wp-admin.
Who sits at the desk
Five roles, one record. Access is a property of the role, not a checklist someone has to remember.
Owner
Full controlManager / PM
OperateOperator / developer
OperateViewer
Read onlyClient
Their site onlyA day in the life
How the desk is actually used — by the PM, the operator, the owner, the client, and the static-site sibling that used to live outside the practice.
Monday morning, PM
Opens the portfolio. Two sites degraded. One retainer is out of hours. One client submitted a request from their Maintenance menu. Opens the Site Fiche on the degraded e-commerce site: PHP 7.4 EOL, no backup plugin, two SEO plugins, staging available. Next action is obvious.
Operator
Does not start in wp-admin. Starts on the fiche. Functional fingerprint, theme is a Timber child with a GitHub repo recorded, two inactive plugins to remove rather than update. Runs cleanup, schedules the safe update path for the two active updates, leaves a note on the task against the Business Plus contract.
Owner
Looks at Portfolio intelligence: five sites still on Contact Form 7, three on an “avoid” page builder, a cluster of unknown plugins. Sets the agency preference: Gravity Forms preferred, CF7 legacy. Drift becomes a queue, not a tribal memory.
Client
Logs into their own WordPress, opens Maintenance, sees that updates were applied, hours used, and a report from last month. Asks for a new landing page. The request lands in Orbit as work to review — not as an untracked email.
Static-site sibling
A campaign site lives on GitHub. It has no plugins. It still has a client, a contract, uptime, a Lighthouse score, and a sync status. When production drifts from main, that is a watch-zone event the same way a missing backup is on WordPress.
The stack is yours
Generic “recommended plugins” are how tools nag you into someone else’s affiliate list. Orbit lets you declare how this agency builds: preferred Gravity Forms, Contact Form 7 as legacy, a page builder you will not put on new work.
Deviation becomes a queue. Onboarding a new developer becomes “read the fiche + read the preferences,” not a verbal history of 40 exceptions.
The retainer is in the product
Packages and contracts are not a spreadsheet export. Hours move with tasks. Clients can see the work (or a curated version of it). That is how maintenance stays sellable.
Pricing posture: per site, not per user. Add the whole team. You are charged for the portfolio you actually run.
None of that is billed yet. Orbit is in pilot, and the agencies we onboard now use it free for at least a year.
Mixed stack, one practice
The WordPress shop, the static campaign site, the custom theme that lives in GitHub — one client record, one contract language, one monitoring pane. Different connectors. Same desk.
Not for
Request access.
If you already maintain a portfolio, you are who this is for.