What to do when the platform running your website changes hands

Move the asset to parts you own. When the vendor hosting your website changes ownership, the safe response is a stack you control: source code in a repository you hold, hosting you can swap in an afternoon, and a domain whose DNS settings sit in your account. I ran that move for dugan-ai.com in nine days and went live on August 21, 2026.

On August 11, Manus told its users it would return to operating as an independent company after unwinding its acquisition by Meta. I had built the original dugan-ai.com on Manus in May. I read the notice, checked which parts applied to my account, and decided the site belonged somewhere I controlled.

Phase 0, project setup, started on August 13. Go-live and the branch split to dev both landed on August 21. Nine calendar days end to end, seven of them working days. The new stack is Lovable for construction, GitHub for version control and ownership of the code, and Vercel for hosting. The domain and its DNS stay at GoDaddy, in my account, under my login.

I spent more than 20 years selling and delivering enterprise technology at Microsoft, Google, and Salesforce. Most of that work was risk management wearing a different job title. On a Salesforce engagement at Honeywell's aerospace division, the customer requirement was replacing an aircraft part inside 12 hours or paying a contract penalty. The only question in that room was what happens when the system is unavailable and the clock is running. That is the same question a business owner should ask about every platform their revenue touches.

• Who it is for: Pittsburgh-area owner-operators whose website, quoting, or customer records live on someone else's platform.
• Time required: an afternoon to answer the four questions below, days to weeks to actually move.
• Tools in the new stack: Lovable, GitHub, Vercel, GoDaddy for domain and DNS.
• What changes: the code, the content, and the domain end up in accounts you can log into.

Platform risk is business risk

A platform you do not own is a dependency, and a dependency is a risk that sits on your books whether you have written it down or not. Ownership changes and regulatory action get decided by people you will never meet. Your exposure is the gap between the day you learn about it and the day you can operate without them.

According to Manus's August 11, 2026 note to users, the company is returning to independent operations following Meta's December 29, 2025 acquisition, and data generated by certain users on or after that date gets deleted to meet regulatory requirements in specific jurisdictions. The note gives affected users a backup window closing at 7:59 a.m. on August 23, 2026 Singapore time, with restore available from 8:00 a.m. on August 25. In Eastern time that is a backup deadline of Saturday evening, August 22, and restore roughly two days later.

The notice does not say Manus is shutting down. It does not say hosted sites go offline. It applies to a defined group of users over a defined date range, and users outside that group can keep working with no action at all. I want to be precise about that, because the specifics matter less than the category. What the notice actually told me is that the terms under which my primary marketing asset operated could be rewritten on someone else's schedule. That is a signal. Signals are for acting on.

The controls are what made the speed safe

Nine days is a function of discipline, and the discipline came from the enterprise playbook. Here is what was in place before the first prompt went into the builder.

• Requirements frozen first. One governing document held every decision: page structure, positioning, pricing, and a single offer catalog that every price and offer name on the site had to match. The build never negotiated with itself.
• Seven hard gates. Seven checkpoints ran through the sprint, and each one had to pass before the next phase opened. One of them verified that the offer catalog rendered correctly before any page work started, because that single file touched every commercial page on the site.
• A rollback defined before the cutover. I lowered the DNS time-to-live to 600 seconds four days ahead of go-live. That one change is what made a same-day reversal possible: point the domain back at the old host and the internet catches up in about ten minutes.
• Screenshots before every destructive change. The existing DNS records were captured before anything got removed. Mail records stayed untouched: MX, TXT, SPF, DKIM, and DMARC were out of scope, because a website cutover that breaks email is a website cutover that broke the business.
• Two independent copies of the old site. A full backup of the site data went to my own storage, and the original Manus code sits in a separate Git repository under my account. Both exist regardless of what any platform decides next.
• The old environment stayed reachable until the new one proved out. Go-live landed with more than a day still on the vendor's clock. A fallback you have already surrendered is no fallback at all.
• Source control separated from production. Production deploys from the main branch, Lovable writes to a dev branch, and changes get reviewed before the public site sees them. That split went in on August 21, the same day as go-live.

That last control deserves an honest note. Through the entire build, every message I sent to the builder deployed straight to production. I took that trade deliberately, wrote it into the plan as an accepted risk with a closing date, and retired it on go-live day. Enterprise discipline shows up in the written record of which risks you chose, why you chose them, and when you closed them.

What this looks like for a business in the South Hills

Ask four questions about every platform your business runs on, and write the answers down.

• If this vendor changed owners tomorrow, what would I lose?
• Can I export the actual asset, meaning the code, the content, the photos, and the customer records, in a format another tool can read?
• Who controls the domain and its DNS settings, and can I log in right now?
• How many days would it take me to stand this up somewhere else?

A Mt. Lebanon agent whose listing pages live inside a brokerage platform has an answer to question one that they will not enjoy. When the affiliation ends, the pages, the URLs, and the search history built over years end with it. A Canonsburg contractor running quotes and customer history inside one field-service app is in the same position with a different logo on the login screen.

Most of the time the fix starts with the domain. Own the domain, own the DNS, and keep an exportable copy of the content, and you have converted a hostage situation into a vendor decision you can make on your own timeline.

Common questions

Platforms change hands. Terms change. The businesses that read those events as signals keep operating while everyone else is reading a support article at midnight. The goal is building systems that stay under your control when the environment shifts.

Written by Chris Dugan, a Pittsburgh-area AI advisor. I work in person with South Hills realtors and small business owner-operators on practical AI systems. You own what we build. No monthly retainer required.