Skip to plans

Pricing

Priced by run, not by step or seat.

Start free. One run is one execution of a published flow, whether it has three steps or thirty — so splitting a step in two never changes your bill.

Automation

For the automations your business runs on.

Lead routing, invoice reminders, support triage, order sync — anything you would wire between your apps, your database and your own APIs. Every plan carries every step type, every provider, versions and the stored trace.

FREE
US$ 0forever

150 runs / month

Unlimited testing in Sandbox on top of the allowance. No card to start.

  • Every step type and every provider
  • Versions and run history
  • Community support
STARTER
US$ 19per month

1,000 runs / month

For the first automations a team actually depends on.

  • Everything in Free
  • Scheduled jobs and outbound webhooks
  • Email support
SCALE
US$ 149per month

15,000 runs / month

For automations carrying real volume across several teams.

  • Everything in Pro
  • Priority support
  • Onboarding with our team

Above your allowance, runs keep going at US$ 10 per 1,000 runs — nothing pauses, nothing queues, and no automation stops mid-month.

Free to build. Free to test. Paid by the run it makes.

YOU PAY FORRuns your flows make
YOU NEVER PAY FORSteps, seats, retries, or flows

What you are buying

A run is one execution of a published version.

Delivered, retried or stopped — each is one run against your monthly allowance. Sandbox runs draw from the same pool, so there is a single number to watch instead of a bill assembled from parts.

Above the allowance nothing stops. Extra runs bill at a flat rate per thousand, so a busy month is a line on an invoice rather than an outage in your operations.

MONTHLY ALLOWANCE4,000 / 4,000
Sandbox + LiveResets monthly

Regulated decisions

Approving credit, screening for fraud, onboarding customers?

That work needs machinery the automation plans do not carry: case management and manual review queues, an approval step before a version goes live, single sign-on and granular permissions, and a decision trace kept for audits and disputes. Same engine, same canvas, different plan.

ENTERPRISECUSTOM
Talk to usvolume pricing

For programs past the Startup allowance, or with a security review, procurement path, or rollout plan attached.

  • Decision volume priced to your traffic
  • Security and architecture review with our team
  • Support through the migration of an existing policy
Talk to sales

See what ArboRule does for risk teams

Questions before you start

Pricing questions, answered plainly.

How much does ArboRule cost?

Automation plans start free with 150 runs a month, then US$ 19 for 1,000 runs, US$ 49 for 4,000 and US$ 149 for 15,000. Runs above your allowance are billed at US$ 10 per 1,000. Regulated decisioning — credit, fraud and onboarding, with case management and review queues — starts at US$ 500 a month for 50,000 decisions.

What counts as one run?

One run is one execution of a published flow version, from the trigger to the last step. A flow with three steps and a flow with thirty each count as one run, a branch that is not taken costs nothing, and a delivery that needed six retries is still one run. Sandbox runs and live runs draw from the same monthly allowance, so there is one number to watch.

Do I pay per user or per seat?

No. ArboRule is priced on runs, not seats. Everyone who touches the work — whoever built the automation, whoever operates it, whoever owns the policy — can work in the same workspace without changing what you pay.

Can I try ArboRule before paying?

Yes. Create a workspace and build in Sandbox at no cost. You can run test cases, inspect the step-by-step trace, and iterate on the logic. The Free plan also carries 150 live runs a month, so a first automation can go live without a card.

What happens if I go over my monthly allowance?

Runs keep going. Volume above an automation plan's allowance is billed at US$ 10 per 1,000 runs, and volume above the 50,000 included in the Startup decisioning plan is billed at US$ 0.03 per decision. Nothing pauses, nothing queues, and no automation stops mid-month.

When do I need a decisioning plan instead of an automation plan?

When the work is a regulated decision. Case management, manual review queues, an approval step before a version goes live, single sign-on, granular permissions and a long trace retention are on the decisioning plans only. If you are approving credit, screening for fraud or onboarding customers, that is the plan you need; if you are routing leads, chasing invoices or syncing orders, an automation plan is the whole product.

Do I need engineering to change a flow?

No. The owner edits the flow, tests the new version in Sandbox, and publishes it — no deploy and no engineering ticket. The API endpoint your systems call stays the same across versions.

Ready when you are

Build it free. Pay when it carries traffic.

Create a workspace, build the automation you already need, and choose a plan the day it is ready for Live.

Need a larger program? Talk to sales