For web agencies that maintain a real portfolio

Run every client website from one desk.

Orbit Webmaster is made for WordPress. It also handles static websites through GitHub sync. One portfolio, one contract layer, one place to see what is healthy, what is drifting, and what to do next.

Request access See how it works

Connected websites in Orbit Webmaster, with health scores and pending updates. — Your connected websites, health scores, and pending updates in one place.

Per-site tokens
Staging-first updates
AI never writes to production

Forty sites. Forty dashboards. A spreadsheet for the plugins.

A typical agency maintenance week is split across WordPress admins, hosting panels, Cloudflare, an uptime tool, a Lighthouse report, a board for tasks, and a separate place for remaining hours. Static sites live in a GitHub repo nobody looks at until they break.

Updates get applied on production — or skipped — because nobody is sure what the site is made of. A new developer cannot see the stack, the contract, and the last safe action in one view. Clients cannot see what they paid for.

Existing “manage all your WordPress sites” tools centralise some of this. They still treat plugins as a version list, skip your agency’s own stack, ignore the retainer, and leave static sites out.

Blind maintenance

Updates on production, or skipped, because the stack is unknown.

No institutional memory

A new developer cannot see stack, risk, and contract in one view.

No commercial trace

Hours evaporate. Clients cannot see what they paid for.

Two-speed portfolios

WordPress gets some tooling. Static sites disappear until they break.

The operations layer for the portfolio. Not another ping tool.

Orbit Webmaster is the control plane for agencies that look after many client websites.

A dashboard for every site you maintain
WordPress intelligence that understands plugins and themes as a stack, not a list
Remote maintenance, hygiene, and scheduled operations
Hosting and Cloudflare as environments you orchestrate, not tabs you remember
Packages, contracts, and hours so the retainer has a system of record
A client view inside WordPress admin — no extra login
Static sites in the same portfolio, connected through GitHub

It is not a page builder, a host, or an autonomous agent with write access to production.

Orbit Webmaster dashboard showing managed sites, pending updates, uptime and site health.

The loop

Understand. Operate. Prove.

Three moves, in order. Everything in the product sits on one of them.

Understand

Open a client site and actually know it. The Site Fiche shows what the site is, how it is built, what is missing, and whether it still matches how your agency builds. AI writes the briefing. You edit it. Regeneration never silently overwrites you.

Operate

Run WordPress from Orbit instead of forty wp-admins: updates, inactive-plugin cleanup, cache, maintenance mode, one-click admin. Schedule the weekly work. Connect static sites with GitHub sync so they are not the forgotten half of the portfolio.

Prove

Every site sits on a package and a contract. Tasks consume hours. Failed work does not. Clients see the maintenance they pay for inside the WordPress they already use.

Explore the product

Two ways to connect a site. One desk.

WordPress gets plugin and theme intelligence, safe updates, and a portal in wp-admin. Static sites get GitHub, drift, and the same commercial layer.

WordPress

Flagship

Install the Orbit connector. A per-site token authenticates the plugin. From then on the site reports snapshots and accepts the actions you allow.

Add the site
Install the plugin
Paste the token

WordPress in depth

Static

Equal desk

Link the GitHub repository and the production URL. GitHub is the source of truth — the way the plugin is for WordPress. Monitoring, SEO, clients, and contracts attach to the same record.

Add the site
Link the repository
Set the production URL

Static sites

Read a site in five seconds. Act in thirty.

Competitors show update counts. Orbit is built so a PM or a developer can open a fiche and leave with a decision.

Under that: a functional fingerprint (which plugin fills SEO, cache, forms, commerce), a watch zone for missing security, backup, cache, and consent, and the contract sitting next to the stack.

See the Site Fiche

WordPress plugin inventory showing active, inactive and redundant plugins, with available version updates.

Your stack, encoded. Then every site that drifted.

Orbit ships a global Plugin Directory and Theme Directory so “SEO plugin” is not a slug. On top of that, you set how your agency builds: preferred, acceptable, legacy, avoid — per role.

Portfolio view then answers the questions a version list cannot: which sites still run Contact Form 7, which ones carry two caches, which ones drifted from the stack you actually sell.

Preferred

Gravity Forms

What you put on new work

Acceptable

WPForms

Fine to keep, not to start

Legacy

Contact Form 7

On the drift queue

Avoid

That page builder

Do not put on new sites

AI writes the briefing. You still decide.

Orbit uses AI to describe sites, classify unknown plugins, and summarise Lighthouse reports. It does not push production.

Typed actions, permissions, and (for updates) a staging-first path are how work runs. Humans confirm anything that changes a live site or the global directories.

How we handle safety

AI output is a draft. Operators edit.
Manual text is never silently overwritten.
Directory changes need a human.
The model never gets a raw write-handle.

A Monday at the desk.

Orbit is built around the people who actually run the portfolio — not a single wp-admin hero.

PM

Opens the portfolio. Two sites degraded. One retainer is out of hours. One client submitted a request from their Maintenance menu. The Site Fiche on the e-commerce site makes the next action obvious.

Operator

Does not start in wp-admin. Starts on the fiche: fingerprint, Timber child, inactive plugins to remove rather than update. Cleanup, then the safe update path, on the contract.

Owner

Portfolio intelligence: five sites still on Contact Form 7, three on an avoid builder. Preference becomes Gravity Forms preferred, CF7 legacy. Drift is a queue, not tribal memory.

Client

Logs into their own WordPress, opens Maintenance, sees the work and the hours, asks for a landing page. The request lands in Orbit — not as an untracked email.

For agencies

Built for agencies with a maintenance practice.

If you look after about ten sites or more — WordPress at the core, static sites in the mix — Orbit is the desk that should replace the pile of tools.

Priced on the portfolio, not on seats: add the whole team.

Orbit is in pilot. Agencies we onboard now use it free for at least a year, while the pricing gets settled with the people actually running it.

For agencies

Maintenance you can prove.

Request access and we will show you the desk with your kind of portfolio in mind.

Request access Compare to a typical WP manager