Moxo vs Pega in 2026: Authority Matrices, Majority Votes and the Price of the Next Case

Overview

Pega publishes a per-unit price for this work and Moxo publishes an allowance, and that is the first thing to settle between them. Pega's AWS Marketplace listing prices Workflow Automation at "$162,000.00" a year for "up to 120,000 cases per year", with "$1.35/unit" beyond that allowance (read 21 September 2026). Moxo prices one plan, Team, at "$5,000/yr" for 100 flows (moxo.com/pricing, 22 September 2026). Across the eight platforms in Automation Atlas's human-in-the-loop ranking, Pega's is the only per-unit rate card and the only six-figure floor (scored 22 September 2026).

They also disagree about who may approve. Pega routes by the org chart and books outsiders in a licence class; Moxo routes by field, rule or desk, and keeps a record of an outsider without ever issuing them a login. Five rounds follow, each with a named winner. Pega's side rests on docs.pega.com and its AWS Marketplace listing, read in a browser on 21 and 23 September 2026; Moxo's on its published pages, its API reference and synthetic AutomationAtlas builder tests.

Company Snapshot

The Core Trade-Off: Pega Routes by the Org Chart, and Its Log Names the Approver

Pega takes the routing round, and the reason is the org chart. Pega Platform '26 can send an approval to a user by name or by reference, to "the reporting manager of the user who last updated the Case", to a Work Queue or by business logic, and the approver can answer by email or push notification (docs.pega.com, updated 16 June 2026). The Approval shape adds the authority matrix: it "Routes a Case to one or more reviewers for an approval, based on a user name, reporting structure, or authority matrix". The record then closes the loop, because "Each history instance contains a date, type, user ID, and memo." The user ID is there because the operator existed before the work did, and that is the return on provisioning.

Moxo routes by fixed contact, a kickoff form field, a flow value, round-robin or rules, and it can hand work to a desk whose routingKey matches a field value exactly, case-insensitively and never fuzzily. It documents no routing by reporting line. For an outsider who arrived by link, its audit log files the opening under "Public link": an honest label that records an assigned inbox was opened, not who opened it.

Pega pays for all this with provisioning. You can route the approval step "only to participants that have an account in your application", and the escape hatch for everyone else is narrowing. A Directed Web Access link "does not require login, but the user can use it only once", configuring it starts with an administrator creating an operator of type External, and "DWA is not supported in Constellation applications". Pega's licence compliance page then books "processing performed by Web users (typically through the Directed Web access feature), classified as Invocation users", apart from "Human users who complete business operations using the system, as Named users", so a client who approves a contract lands in the same bucket as a script posting a REST call. Moxo keeps a record of the outsider, a user of kind external with status ACTIVE, but issues no login and books no licence class.

When a Committee Signs, Moxo Counts the Majority

Moxo wins this round, because it treats a committee as a committee. Group assignments complete on "any one, all, or majority" in the Description of Services, the API's completion mode carries MAJORITY, and the changelog names "majority-vote approval steps" (developers.moxo.com, read 23 September 2026). A credit committee or a three-partner sign-off is one step with a vote, not a subprocess you draw. Behind the vote sit four named rejection routes, "Revise and resubmit", "Let the approver decide", "Run rejection steps" and "End the flow", and the manager's moves have names too, from remind and reassign to reopen and force-complete.

Pega's approval is a named lifecycle step, added on the Workflow tab through "Add Step > Approve/Reject", and its rejection has three named destinations, "Reject and move Case to the next Step", "Reject and change Stage" and "Reject and resolve". No Pega page read for this guide documents a majority vote. Pega keeps a real edge on escalation: an assignment nobody completed can Notify, Reassign to, or Resolve, and the target can be a queue, "specify the user or Work Queue" (docs.pega.com, read 21 September 2026). The queue is the option most buyers overlook. Moxo's named verbs are documented in its API, which is listed from Scale.

Across the eight platforms in Automation Atlas's human-in-the-loop ranking, two reach four or more named rejection routes with a timed escalation path, Moxo and Camunda 8, and two stop at approve and deny, n8n and ServiceNow; the remaining four sit between (scored 22 September 2026).

Once Anyone Signs, Moxo Locks the Document

Moxo takes the signed-record round on two facts a buyer can check before a demo. eSignatures are listed on Team, the plan with a published price (moxo.com/pricing, read 23 September 2026). And the API will not replace a step's document once anyone has signed it: the refusal is ESIGN_ALREADY_SIGNED (409), because "From that moment the document is a signed record and cannot be swapped." A contract cannot change underneath a signature, and the product enforces that rather than trusting a process note.

Pega's Workflow Automation listing names no signature step, so for a Pega buyer the signature is a question for the quote. Pega's case history resolves to a named user ID ("a date, type, user ID, and memo", docs.pega.com, History-Add method), while Moxo's audit log files a link-borne opening as "Public link" (synthetic tests, 14-15 September 2026), which is why the user ID counts in the routing round, where Pega wins.

Pricing (as of September 2026)

Moxo (from moxo.com/pricing)

Team is the only published price: "$5,000/yr" for 100 flows and $100 of AI a year with unlimited seats, read 22 September 2026. Monthly billing has gone. The "$500 /mo" figure no longer appears, the billing toggle survives in the markup but is disabled, and every plan's button now reads "Book a demo", so the smallest commitment Moxo sells is a year. The header also links "Request free trial", a trial Moxo's team builds around your processes, with no length stated. There is no free plan and no published overage rate. Scale and Enterprise are custom quotes, and Agent Foundry, the named agents, the audit log, "Webhooks", "REST APIs" and "Connect via MCP" all start at Scale.

What that $5,000 buys shrank inside three weeks. An Internet Archive capture of moxo.com/pricing on 26 August 2026 shows Team carrying 250 flows a year; the capture of 10 September 2026 shows 100 flows at the same price, a 60% cut to the allowance with the headline figure untouched. List cost per flow went from $20 to $50 in a fortnight, so a buyer modelling Team on August's numbers is modelling two and a half times the volume the plan now carries.

Pega (from AWS Marketplace)

pega.com/pricing is a dead link and Azure Marketplace carries no priced Pega Platform listing, but AWS Marketplace publishes a rate card: Workflow Automation "up to 120,000 cases per year" at "$162,000.00" with "$1.35/unit" beyond the allowance, scaling to "up to 1,000,000 cases per year" at "$1,188,000.00" and "$1.19/unit" (read 21 September 2026). A list price with a stated overage rate is more than most of this category publishes.

Cost Comparison (Estimated Annual)

Both meters charge for the container rather than the decision. Moxo counts flows, Pega counts cases. A process carrying four approvals empties its allowance no faster than one carrying a single approval, so adding a control step to satisfy an auditor costs nothing extra on either price list. What neither list tells you is what an approval costs. Turning Pega's rate card into a per-approval figure needs an approvals-per-case assumption no vendor publishes, so it is not a sum to attempt.

The two price cards decide two rounds, and they go to different vendors: the way in, which follows, and the case past the allowance, further down.

Automation Atlas's human-in-the-loop ranking, scored 22 September 2026, places Moxo first at 7.7 and Pega fourth at 6.9, a quarter of the weight sitting on how the human enters the path. Move that weight onto cost and both fall by the same margin, Moxo to 6.9 and Pega to 6.1, so their order holds.

Editor's Note: Two rate cards, and only one of them, we found, says what happens next. Pega prints the price of the unit after the allowance, "$1.35/unit" past 120,000 cases, so a year that overshoots is an invoice a buyer can model before signing. Moxo prints an allowance and stops. That allowance moved: the same $5,000 bought 250 flows in August and 100 by September. Spend the hundredth in month nine and the next flow is refused; no published rate buys the hundred-and-first, so the remedy is a sales call at the moment the work is busiest. Size the year at 100 flows before signing Team, or get the overage rate written into the contract. Within that allowance, Team already carries Approvals, Decisions and eSignatures at a published price. — Rafal Fila, ShadowGen

The Way In Belongs to Moxo: $5,000 a Year Against $162,000

Moxo wins the way in by knockout. A team running up to 100 cases a year can price Moxo from its own page: Team is "$5,000/yr" for 100 flows with unlimited seats, and it already carries Approvals, Decisions, eSignatures and SMS notifications (moxo.com/pricing, read 23 September 2026). Pega's smallest published commitment is "$162,000.00" for up to 120,000 cases, more than 32 times the outlay, and below that tier there is nothing to read. pega.com/pricing is a dead link and Azure Marketplace carries no priced listing, so a smaller Pega deployment is a quote.

For a firm whose cases fit inside Team's 100 flows a year, that settles the shortlist before a feature is compared. Pega's answer is that it is far cheaper per unit at volume, $1.35 a case against $50 a flow at Team's allowance, and it also prices the case past the allowance, the round Pega takes further down. Moxo's catch sits one plan up: branching, the audit log and the API all start on the custom-quoted Scale plan.

Governance, Admin Controls, and Compliance

Pega

Licence compliance is a governance surface in its own right, because every outsider let into a case is a number somebody defends at renewal. One further design limit sits beside the Constellation exclusion: a Directed Web Access link is single use, so a reviewer who wants a second look needs a fresh one (docs.pega.com, read 21 September 2026).

Moxo

Moxo's controls are documented but gated. The Description of Services lists SAML 2.0 single sign-on and "per-domain SSO enforcement", while moxo.com/pricing puts SAML SSO and the audit log at Scale, so no published price carries either (read 15 September 2026). Our Moxo profile covers where its compliance wording differs between pages.

Neither vendor's documentation settles how long the record is kept. Pega documents the four fields of a history instance with no retention period beside them, and Moxo's legal pages state no retention period, though its security page markets a "7+ Year audit trail", so retention is a procurement question on both sides.

Past the Allowance, Pega Knocks Moxo Out

Pega wins this round by knockout, because it prices the case after the allowance and Moxo does not. The AWS Marketplace card sets "$1.35/unit" beyond 120,000 cases on a "$162,000.00" floor, and at each of the four Workflow Automation tiers the overage rate is that tier's own price per case, rounded to the cent, so overshooting carries no premium. Moxo prints no overage rate at all: once Team's 100 flows are spent the next is refused (on Scale, where the API starts, the answer is 402 QUOTA_EXCEEDED), and the remedy is a sales call held at whatever moment the work is busiest. On Pega the expensive mistake is committing too high; on Moxo it is sizing too low.

The sum fits on a whiteboard. "$162,000.00" for 120,000 cases is $1.35 a case, against "$1.35/unit" of overage; "$324,000.00" for 250,000 is $1.30 against "$1.30/unit"; "$621,000.00" for 500,000 is $1.24 against "$1.24/unit"; "$1,188,000.00" for 1,000,000 is $1.19 against "$1.19/unit" (12-month prices, read 23 September 2026). Staying on the 120,000 tier and paying overage costs exactly what the 250,000 tier costs at 240,000 cases, and each step up breaks even at roughly 96% of the larger allowance. Commit to 120,000 and run 245,000, and you pay about 2% more than the right tier would have cost; commit to 250,000 and run 130,000, and you have prepaid 120,000 cases nobody opened, $148,500 more than the smaller tier plus its overage.

So commit to the volume you are sure of, not the one in the business case, and let the published overage carry the optimism. That runs against the instinct most tiered price lists train, and the listing's 36-month option carries a discount that moves the break-even, so rerun the sum before taking it. Moxo offers no such lever: Team is one fixed allowance, Scale's 500 flows a year is a custom quote, and Pega's smallest published commitment is 240 times as many units of work. A buyer between the two, at a few thousand cases a year, gets a quote from each.

What Moxo does well here it shares with Pega: both meter the container, not the decision, so adding a fourth approval to a case costs nothing extra on either list.

Selection Framework

Start from your annual volume, then from who approves.