For Relay.app teams
Relay.app is shutting down. The approval-first idea should not die with it.
Relay was the rare automation product that treated human approval as a first-class step, not an afterthought. That idea — a human sees it before it happens — is the entire core of Atrobox.
The dates, from Relay’s own notice
- Shutdown announced July 16, 2026 — no successor named.
- Free workspaces were deleted on August 15, 2026.
- Paid access ends September 14, 2026, after which workspaces, accounts, and stored app credentials are deleted.
If you are on a paid plan and have not exported your workflows and run data yet, do that first — relay.app has the export instructions. This page will still be here afterward.
An honest note before any pitch
Atrobox is not a drop-in Relay replacement. Relay was trigger-based workflow automation with a large library of app connectors; Atrobox is an AI organization — named AI agents that plan and execute goal-shaped work under human governance. If what you used Relay for was app-to-app plumbing (new row in a spreadsheet, post to a channel), a workflow tool like Zapier, Make, or n8n will fit better, and you should use one of those.
But if the reason you picked Relay over those tools was the human-in-the-loop part — that nothing important happened without the right person approving it — then what follows is for you.
What carries over
In Relay
A human-in-the-loop step pauses the workflow until someone approves, rejects, or edits.
In Atrobox
Nothing leaves the org without a human approving the exact outgoing text. Approving sends that literal message — not a paraphrase of it.
In Relay
Role-based routing: whoever holds a Role is the one asked to approve.
In Atrobox
Approvals are routed through a real reporting chain. The right human is resolved from the org chart as it exists that day — humans and agents on the same chart, with honest labels on which is which.
In Relay
A workflow run you can watch and intervene in.
In Atrobox
A mission: the plan and its estimated cost are shown before anything runs, every step produces a receipt (model, tokens, cost), and a kill switch is re-checked mid-run.
In Relay
Guardrails you configure once and trust on every run.
In Atrobox
A Constitution: org rules evaluated at execution time on every step — approving a plan does not pre-authorize the actions inside it.
What does not carry over
No connector library, no event triggers, no step-by-step workflow builder. You describe a goal in plain language and a team of named AI specialists plans it, prices it, and waits for your approval — a different shape of work, not the same product with new branding. Your Relay workflows will not import, and we will not pretend otherwise.
Where Atrobox stands
Early access, free while we harden it. Pricing will be published before launch. The changelog is a dated record of what actually shipped — judge the pace there, not from this page. The kernel is MIT-licensed and its code goes public at launch, so the approval and receipt mechanics described above will be readable, not just asserted.