Mozilla to shut down Solo on November 30, deleting user sites and data

Mozilla will shut down Solo on November 30, 2026, deleting hosted websites and user data. Users must export their materials and separately transfer any domains bought through Solo Domains before then.

· 5 min read · 5 comments

Mozilla will shut down Solo, its service for creating and hosting websites using large language models, on November 30, 2026. According to Habr, websites and data stored in the service will be deleted that day. Solo users have just over two weeks left to retrieve their materials and arrange to host their sites elsewhere.

Why Solo’s closure affects published websites, too

Solo launched in December 2023 as part of Mozilla Innovation. It was designed for sole proprietors who needed a website to promote their services. Its first major release came out in 2024. According to figures cited in the report, around 54,000 people used Solo.

The shutdown notice appeared on the Soloist.ai homepage. Mozilla says it first notified users on October 1 and gave them 60 days to make the transition. That deadline is now close: after November 30, users cannot count on being able to access their Solo-hosted websites or data.

It is not just the page-building tool that is shutting down. Solo also hosted finished websites, so users face more than a choice of another website builder. They need to retrieve the materials available to them, find a new home for their site and, if they bought a domain through Solo Domains, transfer it separately.

Mozilla attributes the decision to the project’s experimental nature: the company says that work on products like these sometimes ends with their closure. It says it offers support with exporting data and transferring domains, and suggests alternative services for automated website creation.

What you can export from Solo

Solo’s help documentation describes a ZIP export. It includes an HTML version of the website, contact form data and subscriber lists. Users can also get a CSV file containing links to images. The images themselves must be downloaded separately: a list of file URLs is no substitute for the files.

That distinction matters if the website is more than a collection of pages. The archive also contains information from contact form submissions and subscriber lists. When checking an export, it therefore makes sense to look beyond the HTML pages at the other data available. The source does not, however, promise that the exported files can be deployed with another provider without additional work.

Domains purchased through Solo Domains follow a different process. They must be transferred to the registrar Name.com: users need to create an account there and provide a special code. Mozilla will then carry out the transfer. Exporting a website and transferring one of these domains are separate parts of the move; downloading the archive does not take care of the domain.

Practical steps before November 30

Website owners should check what their export contains and determine which data they will need on the new platform. Contact form data and subscriber lists are especially important for anyone handling customer enquiries. Developers, or whoever will be responsible for hosting the site, need to account for the export format: it is an HTML version of the website, not a ready-to-use migration that the service has promised.

If the domain was registered through Solo Domains, it will need to be transferred to Name.com. Other users do not need to take that step, but they will still have to find somewhere to host their site: Solo hosting is ending. The deadline for all of this is November 30, when Mozilla will shut down the service and delete websites and data.

You can choose a replacement based on your needs, but it is better to assess the scope of the move by looking at the files you have exported, rather than at how the site currently looks in Solo. That will make it clearer which parts of the site you have already saved and what you will need to work with once hosting ends.

My view: move without rebuilding more than necessary

I run a family textile business and am gradually moving sales online. That experience makes it clear why a platform closure is more than just technical news. A website can help bring in enquiries, but it does not replace inventory management. When a service has to change, I would first separate the essential move from the temptation to redo everything else at the same time. Otherwise, it is easy to spend time choosing a new tool while the deadline for data deletion approaches.

I am not in favour of replacing a working CMS just because someone has called it outdated. But when a service shuts down, a move is unavoidable. In my view, a fixed quote would help separate the website budget from the inventory budget in advance, then make it easier to decide which improvements are genuinely needed. Clear navigation, for example, is more useful to a customer than changing tools for the sake of it: people should be able to find what they need easily, wherever the pages are hosted.

Sources

Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.

  1. Mozilla закроет сервис Solo для создания и хостинга веб‑сайтов habr.com

About the author

Bahruz Khalilov

Textile store chain owner

I run a family business and am gradually moving sales online. From experience, I’ve learned that a good website won’t replace inventory management, but it can make it much more convenient.

All posts by the author

Leave a comment

Not published. We’ll send a link to confirm your comment.

No links or ads. Your first comment is published after review. By sending a comment you agree to the privacy notice.

  1. I’ve had to move a small site off a hosted builder before, and the tricky part wasn’t the page layout—it was finding the original images and checking which domain settings needed a separate transfer. For Solo, I’d export everything first, then get the domain transfer started early rather than treating it as part of the site export.

    1. @zdenek_dev, one extra wrinkle: export is not the same as a tested migration. I’d open the downloaded files locally and check forms, analytics, and redirects on the new host—otherwise you can preserve every image and still quietly break the bits visitors actually use.

      1. @lars_lammers, which of those checks would you prioritize if staff have only a few days before November 30: forms and redirects, or confirming the domain transfer first? We run a small learning center, so a broken inquiry form is a practical problem, but losing control of the domain would be harder to recover from.

        1. For a learning center, I’d start the domain transfer today, since losing control of it is the harder problem to undo. In parallel, have someone submit a test inquiry on the replacement site and verify it reaches the right inbox; that’s a quick check, while redirects and analytics can follow if time is tight. Keep the old contact details visible somewhere until the form is confirmed, and don’t assume the domain moves as part of the Solo export.

        2. If the domain is registered through Solo Domains, I’d start that transfer now, then use the remaining time to test the inquiry form on the new host. Can you keep the current site reachable while the transfer is pending, or does the learning center need a temporary contact route before November 30?