Edit a WordPress site on the site itself
A plugin, not a page builder. Log in, open any page on your own front end, click the thing you want to change — and the change is written back into the theme file, block or builder document that actually owns it.
Three steps, and one of them is a click
There is no separate editing environment to learn, no staging copy to sync back, and nothing to install on your own machine.
- 01
Install it like any other plugin
No sidecar binary, no desktop app, no build step, no connection back to a machine of yours. It is PHP running on the host the site already runs on.
- 02
Open your own site and click something
Visit an ordinary front-end URL while logged in. The page you edit is the real rendered page, not a preview or a staging copy — so what you are looking at is what a visitor sees.
- 03
The change is written where it belongs
Text, typography, spacing and colour go back into the theme file, the block markup, the template record or the builder's own document — whichever one actually owns that element.
An edit that survives the plugin being removed
This is the part that decides whether a visual editor is worth installing on a site you already run.
No override layer
Most visual editors bolt a stylesheet on top of your site and call it an edit. Deactivate them and the work disappears. PortBay writes into the thing that owns the element, so the change survives the plugin being removed — because it was never the plugin holding it.
It refuses out loud
A write only happens when the plugin can prove which file, record or builder field owns what you clicked. When it cannot, you get a named blocked state saying so, with the reason. It never guesses at a destination and writes there quietly.
Your builder keeps its data
Editing an Elementor section updates the Elementor document. Editing a block updates the block markup. Nothing is migrated, converted or re-saved into a PortBay format, so the builder's own editor still opens the page afterwards.
Permissions are WordPress's
Every edit session is bound to the logged-in user, their session and their capabilities, checked on the server. An editor who cannot edit a theme in wp-admin cannot edit one through PortBay either.
Whatever your site is built in
An element is handed to the adapter that owns it, so a page mixing a classic template, a few blocks and a builder section is edited in place rather than refused as a whole.
Themes
- Classic themes
- Block themes (FSE)
- Self-built themes
Page builders
- Elementor
- Divi
- Bricks
- Oxygen
- Beaver Builder
- Brizy
- WPBakery
- Breakdance
- SiteOrigin
Content
- Gutenberg blocks
- ACF
- Pods
- Custom tables
- Media library
- WordPress 6.7 or newer
- PHP 8.3 or newer
- No sidecar process, no desktop app, no outbound connection to your machine
One licence, one website
A key is scoped to the domain you are managing, and it brings the agent and the forms with it. The editor itself keeps working on an unlicensed site.
One licence per website
A key covers one site — the domain you are managing in WordPress. Run five sites and that is five keys, each activated on its own install, so a licence never straddles clients you bill separately.
AI credits included
The licence carries credits for the in-editor agent. Describe the change in words — rewrite this section, restyle that card, add a row here — and the agent edits the site through the same adapters a manual click uses, so an agent edit lands in the theme file or builder document like any other.
Forms, built and managed in place
Create a form, or open a form the site already has, and edit it without leaving the page it sits on. Responses land in an inbox inside wp-admin, and submissions are checked for bots and spam site-wide.
Signed automatic updates
Licensed installs receive signed updates through WordPress's own update flow. The editor keeps working on an unlicensed site — a key adds capability, it is not a kill switch.
Where this is up to
In development, not yet released
PortBay for WordPress is being built and there is nothing to download yet. Licensing is settled — one licence per website, AI credits and Forms included — but the price is not published, so this page quotes none rather than guessing. Tell us where to write and you will hear once, when it is installable.
PortBay for WordPress
Not yet. The plugin is in development and there is no public release. Licensing is settled — one licence per website, with AI credits and Forms included — but the price is not published, so this page quotes none. Email [email protected] and we will write to you once when it is installable. The PortBay desktop app for macOS is separate and available now.
One licence per website — the key is scoped to the domain you are managing in WordPress, and each site you run takes its own. A licence includes AI credits for the in-editor agent, the Forms builder and its response inbox, site-wide bot and spam checking on forms, and signed automatic updates. Pricing is not published yet; email [email protected] and we will tell you where it lands.
That is what the included credits are for. Describe the change in words and the agent makes it through the same adapters a manual click uses, so the edit is written into the theme file, block or builder document that owns the element — not into an override layer, and not into a draft you then have to apply.
Yes. Create a new form or open one the site already has and edit it in place on the page it appears on. Responses collect in an inbox inside wp-admin, and submissions are checked for bots and spam across the site. Forms are part of what a licence adds.
The Mac app runs local development environments on your machine and dispatches AI coding agents into them; its visual editor works on a project checked out locally. The WordPress plugin installs on a WordPress site and edits that site on its own front end, with no machine of yours involved. They share the editor, not the delivery.
Adapters exist for Elementor, Divi, Bricks, Oxygen, Beaver Builder, Brizy, WPBakery, Breakdance and SiteOrigin, alongside Gutenberg blocks, block themes and classic PHP themes. An element a builder owns is written back into that builder's own document, so the builder's editor still opens the page afterwards.
Your edits stay. They were written into the theme file, block markup, template record or builder document that owns them, not into a PortBay layer sitting on top, so removing the plugin removes the editor and nothing else.
It tells you, and it does not write. A write only happens when the plugin can prove the owning destination; anything else surfaces as a named blocked state with the reason. An element rendered by another plugin's callback, for instance, is identified as that plugin's rather than given a made-up edit target.
WordPress 6.7 or newer and PHP 8.3 or newer. Nothing else — no sidecar binary, no Node process, no connection back to a machine of yours. It is a normal plugin on whatever host the site already runs on.