Skip to content
newc0

Answer

What happens to your business if your AI platform shuts down?

It depends where your business actually lives. If the code, data, domain and customer relationships sit in the platform’s accounts, a shutdown is an outage you cannot fix. If you hold your own domain, exports and payment relationships, it is a bad month rather than the end.

Last updated

This page gives advice that does not particularly favor newc0, because the advice is the same regardless of which platform you use, including this one.

What actually disappears when a platform shuts down?

Hosting first, then anything on the vendor’s subdomain, then any account they held on your behalf — advertising accounts, payment balances, connected integrations. Your data usually survives if you exported it. Your customers’ ability to reach you survives only if the domain was yours.

The subdomain point is worth dwelling on. Many platforms give each business a generated address on their own domain, and it works well enough that founders never move off it. Every link, every email signature and every search result then points at an address the vendor controls.

Payment balances are the other one people miss. If customer payments flow through the platform and sit in a balance before withdrawal, that balance is a claim on a company that just failed, not money in your bank.

How much notice do you normally get?

Less than you would like, and the terms usually allow termination with little or none. Polsia’s terms, for example, describe a 30-day window after termination in which infrastructure remains accessible and data can be exported, after which resources may be permanently deleted.

A 30-day window is reasonable and fairly typical. The problem is that it assumes you notice, act, and know how to export within it. Founders in the middle of a crisis, or on holiday, or simply not reading email from a vendor, routinely do not.

Note also that a shutdown is not the only way this happens. Account suspension for a terms violation produces the same practical outcome, faster and with less warning.

What should you do before it matters?

Four things: own your domain, keep your customer list somewhere you control, take periodic exports of code and data, and know who your payment processor thinks the merchant is. Half an hour of preparation converts an existential problem into an annoying one.

The checklist in full:

  • Domain. Registered by you, at a registrar you have the login for.
  • Customer list. A copy outside the platform, refreshed on a schedule.
  • Code and data. A real export you have tested, not a button you assume works.
  • Payments. Know whether you or the platform is the merchant of record, and whether a balance is held before you can withdraw.
  • Ad accounts. Know whose account campaigns run in, because history and learning do not transfer.

None of this is specific to AI platforms. It is the same advice that applied to website builders and hosted storefronts for twenty years. The difference is that an AI platform tends to hold more of the business at once.

What if the platform does not shut down, but suspends you?

The practical outcome is the same and it arrives faster. Terms in this category generally allow suspension for suspected policy violation, with limited notice. Since agents act on your behalf at volume, a policy breach can happen without you doing anything deliberately.

This is the scenario founders prepare for least and encounter most. An outbound campaign trips a third-party platform’s rules, an advertising account is flagged, a generated page includes something a policy prohibits — and the account is restricted while somebody reviews it. Nobody has done anything malicious and the business is still offline.

The mitigations are the same as for a shutdown, with one addition: keep your own copies of anything generated on your behalf that you are responsible for. If a policy question arises about a page or a campaign, being able to see what was actually published is the difference between resolving it and guessing.

It is also an argument for approval gates on anything published in your name. Content that a person reviewed before it went out is content you can defend.

The honest position on newc0

newc0 builds an application the founder owns. What is not yet published is the handover mechanic — what happens to it, specifically, if the relationship ends. That gap is recorded on the claim sheet rather than papered over, and the advice above applies to newc0 exactly as it applies to everyone else: keep your domain, keep your list, take your exports.

Written by newc0. Published .

Every claim on this page is recorded on the claim sheet, with its scope. If the two ever disagree, the claim sheet is right and this page is a bug.