Mozilla is shutting down Solo, its AI website creator

Mozilla has made the decision to shut down Solo, the AI website-creation tool. This is the only action in this event explicitly described as a "decision"; everything else is wrap-up arrangements built around that decision.

The official timeline is very specific: all Solo websites and data will be deleted on November 30, 2026; after November 30, 2026, websites, accounts, or data cannot be recovered. This means users are not facing "the service may slow down or features may be reduced" but a definite deletion date.

What needs to be distinguished is this: the shutdown decision and the deletion date are confirmed facts; however, the reason for the shutdown, the number of affected users or websites, whether Solo team members are affected, and whether it is related to an overall Mozilla AI strategy adjustment are all not explained by the source. Filling these blanks in as "strategic contraction" or "product failure" is inference beyond the material.

The official export path is: log in to Solo, click the menu in the upper right corner, select Account Settings, and click "Download Website Data" in the pop-up. Users will receive a ZIP file containing the website HTML export, a CSV of image asset links, and contact form and newsletter submission content.

The key limitation is that the ZIP file does not contain image source files. Users must download images one by one via the links in the CSV before November 30, 2026. This is the most easily underestimated step in the entire wrap-up process—the HTML export looks "complete," but images require additional action and are likewise bound by the deletion date.

From the perspective of operational order, a reasonable approach is to first complete the ZIP download, then handle the image links in the CSV, and finally consider migrating to an alternative host. Because once November 30, 2026 passes, websites, accounts, or data cannot be recovered, and any assumption of "I'll do it later" does not hold.

For active Solo Pro or Grow subscriptions, the official policy is to prorate the unused portion as of October 1, 2026, refund it to the original payment method, and stop renewing the subscription.

There are two points here that are easy to misread. First, the refund baseline date is October 1, 2026, not the deletion date of November 30, 2026; second, the official statement explicitly says "you do not need to do anything to receive a refund," meaning refunds are triggered automatically and users do not need to submit an application.

But the refund scope has boundaries: it applies only to active Solo Pro or Grow subscriptions. The source does not explain how free users, expired subscriptions, or other paid forms are handled, so "prorated refunds" cannot be generalized to all users.

Domains purchased through Solo Domains (not IONOS) must be migrated to its domain partner Name.com. This qualifying condition is important: domains purchased through the IONOS channel are not within this migration path, and the source does not explain how those domains will be handled.

The official migration steps are: create a Name.com account (or log in if you already have one); verify the Name.com account email, because Name.com requires account verification before accepting a transfer; find the unique Account Code in the upper right corner of the Name.com dashboard; send that Account Code to support@soloist.ai, and the official team will notify you by email after completing the transfer; finally, add billing information at Name.com, otherwise Name.com will remind you as the domain renewal date approaches.

In this set of steps, the Account Code is the key credential connecting the two accounts, email verification is a prerequisite, and billing information determines whether the domain can be renewed smoothly. The source does not explain the final handling details of domains and subscriptions after November 30, 2026, so after migration is completed, the renewal responsibility effectively falls on the user's configuration on the Name.com side.

The officially recommended alternative hosts include Wix, Squarespace, and WordPress; AI website-building tools such as Bolt or Lovable may also be considered.

It should be noted that this item belongs to source claims in terms of evidence grading, not an independently verified conclusion. Which platforms the official team recommends and whether those platforms are suitable for a specific site, how high the migration cost is, and whether features are equivalent are two different questions. The source does not explain whether there are other migration options besides the platforms listed above.

For users, the choice of alternative host should be considered in parallel with export progress: first ensure that HTML and image assets are secured before November 30, 2026, and then decide where to migrate. Reversing the order may compress export time in order to "choose a platform."

Users can get further help through support@soloist.ai or the Reddit group. These two channels also include the same email used to submit the Account Code during domain migration, so this email serves both migration operations and general inquiries.

All specific arrangements in this article come from the "Solo Shutdown FAQ" on Solo's official support page. This is a first-party source, but it answers "how to do it," not "why." The source does not explain the specific reason Mozilla is shutting down Solo, nor the number of affected users or websites, whether team members are affected, or whether it is related to an overall Mozilla AI strategy adjustment.

Treating these unexplained items as known would make readers base their judgment of the event on speculation. A more prudent reading is: the shutdown and deletion date are certain, the wrap-up path is certain, and the reason and scale are blank.