Activepieces Cloud Pricing Plans: 2026 Price Guide
Oct 23, 202614 min read
Activepieces Cloud plans and prices, checked October 2026
The short answer
Activepieces Cloud pricing is credit-based and cheap to enter. Free is $0 with 1,000 credits a month, Plus is $20 with 10,000, and Team is $200 with 50,000 credits, 25 users and SSO, which means you must choose based on your monthly volume.
Extra credits cost $0.007 each, according to Toolcolumn, so overages become expensive if you exceed your plan's included credits.
The table shows what each plan includes.
| Plan | Price | Included | Where it fits |
|---|---|---|---|
| Free | $0 | 1,000 credits a month | Testing one real workflow before you commit |
| Plus | $20 a month | 10,000 credits | A small team running a few steady automations |
| Team | $200 a month | 50,000 credits, 25 users, SSO | The self-serve tier where SSO is included |
| Ultimate and self-hosted enterprise | Quoted by sales | Set in the contract | Self-hosted deployments or requirements beyond Team |
| Embed | From $36k a year | Set in the contract | Putting automation inside your own product |
If your own engineers will run the deployment and you don't need SSO, the free Community Edition is enough. It stops being enough when identity management or vendor support is a requirement.
How credits add up
Since the credit is the meter, the real question is how many your workflows burn each month.
At $0.007 a credit, a Plus account that needs 50,000 credits pays $20 plus $280 in extra credits, or $300, which is more than Team's $200.
Team covers the same volume for $200, so the choice is clear if you need 50,000 credits. Past a certain volume, upgrading is cheaper than paying overage.
For self-serve plans, use the pricing page. For self-hosted enterprise, SSO beyond Team, Ultimate or Embed, use the sales form.
**Past a certain volume, upgrading is cheaper than paying overage.
If you are running this arithmetic for your own team, see what the same workload costs on Activepieces.
Every current plan in one table
What each tier includes
| Plan | Price | Monthly credits | Users and SSO | Best fit |
|---|---|---|---|---|
| Free | $0 | 1,000 | Not the SSO tier | Testing flows before committing |
| Plus | $20 a month | 10,000 | Not the SSO tier | One builder running live automations |
| Team | $200 a month | 50,000 | 25 users, SSO | Departments that need single sign-on |
| Ultimate | Quoted by sales | Quoted by sales | Quoted by sales | Larger rollouts beyond Team limits |
| Self-hosted enterprise | Quoted by sales | Quoted by sales | Quoted by sales | Data that must stay in your infrastructure |
| Embed | From $36k a year | Quoted by sales | Quoted by sales | Shipping automation inside your own product |
Go past your allowance and each credit costs $0.007, so Team's 50,000 credits plus 10,000 extra adds $70 a month. Budget for the plan you land on, not the plan you start on.
The prices moved in opposite directions. Plus fell from $25 to $20 a month while Team rose from $150 to $200, according to Gravity's pricing history,.
Entry got 20% cheaper, but the SSO tier got a third dearer. The screenshot below shows the earlier four-tier layout with those old $25 and $150 prices, so treat any quote built on it as stale.
What sales quotes rather than lists
You will not find a published price for Ultimate, self-hosted enterprise or the credit allowance on Embed. Expect the quote to move with user count, credit volume, deployment model and support level.
A self-hosted licence for 25 users on standard support won't cost what 500 users on premium support does.
What the plans cost at realistic monthly usage
Below roughly 35,000 credits a month, Plus is the cheaper plan, and Team is cheaper beyond that. The chart compares monthly bills at three volumes, assuming Plus overage at $0.007 a credit.
Treat the scenarios as assumptions, not measurements, because your credits-per-run will differ. Read the gap between the bars as the cost of Team's 25 users and SSO, which only matter if you need them.
Three usage scenarios
Assume one person running a few automations, about 5,000 credits a month. On the published pricing, Plus costs $20 because 5,000 sits inside its 10,000 included credits.
Team costs $200. Unless you need SSO or multiple seats, you'd pay ten times more for headroom you never touch.
Assume a small team near 30,000 credits. Plus lands at $160: the $20 base plus 20,000 overage credits at $0.007. Team stays at $200 because 30,000 is under its 50,000 allowance.
The $40 difference buys SSO and seats, so for a team that needs either, Team is already the sensible choice at this volume.
Assume a department near 80,000 credits. Plus reaches $510, since 70,000 overage credits add $490 to the base. Team costs $410: $200 plus 30,000 credits over its allowance.
Here Team is $100 cheaper and includes more, so staying on Plus is simply the wrong plan.
Hidden costs and limits buyers hit
When the bill stops tracking run counts, the surprises start. Loops and retries multiply credits per run, Team has a user ceiling, and SSO starts at Team, so a growing rollout hits plan limits before it reaches a sales conversation.
Credit burn from loops and retries
A workflow that looks small on a run count can still be expensive if it uses AI steps, because those cost extra credits on top of the run. The sequence below is an assumption for planning, not a confirmed billing rule, and it shows where a bill grows faster than the run count suggests.
- The trigger fires and starts the run.
- Each action step that executes counts toward credits.
- A loop repeats its inner steps once per item, so the list length multiplies every step inside it.
- A failed step that retries counts again.
- Total credits per run is every step executed, repeats included.
Once the monthly allowance runs out, Activepieces charges $0.007 a credit on Plus and Team, so a failing integration that retries all night costs real money.
Because Team is the lowest plan with SSO and has a user cap, a department that outgrows the cap, or needs SSO on a larger headcount, has no self-serve step above it.
It moves into a sales quote.
Put these questions to sales, because the pricing page confirms the plan limits above but not the following. Does the trigger consume credits, and do polling triggers count on every check? Do retried steps and steps inside loops each count separately?
What happens at the allowance: on Plus and Team, runs keep going and extra credits are billed. What support response is included at our tier? For Ultimate, self-hosted or Embed, how do users, credits, deployment and support shape the quote?
Worth checking against a plan that does not meter every step: one credit covers a whole run on Activepieces.
Self-hosting, Community Edition and when to pay
When Community Edition is enough
When you need none of SSO beyond Team, vendor support, compliance paperwork or embedding, Community Edition is enough. Then the only cost of running it yourself is the server and your time.
On the hosting side, every VPS host that StackRates lists is well under the $20 Cloud Plus price: $5 a month for VPSDime, $5.35 for OVHcloud, $6 for HostHatch and $9 for Hetzner's CX23.
Hardware is not what you're paying for. Updates, backups and the 2 a.m. restart are, and that staff time is the real bill.
Any one of four things ends the free option. SSO beyond Team needs a quote, since Team at $200 a month includes SSO. Community Edition has no vendor support, so an outage is yours alone.
SOC 2 is in progress, not certified, so a buyer who requires the report can't be satisfied today. Embed starts at $36k a year, which is the price of shipping workflows inside your own product.
What shapes a sales quote
Four inputs set the quote: users, credits, deployment and support. Seat count scales licence cost, volume above the included allowance is billed at $0.007 a credit on Cloud, a self-hosted install differs from a managed one, and response expectations change the contract.
How automation platforms meter usage and pricing
Three ways to count the work
The first model charges per step, which is what task and operation meters do. It is easy to understand and punishes long workflows. The second charges per run or execution, which rewards long, branching flows and penalises very frequent short ones.
The third charges for capacity instead of activity: seats, workspaces or a licence for software you host yourself.
Credit systems sit between these. A credit is an abstraction the vendor can tie to steps, runs or heavier operations such as AI calls, which is why two credit-priced tools can behave very differently on the same workflow.
Ways to keep the meter low
Filter early so a workflow stops at its first step when an event isn't relevant, rather than running to the end and discarding the result. Prefer webhooks over polling, since a trigger that checks every few minutes can consume allowance while nothing happens.
Batch items instead of looping over them one at a time where the destination supports it, and cap retries so a broken integration fails quietly instead of spending all night.
The alternative to metering at all is to host an open-source engine yourself, which swaps a usage bill for an operations bill.
Cloud versus self-hosted automation deployment options
Metered cloud is one of four common arrangements. A hosted platform charges by usage and removes the operations work. A self-hosted open-source engine trades the usage bill for servers, upgrades and on-call time, as the Community Edition section above describes.
Enterprise integration suites sell capacity contracts with governance and support built in, and suit organisations whose procurement already runs through such vendors.
Plain code, such as a scheduled script or a queue worker, costs nothing per run but needs a developer to write, monitor and maintain every integration.
Matching the approach to the workload
The cheapest option depends on volume, how often the logic changes and who maintains it. Low volume with frequent changes favours hosted tools, because a builder can edit a flow without a deploy.
Very high volume with stable logic favours code or self-hosting, where cost stays flat as runs grow.
Strict data residency or audit demands push toward self-hosting or an enterprise contract regardless of price. Whichever route you take, the meter only matters once you know how many steps your real workflows execute.
How Activepieces pricing compares with Zapier, Make and n8n
Billing units are not equivalent
Each of the four counts something different: a Zapier task, a Make operation, an n8n execution and a credit. Zapier and Make charge per step, so a ten-step workflow consumes ten units per run.
n8n Cloud counts one execution per run however many steps it contains, which makes long workflows far cheaper there and short ones roughly even.
Activepieces bills the run: 1 credit per flow run however many steps it has, with AI steps costing extra credits on top.
Splitting work into smaller, more reliable steps never raises the meter, which is the opposite of the per-step billing above, and MoneyGram and Moneypenny run it in production.
Automation platform pricing comparison table
The table shows what each vendor bills for and which governance features it offers.
Cells marked "Unverified" weren't confirmed against the vendor's own dated pricing page and should be checked there before you rely on them.
| Vendor | Entry price | Billing unit | Free tier | Self-hosting | SSO | Source and date |
|---|---|---|---|---|---|---|
| Activepieces | Free at $0, Plus at $20 a month | Credit | Yes, 1,000 credits a month | Yes | Team, $200 a month | activepieces.com/pricing, October 2026 |
| Zapier | Unverified | Task | Unverified | Unverified | Unverified | Unverified |
| Make | Unverified | Operation | Unverified | Unverified | Unverified | Unverified |
| n8n Cloud | Unverified | Execution | Unverified | Yes, as a separate self-hosted edition | Unverified | Unverified |
If your workflows are short, per-step billing favours you; if they are long and branching, per-execution billing does.
If self-hosting is a requirement, the shortlist narrows to vendors that ship a self-hosted edition, and the quote then depends on deployment and support, not unit price. Model one real workflow on all four before you decide.
What to do before you choose a plan
Take your three busiest workflows and run the sequence below before committing. Pricing is credit-based, so measure consumption first, not seats.
- Count the steps in each of your three busiest workflows. Every step that runs is what burns credits, so a workflow with a loop or a polling trigger costs far more per day than its diagram suggests.
- Multiply steps by expected runs per month, add the three, and add a margin for retries. That total is your credit estimate, and it tells you whether the entry tiers can hold your load or you're already near the ceiling.
- Start on Free or Plus. Pick Free if your estimate sits comfortably inside its allowance and Plus if it doesn't. Starting low costs you little, because overage is metered per credit and not a hard stop on the account.
- Watch usage for a full month. One month exposes the spikes your estimate missed, such as a batch import or a failing step that retries repeatedly. Compare actual burn against the estimate before you change tiers.
- Move to Team when you need SSO, when you outgrow the user cap of 25, or when your volume is high enough that upgrading costs less than paying overage.
Check current tiers on the pricing page at https://www.activepieces.com/pricing, which lists Free at $0, Plus at $20 a month and Team at $200 a month.
If you need self-hosted enterprise, SSO beyond Team or Ultimate, those are quoted by sales, and Embed starts from $36k a year, so send your measured credit figures through https://www.activepieces.com/sales and the quote will start from your data, not a guess.
Frequently asked questions
Is there a free plan? Yes, there's a Free plan at no charge with a monthly credit allowance.
Can I change plans or cancel mid-month? Upgrades and added seats take effect immediately and are prorated, while downgrades apply at the end of the billing period.
Before upgrading, note that upgrades and added seats apply at once and are prorated, while downgrades take effect at the end of the period.
If you're close to buying Team at $200 a month or beyond, ask sales through https://www.activepieces.com/sales so the terms are in writing.
Do unused credits roll over? Plans are described as monthly allowances, so plan as if unused credits don't accumulate.
Integrations and compliance
Does the Free plan include all integrations? I can't confirm that from the published plan descriptions, so verify the specific integrations your workflows need in the integrations library before building on Free.
Is Activepieces SOC 2 certified? No. The SOC 2 programme is in progress, so the certification isn't held today.
If a security review requires a completed report, record that status in your vendor assessment and raise it with sales early, because it may affect the timeline for an enterprise or embedded rollout.
Related reading
References
Running the numbers
See what the same workload costs here.
Free forever plan, and every paid plan self-hosts at no extra cost.
See pricing Talk to sales
