Mozilla Is Shutting Down Solo. Your AI-Built Site Needs an Exit Plan Before Launch Mozilla is shutting down Solo, its AI website builder and hosting service, deleting every site, account and piece of data on November 30, 2026, with roughly 54,000 users affected. The shutdown FAQ and reporting by The Register show the export package contains only an HTML version of the site, a CSV of image links rather than the image files, and form submissions, while domains bought through Solo Domains must be transferred to a partner registrar via support email. A developer at PolyDraft used the closure to outline an under-an-hour portability drill — checking registrar and nameservers with whois and dig, mirroring the site with wget, fetching linked images, and capturing sitemap URLs for a redirect map — arguing that the exit plan, not the generation step, determines whether a shutdown is a weekend of work or a lost business. Mozilla is shutting down Solo, its AI website builder and hosting service. According to the Solo shutdown FAQ https://support.soloist.ai/doc/solo-shutdown-faq , every Solo site, account, and piece of data is deleted on November 30, 2026, with no recovery afterwards. The Register reported https://www.theregister.com/software/2026/11/13/mozilla-leaves-solo-website-owners-to-go-it-alone-as-hosting-shuts-down/5309632 that around 54,000 people had used it to build pages, many of them sole traders running a custom domain on top. Mozilla did give notice October 1 and an export. But read what the export actually contains: a ZIP with an HTML version of the site, a CSV of links to your images, and your form and newsletter submissions. The image files themselves are not in the ZIP; you download each one individually. Domains bought through Solo Domains have to be moved to a partner registrar through a support email. On X, one web designer summed it up in a single line: own your domain and keep your own backup. This is not a post about Mozilla. Products end, and sixty days of notice is better than most. It is a post about the thing almost nobody checks when they pick an AI website builder: what you can carry out the door on the worst day . The generation step is the part everyone demos. The exit is the part that decides whether a shutdown is a weekend of work or a lost business. When a builder closes, gets acquired, reprices, or just stops fitting, four assets matter. Everything else can be rebuilt. A fifth item is quieter but expensive: your URL map . If the new site does not answer at the same paths, or redirect them, you throw away whatever search visibility the old one earned. You do not need to wait for a shutdown email to find out whether you can leave. Here is a drill you can run in under an hour against any site, including one built with an AI website builder https://polydraft.ai/ last weekend. whois yourdomain.com | grep -iE "registrar:|registrant organization|email " dig +short NS yourdomain.com You want the registrar account to be one you log into, and the nameservers to be somewhere you can change. If the registrar line names your site builder, find out today how a transfer works and how long the unlock takes. Don't rely only on the vendor's export button. Take your own copy of what visitors actually see: wget --mirror --convert-links --adjust-extension \ --page-requisites --no-parent \ -e robots=off https://yourdomain.com/ Open the mirror offline. If pages render empty because content loads client-side, that tells you something important: your "site" is not portable HTML, it is an app that needs the vendor's runtime. If an export gives you a CSV of image URLs as Solo's does , fetch them before the links die: mkdir -p media assumes the CSV has a column of image URLs; adjust the column number cut -d, -f2 images.csv | tail -n +2 | tr -d '"' | \ xargs -n 1 -P 4 wget -q -P media/ ls media | wc -l compare against the row count of the CSV Compare counts. A missing logo or hero image is the kind of gap you only notice after the old host is gone. curl -s https://yourdomain.com/sitemap.xml | \ grep -oE "