For agencies and freelancers who maintain WordPress
Change the WordPress site everyone’s afraid to touch.
Flux copies a client’s live site to a private preview on your machine, makes the change you describe, and publishes only what you reviewed. Old theme, forty plugins, page builder and all.
Limited assisted pilot · Needs SSH access to the host and Docker on your machine
- Read 3 veterinary products from the shop
- Built the page in Elementor, 5 sections
- Added it to the Main menu
- Checked /veterinary-pumps/ in the preview
The page is ready in the preview. Nothing has been published. Open Changes when you want to review it.
Veterinary Infusion Pumps
New and refurbished pumps for small-animal practices, bench-checked before they ship.
Shop vet pumpsTriumph IP12
Triumph SP12
PETite Heat
The inherited site
Every agency has one.
The developer who built it left years ago. It runs a marketplace theme, forty plugins and a page builder three layers deep. The client wants one small change, and everyone knows small changes are how the checkout breaks.
01
No repo, no history
AI code editors start from a git repository. This site is a live server and a database, and it’s the only copy.
02
Staging that drifted
The staging copy is months behind production, so testing there proves very little.
03
Updates on production
Plugin updates run on the live site at 4pm on a Friday because there’s nowhere else to run them.
04
The builder owns the page
The content lives inside page builder data, not in template files anyone can read.
How it works
A copy you can break. A publish you can trust.
Flux never experiments on the live site. It works on a private copy, and the only way back to the client’s site is a review you sign off.
01
Connect
Add the host’s SSH login. Flux finds WordPress, reads the theme and plugins, and stays read-only. That’s enforced by the engine, not by a greyed-out button. Credentials stay in your system keychain.
Connection
Server key verifieded25519SSH signed inWordPress found/public_htmlTheme, plugins and builder readElementor ProRead-only until a preview exists
02
Preview
Flux copies the files and database into a private preview on your machine, running in Docker on the site’s own PHP version. Hosting credentials and caches stay behind. Big sites are fine: IPR Medical’s is 4.2 GB of files and a 589 MB database.
Local preview
Database export589 MBFiles copied and hashed4.21 GBWordPress running locallyready127.0.0.1 · matching PHP · URLs rewritten
03
Change
Describe the change in plain English. Flux edits theme files, Elementor sections, pages, menus and product categories in the preview. You approve each edit; Flux snapshots before writing and reads the result back.
Chat
The shipping banner on the cart page is out of date. Change it to free shipping over $500.
Found the banner in Elementor, cart pageEdited the heading in the previewChecked /cart/ renders20004
Review and publish
Pick the changes to ship. Flux shows the diff, checks the live site hasn’t changed since the copy, writes only your selection, reads it back, and keeps a record so you can revert.
Publish review
- Free shipping on orders over $250
+ Free shipping on orders over $500
Live value matches the copyWritten and read backRecovery record savedrevertable
What agencies use it for
The jobs you’ve been putting off.
Plugin updates, rehearsed first
Run the update on the copy, click through the site, and find out what breaks before the client does.
“Rehearse the latest WooCommerce update and tell me whether the shop and checkout still render.”
Elementor edits and new pages
Find a supported classic section, change it in place, and keep the theme’s own styles. Test new Atomic pages only on a compatible pilot setup.
“On the Service page, replace the second testimonial with the new one from Dr. Patel and tighten the heading.”
Pages, menus and product categories
Create pages, add them to an existing menu, and set up WooCommerce product categories.
“Create a Veterinary page, add it to the main menu after Shop, and put the three vet pumps in a new Veterinary category.”
Questions about the live site
Ask why a page is slow, what a plugin does, or where a piece of text comes from. Before a preview exists, Flux can read but can’t write.
“Where does the “Request a quote” form on product pages come from, and what happens when someone submits it?”
Cloudways staging, handled
Flux finds the staging app for a site, takes a backup, and syncs code or tables when you approve it.
“Push the approved changes from staging to production and verify the homepage afterwards.”
WPBakery pages
In progressInspect and edit WPBakery rows, columns and elements without regex surgery on shortcodes.
“Swap the hero image on the About page and update the intro paragraph.”
Safety, in writing
What Flux guarantees, and what it doesn’t.
Agencies get burned by tools that promise too much. Here’s exactly where the lines are.
Enforced by Flux
- Flux can’t write to a client’s site until you’ve made a preview. The engine enforces it, even with auto-approve on.
- Approving an edit in chat only changes the preview. Publishing is a separate review you sign off.
- Cloudways staging syncs always stop for your approval, and Cloudways takes a backup before they run.
- A publish writes only the files and values you selected. It never replaces the live database.
- Before writing, Flux checks each target still matches what it copied. After writing, it reads the result back.
- If a write fails, Flux rolls back what it changed and tells you anything it couldn’t restore.
- Published file and value changes can be reverted through another review.
Not promised yet
- A lock on the whole site. The check and the write are separate steps, so an editor saving the same thing in that moment can be overwritten. Conflict-aware publishing is on the roadmap.
- One transaction across files and database. A failed publish can leave partial changes, which Flux reports rather than hides.
- Proof the page looks right or checkout works. A working preview and a clean read-back still need your click-through.
- Keeping client data off your machine. Orders and customers are never published, but the preview copy of the database lives on your machine, so treat it like any machine with client data.
Customer story
IPR Medical’s store, running on a laptop.
IPR Medical sells new and refurbished IV pumps to hospitals and vet clinics through a WooCommerce store on Cloudways. It was too big for the first version of Flux, so we rebuilt how Flux copies large sites around it.
Read the story- of site files copied and hashed
- 4.2 GB
- database running locally
- 589 MB
- Cloudways apps paired, production and staging
- 2
How it fits
Another tool in the agency workflow.
AI code editors
A strong choice when a repository is the source of truth. Flux is aimed at a different shape of work: a running WordPress installation whose behavior also lives in its database, page-builder data, plugins and hosting environment.
Host staging
Excellent for server-level testing and a familiar choice for agency teams. Flux adds a private local preview and a change-level review. Its Cloudways integration can also inspect and run explicitly approved staging operations when the required API access is available.
Page-builder AI
Convenient for supported content and layout work inside that builder. Flux is designed for maintenance jobs that may cross the theme, plugins, menus, WooCommerce data and supported builder structures in one reviewed workflow.
Pricing
Priced per site, like your retainers.
Every plan includes the full preview and publish workflow. Plans differ by how many client sites you connect and who else on your team uses Flux.
Free
Try Flux on one real site, including publishing.
$0forever
- Sites
- 1 site
- Seats
- 1 seat
- AI
- Your own AI key
- Full local preview of the site
- Reviewed publishing with drift checks and rollback
- Supported Elementor edits, pages, menus and product categories
- Plugin update rehearsals
Freelancer
For one person keeping a book of client sites healthy.
$39per month
- Sites
- 10 sites
- Seats
- 1 seat
- AI
- $10 of hosted AI a month (about 25 jobs), or your own key
- Everything in Free
- Cloudways staging workflows
- Hosted AI, billed in dollars
- Email support
Agency
For a team that maintains sites for a living.
$129per month
- Sites
- 40 sites
- Seats
- 5 seats
- AI
- $30 of hosted AI a month (about 75 jobs), or your own keys
- Everything in Freelancer
- Shared billing and usage controls
- Spend caps per seat
- Priority support
Studio
For larger agencies and in-house web teams.
Custom
Annual agreement
- Sites
- 100+ sites
- Seats
- Custom seats
- AI
- Custom AI terms
- Everything in Agency
- Security requirements scoped in your agreement
- Invoicing and procurement
- Onboarding for your team
Founding agencies. The founding rate is documented for launch, but checkout is closed during the assisted pilot. Applying does not reserve or start a paid plan.
Questions
What agencies ask first.
What does Flux need from the host?
Can Flux change a client’s live site without me?
Where does the preview run?
Which page builders does it edit?
How big a site can it handle?
Which AI does it use?
Pick the site you’ve been avoiding.
Bring it to the assisted agency pilot. We will validate the setup, complete the first reviewed change with you, then test whether your team can repeat the workflow independently.