Let’s talk about the three AI platforms that died in five weeks — and the one file that walked out with anything useful in it.
Between the thirteenth of August and the fourteenth of September, three tools that real businesses had built real operations on got switched off. Flowise archived its repository. Relay.app started permanently deleting workspaces. OpenAI removed the Assistants API after a full year of notice — and it’s already put a shutdown date on Agent Builder, the drag-and-drop thing it shipped barely a year ago as the future of building agents. November thirtieth.
Here’s the part that should worry you. None of these companies behaved badly.
Relay gave prorated refunds inside five business days. Sixty days of free access for paying customers, extra steps, extra AI credits, priority support for anyone whose workflows were business-critical. Genuinely decent wind-down. And the export still doesn’t work.
Relay’s own documentation says it out loud. The workspace export gives you a JSON file that represents your workflow’s exact structure — and then explains that because every workflow builder uses different JSON, that file “is not perfectly transferrable to other tools without AI interpretation.” You can hand it to another platform as a prompt, “but it won’t work through their native importers.” And then the sentence I haven’t been able to get out of my head: “This is why we have also included a build prompt option, which we encourage you to use.”
Sit with that for a second. A vendor at end of life, with every commercial reason to make the exit clean, concluded that the portable form of your automation is a paragraph of English. The machine-readable file doesn’t machine-read anywhere else.
Flowise is the cleanest case, because there’s no money in it. Fifty-five thousand stars, twenty-five thousand forks, the “build agents visually” project everyone pointed at. Archived on the thirteenth of August. Last commit, same day. The maintainers’ reason, in their own words: developers are increasingly using coding agents for complex work, and the rigid low-code canvas hits a wall once things get complicated. Fork it and maintain it yourself, they said. So now you’re carrying dependency updates and model API churn forever, to preserve flows whose logic you could have written on four pages.
And OpenAI’s version is the state problem. A year’s notice, a documented migration path, and the guide still says this: we will not provide an automated tool for migrating Threads to Conversations. Convert them by hand. Which is fine, unless you quietly promoted Threads from a convenience into a system of record. Persistence came in as a product feature. It never inherited the disciplines storage gets — an owner, a retention rule, someone reconciling it against the system that actually owns the fact. A shutdown date is just the invoice for that arriving on a schedule you don’t control.
Now picture the thing that actually hurts.
There’s an ops team of two in a company of ninety. They built one workflow — invoice exceptions, the ugly ones. Straight boxes, easy to rebuild: read the PDF, check the amount, route it. Anyone can look at a screenshot and recreate five boxes in a row.
What’s expensive is everything hanging off the sides. The retry that fires three times with backoff, because one upstream API returns a 502 about once a week. The extra branch somebody added in March, after a customer got double-billed. The filter that silently drops records where a date arrives as an empty string instead of null, because a vendor changed their serializer and never mentioned it.
None of that is in the diagram. Some of it isn’t even visible in the JSON. Most of it lives in the run history, and only if you know which runs to open. Those are the paths that made the process survive contact with reality, and they were never written down as a process. They were written down as a workflow, inside somebody else’s canvas.
So here’s the trade, and it was never a fair one. You leased the logic. You leased the state. You leased the credentials — when Relay’s workspaces close, the stored OAuth tokens for every connected app go with them. And you did it in exchange for not having to draw the thing on paper.
That’s the real bill. Not the subscription. The fact that the description of how your business works ended up living in a product you don’t own, in a format whose only escape hatch is prose you have to write yourself, on a date they picked.
And if you think the fix is that some vendor will finally ship a universal portable format — watch what happened the same week. Writer launched Enterprise Brain, a governed context layer it wants to sit on top of your company’s brand, decisions, and institutional knowledge, with a team-level memory layer under it. The pitch is perfectly reasonable, and the pitch is exactly the pattern. The industry that just proved your process can’t leave a platform is now selling to make your process live inside theirs.
Both ends push the same way. They want the definition in their box.
So take the operator lesson, because it’s short and it’s cheap and it’s the only part you control.
Write the four pages. The trigger. Every branch and what decides it. The exception paths and what happens on each one. The escalation rule and its threshold. Which systems each step touches, and what it’s allowed to do there. Who owns each credential, inventoried somewhere that isn’t the platform.
Then run the only test that matters. Pick your most important automated workflow and ask whether someone could rebuild it tomorrow, in a different tool, working only from what you’ve written down — without ever opening the platform it runs in. If the answer is no, the shutdown notice just hasn’t arrived yet.
And do the export like a migration with a runbook, not a button you press on the last afternoon. Relay’s export takes up to twenty-four hours to build and the download link dies in forty-eight. The real deadline is three days before the one on the page, and a link that expires in someone’s inbox while they’re on leave costs you an entire cycle.
There’s a principle under all of this, and it’s older than software. Your process is your judgment, written down and repeated. It’s the accumulated “we tried that, it broke, so we do it this way now.” If that lives in a canvas you can’t open, you didn’t automate your business. You rented an implementation of it, and the terms were in a footer you didn’t read.
You own what you can describe. Everything else is on loan.
So write it down this week. Not because a vendor is about to die — because one already did, and the only thing that made it out intact was the sentence you hadn’t written yet. You’ve got this.