How much does Moxo cost in 2026?

Moxo sells flows, not seats, and publishes exactly one price.

Source: moxo.com/pricing, monthly and yearly views, 15 September 2026.

What decides the bill: flows and dollars of AI a year

Two meters, and the pricing page defines neither. The flow is defined elsewhere: Moxo's Description of Services, read 15 September 2026, calls it "A single running instance of a Template, carrying its own data and status". In synthetic AutomationAtlas tests, a template's Flows counter rose by one the moment a flow started (14 and 15 September 2026). That doesn't establish how an invoice counts, but it is the question to put to sales: if a flow counts when it starts, every abandoned onboarding is a flow you paid for.

The AI meter is the more interesting one. The pricing page sells "$100 of AI/yr", yet the product still counts credits. On 15 September an audit row in our test read "13 credits consumed (ai credits)" for one AI extract step, and Moxo's API changelog, read 14 September 2026, describes reports that show AI spend "in credits, the unit you buy rather than our provider bill". Moxo publishes no conversion between the two. A dollar allowance plays well in a procurement meeting because it looks like a budget line with a ceiling, but until the credit rate is in writing it is a label, not a price. The builder's estimates move as well: on 14 September it showed "Est. $0.38 per run" for a four-step template before publishing, and $0.17 at a later reading with no step edited.

What free covers: no free plan is listed

There is no free tier to prototype on. As of 15 September 2026, moxo.com/pricing lists Team, Scale and Enterprise but no free plan, and its header links to "Request free trial" without stating a trial length. Treat the pilot as a sales conversation, and get the trial's flow and AI limits stated before you start building.

Metered overage: allowed by the Terms, unpriced on the page

This is where to slow the procurement down. Moxo's Terms and Conditions, read 15 September 2026, say "Service Fees may include one-time fees, subscription fees and overage fees", while moxo.com/pricing stated no overage rate that day. The contract allows a charge the price list doesn't show. Under the same Terms, a price change applies from "the next Subscription Term, which takes place at least sixty (60) days after the notice of the price change". That protects the fee you can see; it can't protect a rate nobody wrote down, so put the overage rate in the order form.

The test workspace's Billing panel was no help either. In AutomationAtlas testing on 26 August and 14 September 2026, it showed no plan name and read "Your plan is managed by Moxo's sales team".

Discounts and floors: Team is the only published price

Team sets the floor at "$500 /mo" or "$5,000/yr" on moxo.com/pricing (15 September 2026). The page doesn't say whether "$500 /mo" is billed monthly, so no annual discount can be read from it. What you can read is the direction of travel: Internet Archive captures record two restructurings between 7 August and 10 September 2026.

At the unchanged $5,000 a year, the price per included flow at full use went from $20 on the August terms to $50 now, and the most a team can launch without running out before year end fell from about 21 flows a month to about 8 (AutomationAtlas arithmetic from the dated list prices). The AI allowance changed units in the same move. The fee held and the allowance moved, so if you buy, fix the allowance for the term in the contract, not just the fee.

How it compares: Team fits poorly at low volume or without human steps

Per-flow pricing is a bet on volume. At Team's "$5,000/yr" (moxo.com/pricing, 15 September 2026), 100 flows work out at $50 each, and an organisation running 20 flows a year would pay $250 per flow (AutomationAtlas arithmetic). The other side of the ledger is seats: all three plans list unlimited seats, so adding clients, partners or contractors to a flow doesn't raise the bill. Volume beyond 100 flows a year cannot be costed from public sources, and the page lists triggers, webhooks and REST APIs only from Scale, a custom quote.

The meter also shapes design. When every run costs money and seats are free, there is a quiet incentive to cram a whole client relationship into one long flow instead of several clean ones. Decide the process model first, then check it against the meter, not the other way round.

Editor's Note: The number that stuck with me wasn't the $5,000. When we recently built a synthetic four-step template, the builder showed "Est. $0.38 per run" before we had published anything, and a later look showed $0.17 with no step changed. A live cost estimate is genuinely useful, and I'd rather have one than not. But it is quoted in dollars while the audit log counts credits, and Moxo publishes no rate between them, so a buyer can't turn that badge into a budget. The caveat: one template, a workspace that isn't a Team plan, and we never learned why the estimate moved, so get the credit rate from Moxo in writing before you plan against it. — Rafal Fila, ShadowGen