Talk to us

Blog · 16 November 2026 · Rob Sherwood

Mozilla's Solo Shuts on 30 November. What Do You Own?

Mozilla's Solo, the AI website builder for sole traders, closes on 30 November. Every site and all its data gets deleted that day. If you've got a site on it, you have two weeks. If you've got anything else on an AI builder or hosted platform, it's a good moment to ask what you'd actually walk away with if that one closed too.

What's happening with Solo

Solo was a free AI website creator from Mozilla. You described your business, the AI built you a website, and Solo hosted it, custom domain and all.

Users were told on 1 October. Registrations are already closed. The shutdown FAQ is blunt about the end date: "There will be no way to recover your site, account, or data" after 30 November.

Mozilla has given people a way out. It's worth knowing exactly what that way out contains, though.

What the export gives you

In Solo, go to the menu at the top right, then Account Settings, then Download Website Data. You get a ZIP file containing:

  • an HTML export of your website
  • a CSV file with links to your images
  • your contact form and newsletter submissions

Note what's missing. The FAQ says "Image source files are not included in the ZIP." The CSV only points at them, so you need to download each image from those links before 30 November. Once the servers go, those links go with them.

If you bought your domain through Solo, that moves to Name.com. You set up an account there, fill in the contact details, and email your account code to Solo's support address. Do this first, and do it this week. The domain is the bit your customers, Google and your email all depend on, so it's the bit you least want to lose.

Turning the export back into a working site

An HTML export is a snapshot. It's the pages as they looked, not the thing that made them. There's no editor, no AI and nothing on a server answering requests. That's fine for a simple brochure site, as HTML will sit happily on almost any web host. A few things need checking before you switch it on somewhere new, though.

Forms. A contact form on a static page has to send its data somewhere. If Solo's servers were doing that job, the form will look fine and quietly go nowhere. Test it properly once it's moved, with a real message to a real inbox.

Images. Check the exported HTML points at your downloaded copies, not the old Solo addresses. A site that looks perfect today and loses every picture on 1 December is a nasty surprise.

Email. Moving a domain means touching DNS, and DNS is where your email lives too. Before you change anything, save a copy of every record, especially MX, SPF and DKIM. I've written up how to move a website without breaking your email, and it applies here exactly.

Your form submissions. They're in the ZIP as data. Keep that file somewhere safe. Those are your leads.

The FAQ suggests Wix, Squarespace and WordPress as places to go, along with AI builders such as Bolt and Lovable. Any of those can work. Just bear in mind that picking another hosted builder puts you back in the same position you're in now, a few years down the line.

The bigger question: what would you get out?

Solo was a website builder, and a simple five page site can usually be rebuilt if it has to be. It's a lot harder when the thing on the platform is your business.

You might be running real software on an AI app builder or hosted platform: a booking system, a customer portal, an internal tool, a quoting app. These tools are quick and genuinely useful. But it's worth asking the same question Solo users are facing now, while you've got time to think about it rather than two weeks.

Here's what I'd check for anything your business depends on:

  • Can you get the source code? Not an HTML snapshot. The actual code, ideally kept in a Git repository you control, so you have the full history and not just the latest version.
  • Can you get the data? All of it, in a format another system can read. Customers, orders, bookings, files, not just the bits shown on a report screen.
  • Do you know what it depends on? Database, logins, file storage, email sending, payments. If the platform provides those, each one needs a replacement before the code will run anywhere else.
  • Who owns the domain? It should be in your name, at a registrar you have the login for.
  • Have you ever tried it? An export you've never opened is a hope, not a plan. Run it once, now, and see what comes out.

None of this means you shouldn't use these tools. We use AI when we build software ourselves. It just means knowing where the exit is before you need it, the same way you'd want a tested backup before your server dies rather than after.

If the answer worries you

If you can get the code out but aren't sure what you're looking at, that's exactly what our code audit is for. It's £250 + VAT for one system. We go through the code, the hosting, the backups and the data, and you get a written report in plain English with a fixed price for anything that needs fixing.

We also take on apps built with Lovable, Bolt and Cursor, and once the code is somewhere you control, we can host it and keep it patched. Our Look after it service starts from £355 a month + VAT, and you can read what it covers on the support and maintenance page. If you built on Lovable specifically, my earlier post So You Built It on Lovable. Now What? has a quick test you can run yourself. There's also my guide on whether an AI-built app is safe to launch.

If you're on Solo, get your domain moving and your images downloaded today. Those two can't wait.

And if you'd like a hand working out what you'd get out of your own platform, get in touch. Happy to have a look.

Cheers, Rob

Tell us what you've got

It goes straight to Rob and Jase. You'll hear back from one of us, usually the same day, and we'll tell you honestly whether we're the right people.

Just want it checked? Code audit, £250 + VAT