Switching tools
Your AI workflow tool is shutting down. Rebuild on one nobody can take away.
OpenAI Agent Builder shuts down on November 30, 2026. Flowise reached end of life in August, and Relay.app closed in September. Bring us what you built and we’ll rebuild it with you, free, on an open-source engine.
The free rebuild is part of our pilot, open to the first 10 businesses.
- Apr 9, 2026Hosted Langflow on DataStaxRemoved from Astra
- Aug 31, 2026FlowiseEnd of life
- Sep 14, 2026Relay.appPaid accounts closed
- Oct 31, 2026OpenAI EvalsBecome read-only
- Nov 30, 2026OpenAI Agent BuilderShuts down
- Apr 9, 2026Hosted Langflow on DataStaxRemoved from Astra
- Aug 31, 2026FlowiseEnd of life
- Sep 14, 2026Relay.appPaid accounts closed
- Oct 31, 2026OpenAI EvalsBecome read-only
- Nov 30, 2026OpenAI Agent BuilderShuts down
OpenAI Agent Builder
Shuts down November 30, 2026.
OpenAI points its users to the Agents SDK, which is code, or to ChatGPT Workspace Agents, which need a Business, Enterprise or Edu workspace. If you’d rather keep a visual workflow your team can read and approve, here’s how to move.
Before November 30
- 1Export every workflowOpen it in Agent Builder, choose Code, pick Agents SDK, then Python or TypeScript, and copy the whole export.
- 2Note what the export leaves outThe apps it connects to and their logins, and anything the workflow did that the code doesn’t show. OpenAI says the export doesn’t convert the workflow graph.
- 3Save your evals by October 31That is when OpenAI’s evals become read-only. They shut down with Agent Builder on November 30.
Then, on SynapseOrch
- We rebuild it with you, free
- Send us the export. We rebuild it as a workflow you can read and approve: agents stay agents, if/else becomes a check, user approval becomes your sign-off, file search becomes a search of your documents, and guardrails become a check step.
- Any model, not one vendor’s
- Keep using OpenAI with your own key, switch to any of 23+ providers, or use our models with no key at all. Each step can use a different one.
- Apps that called your workflow
- Keep your OpenAI client: change its base URL to https://api.synapseorch.com/api/v1/openai, use a SynapseOrch key, and name the workflow as the model. It speaks Chat Completions, streaming included, not the Responses API, and the workflow’s own tools do the work.
- A chat window on your website
- ChatKit stays, but the workflow behind it goes. Our chat widget puts the rebuilt agent on your site with one script tag.
Also closed this year
Flowise, Relay.app and hosted Langflow
- Flowise · end of life August 31, 2026
- Its repository is archived and the team suggests forking it. If you’d rather not keep a fork alive, bring a flow you run and we’ll rebuild it with you: a chatflow usually becomes an agent with a knowledge base and a chat widget, an agentflow a workflow.
- Relay.app · closed September 14, 2026
- Relay was built around a person in the loop, and so is this: a sign-off anywhere in a workflow, answered in the app or in Telegram. Check your apps first: we connect Google Workspace and 50+ apps, plus any API or MCP server.
- Hosted Langflow on DataStax · removed April 9, 2026
- DataStax points to running Langflow yourself. If you want a hosted workspace for your team instead, with sign-offs and a bill that stops at its limit, that is what SynapseOrch Cloud is.
Why it won’t happen again
An engine nobody can take away.
SynapseOrch is open source under AGPL-3.0. The engine that runs your workflows on our cloud is the same one you can install on your own servers, so it can never be taken away, by anyone, us included.
Cloud or self-host?Install it yourself
Dates from each company’s own pages, checked on October 11, 2026: OpenAI deprecations · OpenAI: Migrate from Agent Builder · Flowise sunset · DataStax Langflow release notes · Inbox Zero on Relay.app.
Bring us what you built.
Send the export, a screenshot or just a description of what it did. We’ll rebuild it with you, free, and you approve every step.
Free plan, no card needed.