iPaaS Cost UK (2026): Pricing Models, Tiers and True Total Cost of Ownership

"How much does an iPaaS cost?" sounds like it should have a sticker price. It doesn't — and the gap between the advertised tier and what you actually pay over a year is where most UK buyers get caught out.

This guide explains the three pricing models iPaaS vendors use, gives indicative UK ranges for the main platforms in 2026, breaks down the hidden costs that inflate the bill, and shows when an iPaaS genuinely beats a custom build — and when it quietly costs more.

A note on the numbers: these are indicative UK market ranges for 2026, not quotes. Most enterprise iPaaS vendors don't publish list prices and route everything through sales, so real figures depend on volume, connectors, contract length and negotiation. We've converted vendor USD pricing to rough GBP at prevailing rates — treat every figure as a ballpark to pressure-test, not a price to budget against.

The three iPaaS pricing models

Before comparing platforms, you need to understand what you're being charged for. There are three dominant models, and they reward very different usage patterns.

1. Task / operation-based (the consumption model)

You pay per unit of work. Zapier counts tasks (each action a Zap performs), Make counts operations / credits (each module run). A single business event — "new Shopify order → create Xero invoice → post to Slack → update a sheet" — is one trigger and four actions, so one order can burn four to five tasks.

This model is cheap to start and brutal to scale. Cost tracks volume, not value, so a high-frequency low-value flow (polling a feed every minute) can cost more to run than a strategic one.

2. Connector / endpoint-based

You pay per connected application. Boomi and Celigo lean this way — Boomi meters by connection, Celigo bundles a set number of integration flows. Adding one more system (say, plugging Salesforce into an existing finance stack) can mean a five-figure annual uplift, almost regardless of how much data actually moves. Volume allowances are usually generous; breadth is what costs.

3. Recipe / workload-based (enterprise consumption)

Workato charges for active recipes plus Workload Units (WLUs) — a measure of processing consumed. It blends the two models above: you pay for both how many automations you run and how hard they work. That's predictable for steady workloads, less so when AI steps and large data jobs spike consumption.

Indicative UK iPaaS pricing, 2026

Platform	Model	Indicative UK entry	Typical annual spend	Best fit
Zapier	Per task	~£24/mo (Starter, 750 tasks); ~£58/mo Professional (2,000 tasks)	£300–£3,000/yr	SMEs, simple SaaS-to-SaaS automations
Make	Per operation/credit	~£8/mo (Core, 10k ops); ~£15/mo Pro	£100–£2,500/yr	Higher-volume, visual multi-step scenarios
Celigo	Per flow + volume	~£470/mo base	£6,000–£40,000+/yr	Mid-market eCommerce, NetSuite stacks
Workato	Recipes + WLUs	~£1,600/mo (entry, annual)	£8,000–£160,000+/yr	Mid-market to enterprise automation
Boomi	Per connection	~£430/mo base (5 connections)	£35,000–£200,000+/yr	Enterprise data + API integration

The jump from the first two rows to the last three is the real story. Zapier and Make are SaaS subscriptions you can put on a card; Workato, Boomi and Celigo are procurement projects — sales cycles, annual commitments and, usually, an implementation partner. There's very little in between, and that gap is exactly where a custom or hybrid approach often wins.

The hidden costs that decide your real TCO

The advertised tier is rarely what you pay. Four line items quietly inflate the total.

Operation / task creep

This is the big one on consumption platforms. Flows multiply, polling triggers fire constantly, and a two-action Zap grows into a six-action workflow. Going over your limit doesn't stop your automations — Zapier, for example, keeps them running and bills overage at roughly 1.25× the base task rate, so you find out after the spend. A flow that "cost £29/month" in the demo can cost £150 in production once real volume hits.

Premium connectors and enterprise endpoints

Many connectors sit behind higher tiers. On platforms like Boomi and Workato, enterprise connectors (SAP, Oracle, Workday) can cost noticeably more than a standard connector — often around 3× — and a single such endpoint can push you up an entire pricing band. Always confirm your specific apps are included before you sign: "1,000+ integrations" rarely means your edge-case API is on the entry plan.

Error reruns and reprocessing

Failed operations often still consume your quota, and re-running a batch of 5,000 records after a fix consumes it again. Robust error handling — retries, dead-letter queues, alerting — is also frequently a premium-tier feature. Poorly built flows that fail and retry can double your consumption invisibly.

Setup, maintenance and the cost of people

This is the cost no pricing page shows. Even a "no-code" iPaaS needs someone to build, test, document and maintain the flows as the underlying APIs change. Budget realistically:

• SME (Zapier/Make): a few days of setup, then ongoing tweaks as you grow. The subscription is usually the smaller cost; the person tending it is the larger one.
• Enterprise (Boomi/Workato/Celigo): total cost of ownership commonly runs to two to three times the licence once implementation and support are counted, and first-year build often matches or exceeds the year-one licence — frequently via a partner.

iPaaS subscription vs custom build: the real comparison

The honest framing isn't "iPaaS vs custom" — it's three cost shapes:

1. iPaaS subscription — low or zero upfront, recurring forever, scales with volume. You rent reliability, connectors and a UI.
2. iPaaS setup cost — the one-off build and configuration of those flows (your own time, or paid implementation).
3. Custom build — higher upfront, then a modest annual maintenance line (commonly ~15–25% of build cost), and no per-task meter. You own the asset. For most UK mid-market integration projects this lands in the region of £8,000–£20,000+, depending on scope — again, indicative, not a quote.

The crossover maths is straightforward. If an enterprise iPaaS will cost £40,000+ a year indefinitely for a handful of stable, well-understood integrations, a custom build at, say, £20,000 once plus a few thousand a year in maintenance can pay back inside two years. If your needs are fluid, low-volume and spread across many SaaS apps, the iPaaS subscription is far cheaper than paying a developer to build and babysit equivalent code.

When iPaaS genuinely beats custom

Choose iPaaS — and don't over-engineer — when:

• The flow is standard and the connectors exist. Shopify → Xero, HubSpot → Salesforce, Stripe → QuickBooks. If a native or iPaaS connector does it well, building custom is wasted money. (See our honest take on Zapier vs Make vs custom.)
• Volume is low to moderate and won't trigger painful task or operation creep.
• You value speed and a UI non-developers can edit, over owning the code.
• Requirements change often — reconfiguring a flow beats re-commissioning a developer.

Lean towards custom when volume is high (per-task pricing punishes you), logic is complex or bespoke, you need strict reliability and audit guarantees, or you're facing five-figure enterprise iPaaS licences for a small, stable set of integrations. Many UK mid-market firms land best on a hybrid: iPaaS for the long tail of simple SaaS flows, custom code for the two or three high-volume, business-critical pipelines.

How to control iPaaS cost

• Model your real volume, not the demo's. Count tasks or operations per business event, multiply by monthly throughput, then add headroom for retries.
• Audit before you scale. Consolidate flows, replace minute-by-minute polling with webhooks, and kill zombie automations.
• Confirm your exact connectors are on the tier you're costing — not a higher one.
• Negotiate annual enterprise deals. Published-equivalent rates on Workato, Boomi and Celigo are starting points; multi-year commitments routinely shave 15–30% off opening quotes.
• Re-run the crossover maths yearly. A subscription that made sense at 5,000 operations a month rarely does at 500,000.

If you're weighing platforms specifically, our iPaaS implementation partner page covers selection and rollout; Services sets out our fixed-price approach.

How APIwise can help

We're vendor-neutral and fixed-price, so we have no incentive to push you onto a platform you don't need. Our Integration Health Check maps your current flows, models your true iPaaS total cost of ownership, and tells you honestly whether to stay on Zapier or Make, move to an enterprise iPaaS, build custom, or run a hybrid — with indicative numbers you can take to your finance team.

If you'd like a clear, jargon-free view of what your integrations should actually cost, get in touch for a fixed-price audit.