This past week I finished moving Allioo Studio from Wix Studio to Wix Managed Headless, and the move turned into more than a new frontend. I built myself a dashboard with sales data Wix never gave me, I finally have a custom blog, and I came away with a clear opinion on where Harmony, Studio and Headless each fit, and what Wix still needs to fix.
How I got here
I didn't find Wix Headless through Wix's marketing. A partner in the Wix Studio group introduced me to it, and I dove in to move Allioo.com, my real estate platform, over to it.
I had built Allioo.com on Wix Studio, but with how fast AI tools were moving, I felt like I was moving too slow, and Wix Studio genuinely wasn't built for what I was building. So back in April, I moved to Wix Headless, the plain version, not Wix-managed. Building that custom frontend is what introduced me to Cursor and Claude Code, the AI coding tools I now run most of my work through. I connected a custom frontend to Wix's backend, but I couldn't see any of that activity in the Wix dashboard. It felt disconnected from the rest of what I run on Wix.
I ended up not using it for long. Not because it didn't work, but because I didn't understand yet why I'd need it over just building the whole thing myself. I found out why later, which is its own section below.
Wix Managed Headless vs. self-managed Headless: what actually changes
After the Allioo.com experience, I went back and looked at what Wix actually documents as the difference, and it explains exactly what I ran into.
With self-managed Headless, you bring your own framework and host it yourself. You're responsible for configuration, authentication and hosting, connecting to Wix's backend through its SDK or REST API. You get Wix's business APIs, eCommerce, bookings, the CMS, but none of the managed pieces: no managed hosting, no built-in analytics tracking, no error or log monitoring, no automatic authentication, nothing showing up in the Wix dashboard alongside the rest of your business.
With Wix-managed Headless, Wix hosts, deploys and runs the frontend for you. Build with Astro and you get automatic authentication, built-in SEO, secrets management, analytics tracking and error monitoring, all included, and all visible in the same dashboard as everything else you run on Wix.
That's the whole difference in practice. Self-managed hands you the backend and leaves you to wire up everything else yourself, API by API, platform by platform. Wix-managed keeps it one ecosystem. For someone who already knows Wix well and wants to live inside it, managed is the easier, and usually cheaper, path: you're not stacking a separate hosting bill, a separate analytics tool and a separate auth provider on top of your Wix plan. You get Wix Forms, Wix Bookings and the rest of the ecosystem included, with one monthly or yearly payment instead of several.
How to actually start one, or convert what you've got
There are two ways in. Start a brand new Headless project from the Wix dashboard and pick self-managed or Wix-managed (Astro) at setup, then build the frontend from scratch. Or, if you already have a Wix Studio or Editor site, convert it in place, which is what I did with Allioo Studio.
Here's the actual path for converting an existing site: open the site in your Wix dashboard, go to Settings, then Headless, and choose Start Migration. Wix turns your existing site into a Headless project without you rebuilding anything from scratch. If it doesn't work out, the same Settings, Headless menu has a Switch back option that reverts the site to its normal Wix Editor setup. I tested both directions on Allioo Studio. Converting was easy, and switching back worked cleanly too.
On pricing: starting a Headless project doesn't require a paid plan. You only need to upgrade once you want to accept payments, connect a custom domain, or pull deeper analytics, the same limits that apply to Wix-managed Headless generally. The part Wix hasn't made simple yet is plan carryover, not price. More on that below.
The dashboard and the blog I finally have
I built myself a dashboard, and I'm building one for clients too, so I can hand off a finished site and still get credit for the work. On my own side, I pulled in numbers Wix's dashboard doesn't show: template and app sales by day, which month and which day sell best, the price point that sells most often, and which templates actually carry the business. I can also see every site I'm a collaborator on in one place.

The bigger win was a custom blog. Wix Studio and the standard Wix editor never let me build the blog I actually wanted. On Headless, that's solved. Correction from the video: I said blog views weren't flowing into the dashboard. That turned out to be my own setup mistake, not a Headless limitation, and I've since fixed it. Views show up now.
That's the trade-off I'd tell anyone weighing Headless: you lose the drag-and-drop editor, and you get a backend shaped around how you actually run your business instead of how Wix assumes you run it.
Why I'm taking on custom work now
Client work isn't naturally where my energy goes. I'd rather build systems than manage back and forth with people. But template sales have cooled this year, so broadening into custom projects alongside templates is the realistic next move.
The plan is to build the systems first so the custom work doesn't become unsustainable: the dashboard above, plus a handover process for client sites. One thing I learned the hard way: duplicating a Headless site doesn't carry over the custom frontend code, only the Wix backend. I'm still working out a workaround for handing off finished custom builds, and I'm not yet sure whether Wix's partner revenue share applies to Headless plans at all. I'll update this once I know.
Why one place matters
The usual stack for a custom site is a place to host it, a domain, a backend, something like Vercel, and a handful of other platforms to get everything live.
Wix-managed Headless gives you hosting, the business tools and one dashboard in a single account. Wix puts it this way:
Build with anything, manage in one place.
That's why I've always stayed with Wix: the ecosystem.
Fair point: you don't have to give up other tools to get it. Wix documents building the frontend with tools like Base44, Lovable, Bolt or v0, with Wix running the backend.
Harmony, Studio and Headless: different jobs, not a contest
Wix now has three serious ways to build, and I don't think they compete with each other so much as split the work by who's building.
Wix Harmony is the AI-assisted editor Wix built for people who've never built a site before. You describe what you want and it builds a starting point, no design background needed.
Wix Studio is the workspace for agencies and freelancers running multiple client sites at once: drag-and-drop design control plus a dashboard built around managing projects, clients and teams. It launched in 2023 and has crossed a million agency and freelancer accounts since.
Wix Headless is for people who want to keep Wix's backend (eCommerce, bookings, the CMS, the dashboard) but build the frontend themselves, in whatever framework they want. That's where Allioo Studio lives now.
Worth mentioning here: Base44, the AI app builder Wix bought in 2025, is basically a no-code version of what I did by hand. It builds a custom Wix dashboard or an AI agent from a plain language prompt, pulling directly from your live Wix site data. I coded mine because I wanted full control, but it's a sign of how far Wix's ecosystem now reaches: the same backend, reachable through a visual editor, an AI prompt or raw code.
Studio 2 is the next version of Studio, and I'm genuinely excited for it. Wix hasn't published details publicly yet, but from what I know, it's headed toward a more AI-native editor built for designers and professionals. Once it's out, my plan is to offer both Studio and Headless, not pick one over the other.
If you're choosing between them: pick Harmony if you've never built a site and want AI to hand you a working starting point. Pick Studio if you're an agency or freelancer running multiple client sites and want full design control plus client management tools. Pick Headless if you already know Wix and want your own frontend framework while keeping Wix's backend. And if you're on Studio today and just want more AI assistance without rebuilding anything, Studio 2 is the one to wait for.
What the research says
A few technical points worth knowing, not a lecture.
- Wix-managed Headless handles hosting, scaling and security for you. Build with Astro, the framework Wix recommends, and it also handles login, SEO and analytics tracking.
- Changes you make in the dashboard show up on the live site right away. You don't need to push a new release for a content change.
- Limits to know: you only need a paid plan once you want to accept payments, connect a custom domain, or see deeper analytics. And some Wix apps don't work on a Headless frontend yet, including Hotels, the Loyalty Program and Smart Chat.
What I'd ask Wix to do
Step back from the day to day and the product itself holds up. What needs tightening is the pricing structure around it.
Right now Harmony and the standard Wix Editor run on the same pricing plans, while Wix Studio runs its own, separate, higher-priced plans. I tested this myself: only Premium (Editor-tier) plans currently carry over into a new Headless project. Studio plans don't. You can still get a Studio site onto Headless, just not by starting a new Headless project under a Studio plan, by converting the existing site through Settings instead (the steps are above), and you can switch back if it doesn't work out. But starting a fresh Headless project on a Studio plan is backwards to me: Studio and Headless are both built for the more advanced builder, so if anything, Studio should be the plan that transfers.
One plan, with everything else (Studio's agency tools, Headless project access, deeper analytics) sold as add-ons on top of it, would be simpler for everyone, and would stop Wix's own product lines from competing with each other on price.
Make it easier to add a Headless frontend to an existing Studio or Editor site, not just start fresh. And keep pulling partner feedback into the roadmap. The people building on Wix every day are the ones who'll notice the rough edges first.
Where this leaves Wix
Wix Managed Headless gave me a backend I own, a blog I've wanted for years, and a dashboard that actually tells me how my business is doing. It's also pushed me toward custom work I wouldn't have picked on my own, which is turning out fine so far.
I think Wix is in a strong spot going into this next stretch. Harmony now runs on its own proprietary AI model, one Wix built in-house specifically to power Harmony's design engine, which Wix says lowers its own costs and lets it iterate faster. Add Base44, the AI app platform Wix bought and is building its own model for too, plus Headless tying a fully custom frontend to all of it, and you've got one company covering the AI-native, no-code and full-code ends of building at once.
Questions
What's the difference between Wix Headless and Wix Managed Headless?
Self-managed Headless gives you Wix's business APIs but leaves hosting, authentication and analytics to you. Wix Managed Headless hosts and runs the frontend for you, with login, SEO, secrets management, analytics and error monitoring included and visible in the Wix dashboard.
Why did I move Allioo Studio to Wix Headless?
Wix Studio wasn't built for how fast I wanted to move, and I wanted a backend shaped around my business, not the standard editor's assumptions, plus a custom blog and my own sales dashboard.
Will Wix Studio and Wix Headless both stay in my toolkit?
Yes. Once Studio 2 ships, the plan is to offer both Studio and Headless depending on the project, not pick one over the other.
If I duplicate a Headless site, does the custom frontend code come with it?
No. Duplicating only copies the Wix backend, not your custom frontend code. I'm still working out the best workaround for handing off finished client builds without rebuilding the frontend each time.





