TL;DR
- iPaaS pricing follows one of six models: per task, per credit, per connection and transaction, per flow, per user, or a flat license.
- The model predicts your bill better than the sticker price. Per-task and credit billing rise with every extra step, retry, and poll. A flat license doesn't.
- Before you sign, ask the vendor to price one real workflow at three times your expected volume.
Every iPaaS comparison leads with a price. Few explain the pricing model behind it, and the model, not the number, decides whether your integration bill stays predictable or becomes a quarterly surprise. This guide compares the six iPaaS pricing models in use today, with published numbers from the platforms that use each one and the way each model breaks under load.
iPaaS pricing models at a glance
| Model | Used by | What raises the bill | Where it breaks |
|---|---|---|---|
| Per task or operation | Zapier, Tray.ai, Workato | Every workflow step counts as a billable task | Complex workflows and retries multiply the bill, not just the workload |
| Credit-based | Make | Credits consumed per operation | Frequent polling and loops burn credits; extra credits cost more |
| Connections and transactions | Boomi, MuleSoft | Connections, message volume, and runtime counts | Separately priced add-ons appear at renewal |
| Per flow, quote only | Celigo | Number of integration flows | Costs climb as your portfolio grows, with no public price list |
| Per user, with a connector cliff | Power Automate | Licensed users, plus premium connectors | One premium connector moves every user of that flow to Premium |
| Flat license | Koodisi, SnapLogic | Contract scope, not task or data volume | You need to confirm what the contract covers at peak volume |
How each iPaaS pricing model works
Per task or operation
Zapier, Tray.ai, and Workato bill each workflow step as a task. A ten-step Zap uses ten tasks every time it runs. Zapier's Team plan is $69 a month for 2,000 tasks. Tray.ai's plans run from about $695 to $2,450+ a month, and Workato's task-based contracts reportedly start at one million tasks, priced by quote. The trade-off is simple: you pay little for simple automations and a lot for complex or noisy ones.
Credit-based
Make switched from operations to credits in August 2025. Plans start at $9 to $29 a month, but frequent scenarios add up fast: polling every 15 minutes uses roughly 2,880 credits a month for one scenario before it processes any data, and extra credits cost 25% more than your plan rate.
Connections and transactions
Boomi prices on connections, transaction volume, and runtime counts; its Professional plan is around $550 a month, with enterprise tiers quoted. MuleSoft moved to flows, messages, and data-throughput pricing in 2024 and is quote-only. Both are predictable if your connection count is stable, and harder to budget when add-ons are priced separately.
Per flow
Celigo doesn't publish prices. Plans are quoted by the number of integration flows, so cost grows with the size of your portfolio rather than your traffic.
Per user, with a connector cliff
Power Automate is priced per user, at $15 per user per month for Premium. The catch is structural: if a flow uses a single premium connector, such as Salesforce, SAP, ServiceNow, or SQL Server, every user of that flow needs a Premium license. A 200-person team that builds one cross-department flow touching Salesforce can end up licensing everyone at the Premium rate.
Flat license
SnapLogic uses flat package pricing that isn't billed by data volume. Koodisi uses a flat enterprise license that doesn't bill per task or per step, with the API Manager included rather than sold as an add-on. Plans are quoted against your deployment model and scale. The question to ask any flat-priced vendor is what the contract covers when your volume grows.
Why the pricing model matters more than the price
A $69 Zapier plan and a $695 Tray.ai plan look like different price points. What predicts your real cost is what happens when a workflow runs ten times more often than you planned: a partner API starts failing and retries pile up, an onboarding surge hits, or a daily batch becomes hourly. Under per-task or credit billing, that spike lands on the invoice straight away. Under a flat license, it doesn't.
Self-hosting isn't automatically cheaper either. n8n's Community Edition is free, but SSO, Git sync, and multiple environments sit on paid plans of up to $800 a month, which many teams only discover when they need those features in production. For more on costs that don't appear on a price list, see the hidden costs of data integration platform implementation.
How to estimate your iPaaS cost
- List your ten busiest workflows with their steps per run and runs per month.
- Multiply steps by runs to get tasks or operations per month for each one.
- Add a buffer for retries and polling: failed calls that retry and scheduled checks that find nothing still count.
- Price the result under each vendor's model, including connectors, environments, and support.
- Repeat at three times the volume to see which bill holds steady.
What to ask a vendor about pricing
- What happens to my bill if one workflow's volume triples for a month? Walk me through the maths.
- Which features are add-ons in practice: premium connectors, master data management, extra environments, enterprise support?
- If I add one connector or integration, does it change the tier for my whole team or just that workflow?
- Is there a published price list, or is everything quoted? Boomi, MuleSoft, Celigo, and Workato are quote-based, so budget time for a sales conversation with each.
If you're comparing vendors on more than price, our best iPaaS platforms in 2026 guide covers deployment and fit as well. Teams leaving MuleSoft should also read why to check the pricing model first.
Frequently asked questions
How much does an iPaaS cost?
It ranges widely. Make starts at $9 a month and Zapier's Team plan at $69, while enterprise platforms such as Boomi, MuleSoft, Workato, and Celigo are quote-based and often reach five or six figures a year. Your workflow volume and the vendor's pricing model matter more than the starting price.
Which iPaaS pricing model is cheapest?
None is cheapest in general. Per-task and credit pricing can be very cheap at low, steady volume and expensive at high or spiky volume. Flat licensing trades a higher starting price for a bill that doesn't move with usage.
What's the difference between task-based and credit-based pricing?
Both charge per unit of work. Task-based pricing (Zapier, Tray.ai) usually counts each workflow step as one task. Credit-based pricing (Make) assigns credits to operations, which makes costs harder to predict in advance.
Does flat-rate iPaaS pricing mean unlimited usage?
Not necessarily. Flat usually means no per-task, per-connection, or per-volume charges within the contracted scope. Ask what the contract covers at your peak volume.
Why don't iPaaS vendors publish prices?
Enterprise contracts are negotiated around volume, support, and connectors, so many vendors only quote. That makes side-by-side comparison slower, which is why pricing one real workflow with each vendor is worth the effort.
The takeaway
How a pricing model behaves under load predicts your cost better than any sticker price. Before signing, ask what happens to the bill when volume spikes, not just what it looks like today. If you'd like that worked out for your own workflows, talk to Koodisi about pricing.