Self-managed websites and online stores
A team writes it by hand. You change it by typing what you want. Both kinds of change land in the same version history: you see a preview before you publish, and if you don’t like it, it goes back to how it was. In seconds.
Demo with sample changes
change «the button in yellow»
change «a dark background»
change «the title on the left»
change «a bigger title»
change «a rounded button»
How it works
Between what you type and what your visitors see there is a review and a preview. Nothing reaches your domain until you say so, and anything that does can be undone.
In your own words, the way you’d say it to a designer. You pick whether the change covers this section, this page or the whole site, and you see what it will cost before anything is generated.
scope: this section · ~1 credit
Before anything compiles, we check which files the change touches and that your content still arrives separately. Whatever reaches a forbidden area isn’t applied, and that part isn’t billed.
comercio/ · sistema/ · out of scope
The change is built and served on a separate domain, kept out of Google, so you can take your time with it on your phone and on your desktop. Your live site stays exactly as it was.
yourname-v19.preview.wixy.app
Publishing moves a pointer: it takes as long as one database query. If something doesn’t sit right, the same pointer moves back to the previous version, and your site with it.
v19 published · v18 one click away
A change that doesn’t compile, doesn’t pass the review or simply isn’t what you wanted stays in the preview and never reaches your visitors. The only way your website changes is you pressing publish.
Two hands, one folder
Not two products, not two websites. The same files, the same theme, the same version history, the same preview and the same publish button. A change of yours and a change from the team stack up in one history, get reviewed the same way and roll back the same way.
Your team, or ours
From their code editor, with Git and the platform’s command line. No limits on what they can write.
You, from your panel
You type what you want to change and a model rewrites the theme code for you. Your content stays untouched.
If your team changes the footer on Monday and you change the hero on Tuesday, nothing gets overwritten: both versions sit in the history, one after the other, and both can be rolled back. And if you both touch the same file, the platform says so before anyone loses work.
The proof
One line of classes. The title and the button text still come from your panel, exactly as before and in the same place in the file. That is the difference between changing the design and rewriting the page.
The underlined parts are content: they’re read from the CMS every time the page is drawn. If a change tries to copy them into the component, the version is rejected and you aren’t charged.
Classes, structure, spacing and animation, in an .astro file your team — or any developer you hire — can open and review line by line. There’s no format of ours to learn first.
With its author, its date, what you asked for and what it cost. The previous one is never deleted: publishing and rolling back are the same move in two directions.
change «the button in yellow»
change «a dark background»
change «the title on the left»
change «a bigger title»
change «a rounded button»
What the AI leaves alone
It’s forbidden in the platform’s own code, above any setting, and it’s checked twice: when the version is saved and again before it compiles. A prompt doesn’t reach there, no matter who writes it.
bloques/ The hero, the gallery, the testimonials, the FAQ: how each piece of your pages looks. layouts/ The header, the footer and the wrappers around every page. componentes/ The theme’s helper pieces, and the look of every form field. estilos.css · tema.json Colors, typefaces, corner radii and spacing: the feel of the whole site, in two files. comercio/ Cart, checkout, account and payment. Whatever charges money lives in the core; the theme only draws it. sistema/ The SEO <head>, the canonical URL and the structured data. The system sets them, not the theme, so a redesign can’t take them away. Form submissions Where the data goes, which fields are required, the antispam and the consent. Validated on the server, always. Your content Titles, copy, prices, products. The AI changes how a title is drawn, never what it says. That’s why an AI redesign can’t break your SEO, stop taking payments or lose an order. And if a change fails validation, it isn’t applied and you get every credit back.
Blocks
No visual builder: you pick the blocks, order them and fill them in from your panel. How each one looks is theme code, and that code is written by your team or by the AI. When a block’s design changes, it changes on every page that uses it.
You write the title in Pages. You ask the AI for “dark background and the button on the right”. The words stay put; the design moves.
You upload twelve photos from the job site and mark the focal point on each one: no crop ever cuts off a head, not on a phone and not on the blog cover.
You ask for “a testimonials section” and the AI writes the component. Adding it to a page is one button, pressed by you, and it’s logged as a content change, not a design one.
You choose which form goes on the page. The theme decides whether the fields sit in one column or two; where it’s sent and what’s required is nobody’s call but yours.
Pick six products by hand, or say “the latest published ones”. Unpublish one and it drops out of the grid without anyone editing the page.
You write the questions and their structured data comes out on its own, ready for Google. Change the block’s design five times and it still comes out the same.
Managed, not held hostage: your website isn’t a canvas inside our server, it’s a folder of files your team can open today and walk away with whenever you decide.
Modules
One panel, showing only what your plan includes. Every module is read, changed and published from the same place, with nothing to install.
Two people buy the last size M at the same moment and only one of them gets it. The price you charge is the one in your database, not the one the browser sends. No transaction fees.
A fifteen-field quote in four steps, with the total adding itself up and the visitor able to come back tomorrow through the same link to finish it.
You change the slug of a page that was already in Google and the redirect writes itself, including the ones for its child pages. The title and the canonical URL are set by the system, not the theme.
You upload a 4 MB photo straight from your phone and get four sizes in AVIF, with a WebP fallback, served by CDN. Alt text is required: without it there’s no accessibility and no SEO.
Your real estate agency needs “viewing hours” on every listing. The team defines it, you fill it in, the theme draws it, and the AI knows it exists but can’t invent another one.
One agency, forty clients, one panel. Each with their own domain, theme, history, library and users, never seeing a single row belonging to the one next door.
Under the hood
Pricing
Free forever, not a trial that expires. No transaction fees, ever. And AI credits are only spent when the change is applied.
$0 /mo
To get started, and to stay as long as you like.
$19 /mo
Your website on your own domain.
$39 /mo
Everything in Professional, and you sell.
$99 /mo
Many clients, one panel, and you decide what gets published.
Prices in US dollars, per month. With no credits left, your published site stays published, the history and the preview are still there, and the SEO analysis keeps working because it costs nothing. The full plan-by-plan comparison is on the Pricing page.
AI credits
A credit is a unit, not a mystery. You type what you want, pick the scope and see what it will cost before you generate. And the cost of every change sits next to its version, in the history.
| What you type | Scope | Credits |
|---|---|---|
| “the main button in yellow” | This section | ~1 |
| “move the form to the top and the map to the bottom” | This page | ~3 |
| “give the whole site a more serious look” | Whole site | ~5 |
Estimates: the real cost depends on what the model reads and writes, and you see it before you confirm.
If the change fails validation, if the model declines or if it cuts off halfway, nothing is applied and you get every credit back. A failure on our side is never on your bill.
Questions
No. You type what you want to change, in your own words, and a model writes the code for you. You see the result in a preview before you publish. The code is there for anyone who wants to read it: your team, a developer you hire, or us.
It’s free forever: one site at yourname.wixy.app, blocks, forms, SEO and 50 AI credits a month. We don’t ask for a card and there’s no deadline. You pay when you want your own domain, an online store or more credits.
It can write a change you don’t like, and that’s what the preview and the rollback are for. What it can’t do is break what matters: the checkout, form submissions and the SEO head are out of its reach in the code, and a change that doesn’t compile or fails validation isn’t applied. Your published site isn’t touched until you publish.
You don’t pay. If the change fails our validation, if the model declines or if it cuts off halfway, nothing is applied and every credit is refunded. And if it generates something you didn’t want, you discard it from the preview and it never reaches your site.
The panel tells you so and spends no credits: “that’s changed in Pages”, with the link. Your hero’s title, your prices and your copy are edited where they’re edited, and that’s exactly why a design change can’t take them down with it.
Yes, in seconds. Every change is a version, whether your team or the AI made it. Publishing moves a pointer, and rolling back moves it back. The published version and the one before it are never deleted, whatever happens to your plan.
Your published site stays published, the history and the preview are still there, and the SEO analysis keeps working because it costs nothing. It only stops generating new changes until next month, or until you ask us for more credits or move up a plan.
No, never, on any plan. You pay your plan and your payment gateway’s fee (Culqi, Mercado Pago or Stripe), which is theirs, not ours. The price your store charges is the one in your database, not the one the browser sends.
You take it with you. Your site is a folder of Astro files, not data on a canvas: your team opens the code with the platform’s command line, from any version; your content comes out through the API as JSON and your form submissions as CSV. If you want it all in one package, we put it together for you. There’s nothing to rescue, because nothing was ever held.
A site at yourname.wixy.app, 50 credits a month and the full history from day one. No credit card and no expiration date.