PlugPress
Saddle Pro: AI That Builds Real Divi Pages
Saddle Pro teaches your AI assistant to build real Divi 5 pages. Not HTML pasted into a Code module, and not a layout only the AI can edit — actual Divi modules, in actual sections and rows, styled with your site’s actual global colors and presets, that open in the Visual Builder exactly like a page you built by hand.
Free Saddle already gives an AI safe access to your posts, pages, media, and Gutenberg blocks. Pro is for sites built with Divi, where “edit this page” means editing a builder layout that free Saddle can read but not compose.
What does Saddle Pro actually add?
47 Divi-native tools, on top of the 61 the free plugin already provides. They cover the whole Divi 5 surface an agent needs to build a page and keep it on-brand:
| Area | What the AI can do |
|---|---|
| Modules | Read a page’s module tree, add, edit, move, and remove modules — addressed by position, so it can change one module without rewriting the page |
| Design system | Read and manage Divi Global Data: global colors, global fonts, design variables (tokens), and module presets |
| Presets | List, apply, create, edit, delete, and set the default style preset for a module type |
| Library | List saved layouts, insert one into a page, save a new one, delete one |
| Theme Builder | List templates, set their assignment conditions, delete templates |
| Loops | Enable, configure, and disable Divi’s Loop on a module — query type, source, and settings |
| Dynamic content | Bind a field to a dynamic source, or clear the binding |
| Display conditions | Show or hide a module by rule |
| Design checks | Commit a design brief up front, then verify, lint, and render a page against it |
Everything is a defined, gated tool. Saddle Pro never executes code an agent supplies — there is no PHP eval, no shell, no arbitrary-code path anywhere in it.
How does an AI build a Divi page with Pro?
The point of Pro isn’t a bigger tool list — it’s that the AI stops guessing. The working loop looks like this:
- Read the site’s Divi memory. One call returns the module catalog (including any module packs you have installed), your global colors, variables, presets, fonts, and site conventions — so the assistant knows your brand before it designs anything, in every new session.
- Commit a design brief. The palette, the accent budget, the radius, spacing and type scales get written down before building. Every later check holds each module to that brief.
- Build with real modules. Section recipes — hero, features, pricing, testimonials, call to action, FAQ — build as genuine section → row → column → module structures, ready to fill in. Where a purpose-built module exists (an info box, a pricing table, a carousel), the AI is guided to use it rather than faking one out of headings and buttons.
- Verify and fix. Every write reports which fields and style paths were actually applied and which were silently ignored, checked against the module’s real schema — so a mistyped setting surfaces immediately instead of quietly doing nothing. Then verify scores the saved page and lint reports concrete design fixes, each at its exact module address.
The checks catch the things that make AI pages look like AI pages: rows of identical centered cards, off-palette colors, ad-hoc sizes, over-budget accents, and modules bound to a global preset while locally overriding it.
How do I activate my license?
Install and activate Pro alongside the free plugin, then open Saddle → License in your WordPress admin — Pro adds that tab to Saddle’s own screen. Paste the key from your purchase email (or your PlugPress account) and click Activate. The Plugins screen also carries a License link next to Saddle Pro that lands in the same place.
Once active, the page shows the last four characters of the key, the expiry date if the license has one, and buttons to Check for updates or Deactivate — deactivating frees the seat for another site. The full key is never stored anywhere it could be read back.
Is the safety model the same?
Yes — Pro adds tools, not exceptions. Every Divi tool runs through the free plugin’s machinery unchanged:
- Access levels apply. Page-level editing needs Reading & writing. Anything site-wide — global colors, fonts, variables, presets, the Theme Builder — is Managing the site, the highest level, because changing one global color changes every page that uses it.
- Deletions still preview and ask first. Deleting a global color, a variable, a preset, a library item or a Theme Builder template goes through the same two-step approval gate as deleting a post. Divi’s built-in colors, font variables, and default presets are protected outright.
- Per-tool switches apply. Every Divi tool appears on the Permissions screen and can be turned off individually.
- Everything is logged in the same activity log as core content changes.
What about other page builders?
Free Saddle handles Gutenberg blocks natively — no Pro needed. Pro handles Divi 5. If an AI tries to lint, verify, or render a Divi page without Pro installed, it gets told exactly that rather than failing silently.
Divi’s support is built behind a builder-driver interface rather than hardcoded, which is the groundwork for Elementor and Bricks later — but neither is supported today. Divi 4 layouts are not the target either; this is Divi 5.
Does Pro add tools from my other plugins?
One: Knovia, the documentation plugin — with Pro active, an AI can create, organize, and update knowledge-base docs and categories. (These docs were written that way.)
It’s worth being clear about what is not Pro, because it’s easy to assume otherwise:
| Capability | Free Saddle | Needs Pro |
|---|---|---|
| Posts, pages, media, taxonomies, search | ✔ | |
| Gutenberg block editing, design tokens, patterns | ✔ | |
| Skills — installable playbooks | ✔ | |
| Memory | ✔ | |
| Activity log | ✔ | |
| Site management — plugins, themes, options, cache | ✔ | |
| Unsplash search and import | ✔ | |
| Waggle — SEO & AEO tools | ✔ | |
| Mailyard — email tools | ✔ | |
| OAuth sign-in for ChatGPT | ✔ | |
| Knovia — documentation tools | ✔ | |
| Divi 5 page building — 47 tools | ✔ |
Waggle and Mailyard bridge through the free plugin’s integration engine. See Permissions and Access Levels for how every one of these is gated.
Does anything leave my site?
Your content and your AI’s tool traffic never do. Pro adds exactly one outbound call the free plugin doesn’t make: a license and update check to Freemius, the account layer you buy and activate Pro through. It carries licensing information only — never your site’s content, and never anything about what your AI did.
Pro is an add-on of the free plugin, not a replacement: it requires free Saddle 1.0.0 or newer, and both stay installed and active together.
FAQ
Do I need Pro to use Saddle?
No. Free Saddle is complete on its own — nothing in it is locked, limited, or nagging you to upgrade. Pro matters if your site is built with Divi 5 and you want the AI building real builder layouts.
Will pages the AI builds still be editable by hand?
Yes — that’s the whole point. Pages are composed as real Divi modules through Divi’s own APIs, so they open and edit in the Visual Builder normally. You are never left with a layout only the AI can change.
Can the AI change my brand colors by accident?
Not without the highest access level. Global colors, fonts, variables and presets are site-wide, so they sit behind Managing the site, and deleting any of them previews and asks first. At the default Just reading level the AI cannot change anything at all.
Does Pro work with third-party Divi module packs?
Yes. The AI is told which packs are installed and is guided to prefer a purpose-built module from them — an info box, a pricing table, a carousel, a gallery — over composing something generic from primitives.
Where do I enter my license key?
Under Saddle → License — Pro adds that tab to Saddle’s admin screen once both plugins are active. Older Pro builds put it on its own settings page instead; updating Pro moves it into Saddle where the rest of your setup lives.
Saddle Pro says it needs a newer Saddle than exists.
That’s a version-check bug in Pro 1.2.0, not a missing free release. Update Pro to 1.2.1 or newer and the builder tools return on their own — the free plugin was never the problem. Details in Troubleshooting.
My license won’t activate — it says the plugin does not exist.
That’s a defect in Pro 1.3.0, which shipped pointing at the wrong product record. Update to 1.4.0 or newer and activation works; sites you activate also start appearing in your PlugPress account again.
What happens if my license expires?
You stop receiving automatic updates. Nothing about your site or your existing pages changes.