Moxo

About Moxo

Moxo AI is a process orchestration platform for work that crosses company lines. You build templates of human steps such as forms and approvals, with AI agents and automations around them, and each run is a Flow that outsiders can join through account-free links. It is served at app.moxo.com, separately from the older Moxo Classic. Its publisher began as Moxtra, which a June 2021 PR Newswire release says was co-founded in 2012; Moxtra announced the Moxo name on 7 March 2022, and as of 15 September 2026 Moxo's Terms of Service, Terms and Conditions and Privacy Policy name the company as Moxo, Inc. The paper trail starts a little earlier than the brand: Moxtra, Inc.'s first SEC Form D, filed on 8 August 2013, lists its previous name as Xebew, Inc., incorporated in 2012, and Xebew, Inc. was the original applicant on the MOXTRA trademark filed on 3 January 2013. That 2013 filing gave a Los Gatos, California address; Moxo, Inc.'s trademark records now place the company in Cupertino.

The read that matters for a buyer: Moxo's real product is the approval, not the AI. A Flow is "A single running instance of a Template, carrying its own data and status" (Description of Services, read 15 September 2026), built from more than thirty step types, and each human-action step can carry up to three assistive slots, a preparer, an advisor and a reviewer, each fillable by a person or an AI agent. The AI prepares and checks; a person owns the step. The price list says the same thing more bluntly. Team, the only plan with a published price ("$500 /mo" in the monthly view or "$5,000/yr" in the yearly view on 15 September 2026), includes Approvals and Magic links, 100 flows and $100 of AI a year, and unlimited seats. Agent Foundry and the Automation, Review, Prepare and Advise Agents start on Scale (500 flows and $500 of AI a year, custom quote), and Supervisor Agents appear only under Enterprise. At list price, Moxo sells structured human sign-off with outsiders in the loop; the agents are the upsell.

That makes the wrong fit easy to spot. There is no free plan, and branching, loops, triggers, webhooks, REST APIs, the audit log and SAML SSO are all listed from Scale, so app-to-app automation with no human decision in it has no published Moxo price. The pricing page defines neither a flow nor the AI unit and states no overage price, although Moxo's Terms and Conditions, read that day, say fees may include overage fees. Team's allowance also moved under a steady price: the 26 August 2026 Internet Archive capture listed Team at the same price with 250 flows and 25,000 AI credits a year, and with branching, loops, triggers, webhooks, REST APIs and MCP connections that the 10 September 2026 capture listed under Scale.

Under the hood, the documentation is serious. The Description of Services covers a public REST API, webhooks, SAML 2.0 single sign-on and MCP in both directions: workflows can call MCP servers as tools, and Moxo "exposes itself as an MCP server". It says the service "is hosted on Amazon Web Services" and that "Moxo undergoes SOC 2 Type II auditing", while Moxo's security page, read the same day, says Moxo "is SOC 2 Type II and SOC 3 certified". Those are not the same claim, so ask for the report and check which wording your contract uses.

Our synthetic tests, on a test workspace that is no guide to what Team includes, cut both ways. On 14 September 2026, Build with AI turned a written recruitment brief into a four-step template (form, AI extraction, internal review, approval) with three human roles, and showed "Est. $0.38 per run" before anything was published; a later reading showed $0.17 with no step edited. On a supplier brief the same day, it described two approvals as running "independently in parallel", and Moxo's own publish validator refused that design with 2 blocking issues. That is the right outcome: the AI may draft the process, but it doesn't get to ship one that doesn't hold together. The Capabilities settings page was candid too, showing 12 flow actions and 6 flow controls as available and counting 8 and 3 more as "Not available on your plan" without naming them. On 15 September the Approval step offered four rejection routes, and across both days the audit log gave every row an actor, such as "AI Agent", "System", "Public link" or the person's name; 17 rows were read for one flow. Closest comparators covered on this site: Zapier, n8n and Kissflow.

Editor's Note: The moment I trusted Moxo a little more was when it said no to itself. We recently asked Build with AI for a supplier process with two parallel approvals. Its summary said they would run "independently in parallel", and the publish validator then refused that design with 2 blocking issues. In a product sold on accountable decisions, a validator that overrules the AI builder is a feature, not an embarrassment. The same builder offered four ways to handle a rejected approval, so what happens after a "no" is settled before a flow goes live. — Rafal Fila, ShadowGen