Your systems on someone else's infrastructure. What if the vendor shuts down?

Treat every AI vendor as somewhere you'll leave one day. Keep your data, your instructions and your test cases in a form you can take with you, and know how the job gets done for a month if the tool's gone on a Friday.

By Matthew Steele4 min read28 October 2026

A server cabinet door open in a small comms room, a technician unplugging one labelled cable while reading from a printed checklist
Illustrative scene, not a customer's premises.

Three kinds of vendor

Vendor What they hold If they vanished How easy to swap
The model provider Nothing of yours, if the settings are right. Your prompts and files pass through. You switch models. A few days of adjustment, mostly to the wording of the instructions. Easy. Several providers, similar capabilities.
The platform or tool the agents run on Your agents' instructions, connections, logs, sometimes copies of your data. The agents stop. If the instructions and test cases only live in there, you're rebuilding from memory. Middling. Alternatives exist, the move takes weeks.
The builder or consultancy The knowledge of how it all fits together. Nothing stops straight away. Nobody can change anything either. Hard, unless the documentation is good.

The one people worry about most, the model provider, is the one that matters least. The one people forget – the builder with all the knowledge – is often the biggest exposure. That applies to us as much as anyone.

What to keep in your own hands

What you keep, what the vendor keeps, and Monday morningThree columns. You keep: the data in your systems, the instructions and rules in a document you own, the saved test cases, and a one-page map per agent. The vendor keeps: the platform and the model, which are replaceable. Monday morning, if the vendor is gone: the manual fallback for a few weeks, and a rebuild from the instructions and the test cases that takes weeks rather than months.You keepThe data, in your systems.Every agent's instructions andrules, in a document you own.The saved test cases.A one-page map per agent:what, connected to what, who,and how it is done by hand.The vendor keepsThe platform the agents run on.The model.Both are replaceable. Modelproviders are more alike thanthey look; the tool on top isthe harder move.Monday morningThe three people who used it goback to the manual process,which is written down.Someone stands the job upelsewhere from the instructionsand the test cases.Weeks, not a rebuild.The Friday testFor each tool you depend on: if it were gone on Friday evening, what happens on Monday? A bad answer is the one to fix this month.
What you keep, what the vendor keeps, and what you'd need on the Monday morning. Everything in the left column is yours to arrange.
  • The data: results written into your CRM, your accounts system, your file store, not held only in the vendor's tool. If a tool has to hold data to work, schedule the export and have it land somewhere you own.
  • The instructions: every agent's rules, prompts and thresholds in a document in your own system, kept current by the owner. One source of truth gives you this for free if you follow it.
  • The test cases: the 10 to 20 real examples with the expected answers. They're what makes a rebuild on another platform a week's work instead of a month's.
  • The map: one page per agent saying what it does, what it connects to, who owns it and how the job gets done by hand if it stops.

The Friday test

For each tool you depend on, ask yourself: if it were gone on Friday evening, what happens on Monday? A good answer sounds like "the three people who use it go back to the manual process for a few weeks, which is slower but works, while we stand it up somewhere else from the instructions and the test cases". A bad answer is "we don't know how the job gets done without it". The bad answer is the one to fix, and usually that means writing the manual process down before everyone's forgotten it.

The contract points worth asking for

Export of your data and configuration on request, in a usable format, at any time. A notice period for material changes to pricing or features, which in practice happen far more often than shutdowns. Clear terms on what happens to your data when you leave. Source-code escrow gets offered to smaller customers now and then, and in our experience it's rarely worth the money. The documents and test cases above do more.

What actually happens

Tool vendors do shut down suddenly now and then, but in our experience the common event is quieter – a price rise, a feature withdrawn, a product sold to a company that changes the terms. If you can leave in weeks, you negotiate those from a strong position. If you can't, you pay.