For agencies
All your clients’ websites, in one panel.
Each client gets their own domain, theme, version history, media library and users, and never sees anything of anyone else’s. Your team works from their code editor and the command line; the client proposes changes through AI and you decide what gets published. Unlimited clients, 5 published sites included and $15 for each one after that.
Every version can be previewed, compared and restored.
- v21 You · AI You added testimonials published2 hours ago
- v20 Team Mobile responsiveyesterday
- v19 You · AI You changed the hero3 days ago
- v18 Team Initial design2 weeks ago
Three ways of working
How does your agency work today?
I maintain WordPress sites
1
installation for all your clients; every website with its own separate build
Twenty installs, twenty sets of plugins to update, and one that wakes up down every month. Here there’s a single installation of the core for all your clients, and what is per client is their website: it’s built, previewed, published and rolled back on its own. Whatever a client breaks stays on their site, never on anyone else’s and never in your panel.
I design in a visual builder
2
hands on the same folder: your team in code, your client through AI
Fast to deliver, and then the client calls you for every change, or goes in and moves the hero at eleven on a Thursday night. Here the design is code your team writes with Astro, React and Tailwind, and the client changes it by typing what they want, within what you allow. Both changes go into the same history, one after the other, and neither overwrites the other.
I sell websites and want monthly revenue
$15
per published site beyond the 5 included in the Agency plan
Charging once for the website and maintaining it for free is the model that burns agencies out. With a monthly plan you sell maintenance that’s worth something: AI changes with the plan’s credits, the full history, a preview to sign off on and rollbacks in seconds. Unlimited clients for $99 a month; the marginal cost is $15 per published site, and there is no other.
A new client
From the kickoff call to the client’s domain, with nothing to set up
No server to rent, no install to prepare, no plugins to choose. You create the client and your team keeps working in the editor they already use.
-
You create the client
Their account is born with their domain, their theme —which starts out inheriting from the base one—, their library and their users. Nobody on that account sees anything of another client’s, not even by mistake.
inherits from: base
-
Your team opens their website
One command materializes the code on the machine of whoever is going to touch it: the base theme read-only, and that client’s own pieces on top of it.
mc abrir clinica-san-jose
-
Every save is a version
With its author, its date and its note. Saving requires starting from the latest one, so if someone saved in the meantime it tells you and lets you compare.
mc guardar -m "New hero"
-
Preview first, and you publish
The preview opens on a separate address for the client to sign off on. Publishing moves a pointer, and rolling back is the same move in reverse.
mc previa · mc publicar
After that the client goes into their panel and changes what’s theirs: the content always, the design if you grant it, and never the checkout folder or the system one. All four steps land in the same history as their changes.
Approval workflow
The client proposes. You publish.
It’s the difference between handing your client a key to the house and a key to the workshop. With the approval workflow they generate through AI, review it in their own preview and request publication; you compare, approve or reject with a comment, and publish when it’s ready.
-
You set it per client, not per plan
The one who’s been with you three years publishes directly; the one who had a scare goes into approval, without changing their plan.
-
And you decide who touches the design
Every user carries a permission: none, propose or publish. The person writing the blog doesn’t redesign the site, and granting it is logged.
-
Freeze the design while you rebuild their site
During a big redesign their AI doesn’t generate and they’re told why. You turn it on and off yourself, when you’re done.
What do you want to change?
Preview ready · v22
For agencies
What an agency needs, and can’t find anywhere else
Each card is a situation from an ordinary Tuesday, not a definition.
-
Many clients, one panel: See security
Log in once and they’re all in front of you. Each with their own domain, theme, history, library and users, isolated in three layers all the way down to the database itself. A user from one client can’t see anything of another’s, not even by typing the address by hand.
-
Log in to a client’s account, with an audit trail
They call because “the form isn’t showing up”. You open a session as their owner for one hour, with a permanent banner on screen and a log entry on the way in and on the way out. Anything you change inside carries your name and theirs: it never shows up as if they did it.
-
Your team works in their own editor: See the version history
Astro, React and Tailwind, in everyone’s own editor and on the command line they already use. One command materializes a client’s website on disk; every save is a version with an author, a date and a note.
-
A client published something odd on a Sunday: See versions
Rolling back moves a pointer to the previous version, which is still saved. And if the new version fails to start, the platform goes back to the previous one on its own, documents the rollback and notifies you, without anyone having to watch.
-
A new block, on every client who uses it: See the blocks
You write the “medical team” block once and any client who puts it on a page has it. And when you improve the base theme, the improvement reaches the clients who didn’t customize that piece on its own, a test group first.
-
You know where every credit went: See pricing
The Agency plan comes with 2,000 AI credits a month. Every change is logged with its client, its user, its prompt and what it cost, and there’s a daily cap per user so that one enthusiastic Monday doesn’t eat the whole month.
Two hands, one folder
Your team writes the code. Your client changes it by typing. Nothing gets overwritten.
On Monday your developer changes the footer from their editor. On Tuesday the client asks the AI for “a dark background on the hero”. Both versions sit in the same history, one after the other, with their author and their origin. If they both touch the same file, the platform warns you before anyone loses work: nothing is merged on its own inside a file.
- Four origins in the history: team, client through AI, client by hand, and system
- Lock a file and the client’s AI no longer touches it, even if they haven’t customized it yet
- The commerce folder and the system folder are out of reach of any prompt; it isn’t a box you can uncheck
- If your team has that website open, the client’s panel tells them before they generate
change «the button in yellow»
change «a dark background»
change «the title on the left»
change «a bigger title»
change «a rounded button»
The promise
Your team is still your team.
There’s no new platform to learn in order to work: Astro, React and Tailwind, everyone’s own editor and the command line. What changes is that every save is now a version of that client’s site, with its author and its note, and that publishing and rolling back stopped being frightening.
Whatever a client breaks stays with that client. Separate build, separate process, separate artifact.
Questions
What an agency asks
How many clients can I have?
Unlimited, on the Agency plan. What counts is published sites: 5 are included in the $99 a month, and each one after that is $15. A client who hasn’t published yet doesn’t count.
Do my clients see the Wixy brand?
Today, yes. The panel carries the Wixy brand and there’s no white label in this version. What is yours is the relationship with your client: you create their account, your team writes their code, you decide what gets published, and they never see anything of another client’s.
Can one client break another client’s website?
No. Each client is isolated in three layers: a foreign key on every table, the panel’s access control, and row-level security in the database itself. Their site is built in a separate container with no credentials and no network, and served from its own process with a token that only reaches their published content. Whatever a client breaks stays on their site.
What if a client publishes something broken?
If the build fails, the version is marked as failed and their published site isn’t touched. If the new version fails to start, or racks up errors in its first few minutes, the platform rolls back to the previous one on its own, leaves a “system” version documenting it, and notifies you. And you can roll back any client in seconds, always.
Can I make changes by hand while the client keeps using the AI?
Yes, that’s the idea. Your team saves versions from the command line with the origin “team”; the client generates theirs through AI. Saving requires starting from the latest version, and if someone saved in the meantime, the platform says so and lets you compare. For a big redesign, you freeze the client’s design until you’re done.
How do I know where the AI credits go?
Every generated change is logged with its client, its user, its prompt, its scope and what it cost, next to the version it produced. There’s a daily cap per user, and only the users you grant design permission to can generate at all. Plan credits renew every month and don’t carry over; if a client runs out, their published site stays published and the SEO analysis keeps working.
Unlimited clients, five published sites and one panel for all of them.
Agency plan at $99 a month, $15 per extra published site and 2,000 AI credits a month. We’ll show you on a real website, not a demo.