comparison

Moxo vs Relay.app in 2026: Where Relay's Approval Workflows Can Go Next

Relay.app, founded in 2021, shut down in September 2026 and deleted every account, workflow and run history; Moxo, whose predecessor Moxtra was co-founded in 2012, is one destination for its human-in-the-loop users. Relay.app takes two rounds, Moxo one, and vendor risk is a draw. The page maps which Relay steps Moxo replaces, on which plan, and what the shutdown teaches about exports, from sources read 28 September 2026.

The Bottom Line: A Relay.app team moving to Moxo should check three things in order. First, that its approvals and forms fit Team's "100 flows/yr" at "$5,000/yr", the last list Moxo published (read 28 September 2026), roughly 22 times the $19 a month Relay charged for Professional on annual billing. Second, that the paths, loops and sequences it relied on are budgeted at Scale, a custom quote. Third, that one finished case can be exported and read outside Moxo before the first live client, because Relay's closure deleted every account, workflow and run history.

Overview

Relay.app is gone. Its homepage, read 28 September 2026, says "Relay.app shut down in September 2026. All accounts, workflows, and run history have been permanently deleted", and that "The July 2026 version of our homepage is preserved on the Internet Archive". Relay announced the closure on 16 July 2026; free accounts were deleted after 15 August and paid accounts after 14 September (Automation Atlas shutdown guide). This page is for teams that used it for human-in-the-loop work and are deciding where that work goes next, with Moxo as one destination among several.

It is a migration comparison, so the rounds score what each product did for the person in the middle of a workflow, not which one to buy today. Relay.app takes two rounds, Moxo takes one, and vendor risk is a draw. Relay's side rests on its homepage as captured on 14 July 2026 and its pricing page as captured on 29 June 2026, both on the Internet Archive. Moxo's side rests on its pricing page as last published (read 28 September 2026, before it redirected to Moxo's homepage), its Description of Services, Terms and Conditions and API reference, read 28 September 2026, and on synthetic AutomationAtlas builder tests on 14 and 15 September 2026.

Company Snapshot

Moxo Relay.app
Founded Predecessor Moxtra "co-founded in 2012" (PR Newswire, June 2021) 2021 (Automation Atlas Relay.app profile)
Legal entity Moxo, Inc., San Francisco (Terms and Conditions, 17 Sep 2026) Relay.app Inc. (homepage footer, 14 Jul 2026 capture)
Customers No count in the sources read (28 Sep 2026) "Used by thousands of businesses" (homepage, 14 Jul 2026 capture)
Funding / valuation Private company; third-party totals conflict (14 Sep 2026) No figure on the pages read (28 Sep 2026)
Recent signal Team cut from 250 to 100 flows a year at an unchanged $5,000 (archive captures, 26 Aug and 10 Sep 2026) Shut down in September 2026; accounts, workflows and run history "permanently deleted" (relay.app, 28 Sep 2026)

The Core Trade-Off: The Price of Staying Small Goes to Relay.app, by Knockout

Relay.app wins the entry round by knockout, and it is the loss a migrating team feels first. Its pricing page, captured on 29 June 2026, offered Free at $0 for 1 user and 200 steps a month, Professional at "$19 per month, billed annually" for 750 steps, and Team at "$59 per month, billed annually" with "10 users included", and it promised "All features included in every plan". Human-in-the-loop sat in that list on every plan: "AI output reviews", "Custom approval steps" and "Custom data input steps". A one-person approval workflow cost nothing, and a ten-person team paid $708 a year (AutomationAtlas arithmetic).

Moxo stopped publishing prices. The last list it published, read 28 September 2026, put Team at "$5,000/yr", annual only, with no free plan. That is about 7 times Relay's Team plan and 22 times its Professional plan, before a single flow is built (AutomationAtlas arithmetic). The unit changes too. Moxo sold "100 flows/yr", where Relay metered steps and did not charge "for triggers, data transformation steps, path and loop evaluations". A Relay user who ran a few hundred small approvals a month will not fit 100 flows a year, the allowance Moxo last published.

AI changes shape as well. Relay included 500 AI credits a month on Free and 2,000 on its paid plans, and let any plan bring its own API keys. Moxo gave Team "$100 of AI/yr" in dollars on that last list, with no published conversion to the credits its product logs, and "Bring your own model / agent" sat on Enterprise. An AI-heavy Relay workflow is expensive to move.

Approving Where the Team Already Works Goes to Relay.app

Relay.app takes the second round because its human steps met people where they already were. The homepage promised to "Pull in a teammate anywhere you need an approval, data entry, or AI output review", its pricing page listed a Slack integration under Human-in-the-Loop on every plan, and Automation Atlas's shutdown guide found its distinguishing capability was a run that pauses so a named person can approve, reject or edit an AI-drafted output, usually from Gmail or Slack (checked 28 July 2026).

Moxo sends the work to its own surface. Its Description of Services offers Slack and Microsoft Teams "flow-event notifications to channels and direct messages to participants", Team listed SMS notifications on the last published plan list, and the task itself is completed in Moxo's Assignee Portal. For a team that approved AI drafts in Slack twenty times a day, that is one more place to go. Moxo's AI steps do carry a "Human review" switch ("Pause for a user to review and edit the AI output before it's used downstream"), seen off by default in a synthetic test on 15 September 2026, and the Review Agent that automates the check started on Scale on that list.

Getting the Record Out Goes to Moxo, by Knockout

Moxo wins the exit round by knockout, because Relay's shutdown deleted every run history along with the accounts it belonged to. The lesson for your next vendor is to hold your own copy of each case, and Moxo's API is built to hand one over. GET /v1/flows/{id}/export "Downloads the flow's data and attachments as a ZIP archive", one case at a time, and GET /v1/templates/{id}/export downloads the template definition behind it (developers.moxo.com, read 28 September 2026). You can pull a case out the day it closes, not the week a vendor announces its end.

Relay's record was thin at the bottom even before the end. Its pricing page listed run history retention of "30 days" on Free and "Custom" on paid plans (29 June 2026 capture), and its export, per Automation Atlas's shutdown guide, capped run-history CSVs at 100,000 rows while Relay warned that its JSON "won't work through their native importers". Moxo documents more to take with you. Its Description of Services offers "a complete Flow record (summary, per-step detail, audit trail, and attachments) as an archive", exports audit and activity records "to CSV, JSON, or PDF with chain-of-custody headers and a SHA-256 fingerprint", and lets an organisation auto-delete file contents while "retaining metadata and audit records". The flow audit log returns "every action taken, by whom, and when".

The record also outlives the people in it. When you remove a user with DELETE /v1/users/{id}, the API says their "name stays attached to past assignments so the audit trail remains intact". Staff leave and client contacts change over a long case, and the approvals they gave stay attributed to them. Outside participants are held the same way, as users of kind external: a record, never a login.

Two limits keep the knockout honest. An export you never run protects no one, and Moxo is a vendor too, so the vendor-risk draw below applies to it in full: script the flow export into your close-out and keep the archives where Moxo cannot delete them. And on the last published plan list (28 September 2026) the audit log and REST APIs sat on Scale, a custom quote, not on Team, while a template leaves as "a .moxo.json file", a format only Moxo runs. What you carry out is evidence rather than a process another engine can execute.

Rebuilding a Relay Workflow on Moxo

Relay's export was built for this moment. Each workflow folder held a rebuild prompt as a markdown file, and Relay itself treated the markdown, not the JSON, as the migration vehicle (Automation Atlas shutdown guide, 28 July 2026). Moxo's front door takes that shape: its Description of Services documents "Conversion of an existing written process" from pasted text or uploaded documents into a draft template using AI. Expect a draft, not a copy. In a synthetic test on 14 September 2026, Moxo's own Build with AI produced 4 steps and 3 roles from one prompt, then its publish validator refused the design with 2 blocking issues.

The table shows where each Relay building block lands, and on which Moxo plan.

Relay.app building block (every plan, June 2026) Moxo equivalent Moxo plan (last published list, 28 Sep 2026)
Custom approval steps Approvals, Decisions Team
Custom data input steps Forms, File requests Team
AI output reviews AI step "Human review" switch; Review Agent Review Agent on Scale
Paths, merging paths Branching Scale
Looping, sequential and parallel Loops (For-each) Scale
Sequences (sub-workflows) Subflows Scale
Wait-for-webhook step WAIT step resumed by callback token Not named on the pricing page
Time-based trigger Scheduled flows Scale
Webhook trigger Webhooks, Triggers Scale
Tables Data tables Enterprise
Bring your own API keys Bring your own model / agent Enterprise

Read down the right-hand column. Moxo replaces Relay's approval and form steps on Team, but almost everything that made a Relay workflow a workflow, from paths and loops to sequences and triggers, started on Scale, a custom quote, on the last published list.

Vendor Risk Is a Draw

Call vendor risk a draw, because a shutdown teaches the same lesson about every vendor. Relay gave its paying customers about 60 days, from 16 July to 14 September 2026, with full access at no charge, and free users about a month (Automation Atlas shutdown guide). No workflow survived the end date.

Moxo is a private company whose funding totals conflict across third-party databases (14 September 2026), and it moves its terms quickly: Internet Archive captures show Team carrying 250 flows a year on 26 August 2026 and 100 on 10 September, at the same $5,000, and by 13 October 2026 moxo.com/pricing redirected to its homepage. Its Terms and Conditions give some protection. A price change applies only from the next subscription term, "at least sixty (60) days after the notice", and Moxo will use "commercially reasonable efforts" to give 30 days' notice of a change that "materially affects the functionality" of the service. The Terms state no window for exporting your data after termination, and the Description of Services says only that organisation deletion comes "with a compliance audit trail and a grace period", without a length. Put the export window in the order form.

Pricing (as of September 2026)

Moxo (last published list, moxo.com/pricing)

Moxo stopped publishing prices: by 13 October 2026 moxo.com/pricing redirected to its homepage. The last published list, read 28 September 2026, put Team at "$5,000/yr" for "100 flows/yr · $100 of AI/yr · Unlimited seats", annual only; Scale and Enterprise were custom quotes. Every plan's button then read "Book a demo", and the header still links "Request free trial", with no length stated. There was no free plan and no published overage rate; past the allowance the API answers 402 QUOTA_EXCEEDED.

Relay.app (final published prices)

From the 29 June 2026 capture of relay.app/pricing on the Internet Archive (re-checked 13 October 2026): Free at $0 with 1 user, 200 steps and 500 AI credits a month; Professional at $19 a month billed annually, 1 user, 750 steps and 2,000 AI credits; Team at $59 a month billed annually, 10 users, 1,500 steps and 2,000 AI credits; Enterprise custom. The billing toggle read "Annual (Save 50%)". None of it can be bought now.

Cost Comparison (Estimated Annual)

Tier Moxo (last published list, 28 Sep 2026) Relay.app (June 2026, now closed)
Free plan with approval steps None Free, 1 user, 200 steps a month
Entry paid Team, $5,000/yr, annual only Professional, $228/yr billed annually
A team of ten Team, $5,000/yr, unlimited seats Team, $708/yr billed annually
Metered unit Flows a year, plus dollars of AI Steps a month, plus AI credits
Branching, loops, sub-workflows Scale (custom quote) Every plan
Run history kept Audit records kept when file contents auto-delete; audit log on Scale "30 days" on Free, "Custom" on paid

Moxo is the wrong choice for a Relay team whose workflows were one person's automations with an approval in the middle: on its last published list it cost about 22 times Relay's Professional plan and metered a unit those workflows never needed. It fits when the approval was always the front of a longer case with people outside the company.

Migration Framework

Start from what your Relay workflow waited for.

If your Relay workflow… Where it lands
Paused for one teammate to approve an AI draft in Slack Not Moxo's strength; compare the options in the shutdown guide
Ran a few hundred small approvals a month on Free or Professional Not Moxo; the last published 100 flows a year at $5,000 will not fit
Collected a form from a client, then routed an approval Moxo Team (Forms, Approvals)
Needed sign-off by any one, all or a majority of a group Moxo (group completion modes)
Involved clients or suppliers who are not on your team Moxo (unlimited seats; external user records)
Branched on data, looped over line items or called sequences Moxo Scale (custom quote)
Waited for another system to call back Moxo WAIT step, resumed by token
Kept reference data in Tables Moxo Enterprise (Data tables)
Must leave an exportable record of every decision Moxo flow export and audit log (Scale on the last published list)

Editor's Note: Relay.app's pricing page, captured on 29 June 2026, listed run-history retention of "30 days" on Free, and free accounts were then given the same 30 days, from the closure announcement on 16 July to deletion after 15 August. If that retention was a rolling window, a free user who waited for the deadline could export nothing older than the announcement. Moxo's API reference describes GET /v1/flows/{id}/export, a ZIP of a flow's data and attachments, as "useful for archival, compliance exports, and migrations", but its Terms name no export window after termination, so we would run it as each case closes. — Rafal Fila, ShadowGen

Written & reviewed by Rafal Fila · Last updated:

Tools Mentioned

Related Guides

Related Rankings

Best Human-in-the-Loop Automation Platforms 2026

Eight platforms are ranked here on a single mechanism: how a person enters an automated path, and what the system can prove afterward about the decision they made. Moxo scores 7.7 and ranks first; Camunda 8 scores 7.2, Microsoft Power Automate 7.1, Pega 6.9, n8n 6.7, Zapier 5.9, Kissflow 5.8 and ServiceNow 4.8, scored 22 September 2026 on the five weighted criteria. Those criteria cover the step type, the approver's account or licence, the routes available on a rejection, the audit record, and the meter that charges for the decision, and none of them can tell a review from a rubber stamp, so the methodology adds a check readers can run on any product in a few minutes: whether the decision record tells a considered approval from an instant one. Every figure was read from a vendor-owned surface and carries its own date.

Best Automation Platforms for AI Orchestration 2026

This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two neighbouring pages on this site answer different questions. Best Process Orchestration Platforms 2026 scores multi-step process control, error handling and state management. Best AI Agent Platforms 2026 scores building and hosting the agent itself. This page scores the layer between them: the connective tissue that lets an agent already built elsewhere reach the applications a business actually runs on. A platform that leads one of those pages can place low here, and two of them do. Scores derive from application and action catalogue counts, the exposure model each platform uses to publish those catalogues to an agent, setup effort, failure handling and cost per agent action. Every figure was retrieved from a vendor-owned surface on 11 August 2026 unless an earlier date is stated against it.

Common Questions

How do banks and wealth firms use Moxo for client onboarding?

Moxo's financial-services page (read 13 October 2026) pitches account opening and KYC reviews as shared work: the client gets a secure link to see what is needed and sign, while relationship managers, compliance and operations staff review and approve inside one tracked flow. The named bank case studies do not describe the current product, though: Moxo told Automation Atlas in writing on 6 October 2026 that its Citibank, BNP Paribas and Bank of Queensland stories describe Moxo Classic.

Can healthcare teams run patient-facing workflows on Moxo?

Yes for coordination work, once a signed BAA is in hand: Moxo told Automation Atlas in writing on 6 October 2026 that it signs BAAs, but it publishes none and did not say which plans the agreement covers or whether it reaches Moxo AI. Moxo says it has no native EHR, HL7 or FHIR connector, so anything that reads or writes the chart runs through its REST API or webhooks, or through a tool that signs its own BAA. These are vendor statements.

Who is accountable when an AI agent acts in a Moxo workflow?

The company that deploys the agent is accountable: Moxo's Terms and Conditions (read 13 October 2026) make the customer "solely responsible for any AI Content, including the accuracy, quality, appropriateness, and legality thereof". In the workflow, a named person owns each human step, Moxo's REST API refuses an organisation key for completing it, AI agents are their own user kind, and the record shows who completed a step but nothing documented shows the approver read it (API 2.0.0, read 13 October 2026).

How does Moxo keep humans in control when AI agents run a workflow?

Moxo keeps people on the decisions by design: approvals and other human steps are ones its product page says "only a person can close", and AI agents can fill preparer, advisor or reviewer slots around them (both read 15 September 2026). The checks on AI output are opt-in, though. In synthetic AutomationAtlas tests that day, an AI extract step's "Human review" and "Supervisor Agent" switches were both off by default, and the builder accepted the same role as a form's submitter and its approver.