Questions agencies actually ask.

It is made for WordPress — that is the depth. It also handles static websites through GitHub sync, in the same portfolio, on the same contracts.

We replace the “many wp-admins plus a spreadsheet plus a retainer in someone’s head” pile. If all you need is bulk plugin updates on production, you already have tools for that. Orbit is for understanding, hygiene, safe operations, and proof of work.

A thin connector plugin. Tokens per site. The product lives on the server. Remove the plugin and the site disconnects; your history stays.

You link the GitHub repository and the production URL. GitHub is the source of truth. We do not replace your deploy pipeline.

No. AI drafts descriptions, suggests classifications, and later proposes plans. Humans confirm. Typed actions execute. Manual text is never overwritten by a regenerate.

For WordPress, they don’t — not to Orbit. They use their existing wp-admin. Maintenance is a menu there. They can request work. They cannot run it.

Orbit is in pilot. Agencies we onboard during the pilot use it free for at least a year from the day they connect their first site — no card, no seat count. When pricing lands it will be per site, not per user, with unlimited team members, and pilot agencies hear about it before anything changes.

You connect a real portfolio, not a test site, and you tell us where the desk is wrong. That is the whole deal. There is no minimum commitment and no obligation to buy when pricing exists — pilot agencies are how the pricing and the roadmap get set.

Not as a sharing layer. We will not help mutualise paid plugins across sites. Entitlement tracking, if it comes, stays inside that rule.

Single-site owners, and anyone who wants an unsupervised agent on production.