What Does an Integration Platform (iPaaS) Cost?
An integration platform (iPaaS) costs anywhere from a few hundred kronor a month for simple automation tools to SEK 30,000–100,000 a month for enterprise platforms. The alternative, custom-built integrations, typically costs SEK 100,000–500,000 per connection. The platform usually pays off as the number of flows grows, but license fees, volume caps, and lock-in need to factor into the math.
As the number of integrations grows, the question comes to a head: should every connection be built separately, or should an integration layer be bought as a service? An iPaaS – Integration Platform as a Service – trades development cost for license cost. Whether that’s a good deal depends almost entirely on how many flows you have and where they’re headed.
License tiers: from a few hundred kronor to six figures a year
Price lists change over time, but the orders of magnitude hold steady:
| Tier | Approximate cost | Fits |
|---|---|---|
| Simple automation tools (e.g. Zapier, Make) | Around SEK 200–2,000/month | A handful of flows between standard apps, low volume |
| Dedicated iPaaS services | Around SEK 5,000–30,000/month | Multiple flows, higher volumes, error handling and support |
| Enterprise platforms | SEK 30,000–100,000+/month | Many systems, governance, high volumes and compliance requirements |
Pricing is almost always volume-based – number of flows, runs, or “tasks” per month. That means the cost grows with usage: the platform that was cheap at a thousand runs a month can become a significant line item at a million.
The comparison: custom-built integration
The alternative is to build the integrations as custom code. A custom point-to-point integration typically costs SEK 100,000–500,000 to build, plus an ongoing maintenance line item of typically 10–20% of the build cost per year. No monthly license, no volume caps, and full control – but every new flow is a new development project, and you have to handle monitoring and error handling yourself.
Breakeven: count in flows and volume
A simplified but useful way to compare is total cost over three years.
Scenario A – two stable flows. Custom-built: two integrations at SEK 200,000 each plus maintenance comes to around SEK 520,000 over three years. A mid-tier platform: SEK 10,000 a month plus configuration work of, say, SEK 80,000 comes to around SEK 440,000. Roughly even – and if high volume pushes up the license tier, custom-built wins.
Scenario B – ten changing flows. Custom-built: even with reuse, roughly SEK 1.5–2.5 million plus growing maintenance. Platform: the same monthly license covers every flow, and new connections are configured in days instead of developed in weeks. Here the platform wins clearly.
The rule of thumb: few, stable, high-volume flows favor custom-built – many, changing flows between standard systems favor a platform. Volume can flip the math the other way, though, since the license scales with usage but the cost of a custom build doesn’t.
Lock-in and exit cost belong in the math
What rarely shows up on the price list: flows built inside a platform don’t come with you. The logic is expressed in the platform’s tooling, and an exit means every integration gets rebuilt from scratch. The exit cost is therefore roughly the same as building the equivalent integrations new – and it belongs in the total math, weighted by the likelihood you’ll ever want to switch.
The risk can be limited with a simple principle: keep business logic in your own systems and APIs, and let the platform handle transport and mapping. That keeps the flows thin and cheap to recreate elsewhere.
How to choose
Start from the need, not the tool. List the flows you have and the ones you see coming within two years, with volumes. If the list is short and stable: build. If it’s long and shifting: evaluate platforms against the actual list, including volume caps and exit. And remember the hybrid path – platform for the standard flows, custom code for the critical ones – which is often the most economical overall approach.
Four questions to ask during evaluation:
- What does the tier we need cost if volume grows tenfold?
- Are there ready-made connectors for our specific systems – at the license tier we plan to pay for?
- How do we troubleshoot a flow that stalls in the middle of the night, and who gets alerted?
- What does it cost to leave – and have we kept the logic outside the platform so it stays cheap?
The answers separate the platforms far more than their homepages do. At Weapp we’re happy to help with that analysis as part of our work with integrations and automation. Want to talk through your integration map? Get in touch.
Frequently asked questions
What is an iPaaS?
iPaaS stands for Integration Platform as a Service – a cloud service where integrations are built with ready-made connectors and visual flows instead of custom code. The platform handles operations, monitoring, and scaling, and new flows between common systems can be set up in hours instead of weeks.
Is Zapier enough for a business?
For simpler flows between standard systems, yes – many businesses automate leads, notifications, and document handling that way at low cost. The limit is hit at volume, complex business logic, and requirements for error handling or compliance. Once flows become business-critical, a heavier platform or a custom integration usually takes over.
How are integration platforms priced?
The most common model is a combination of tiered monthly licensing and volume – number of flows, runs, or so-called tasks per month. The price steps up with more connectors, higher volume, and features like advanced error handling and environment management. Read the pricing model carefully: the volume cap is what most often catches people off guard.
What happens if we want to leave the platform?
The flows are built inside the platform's tooling and don't come with you – an exit means the integrations have to be rebuilt, either on another platform or as custom code. So factor in the exit cost when you first choose a platform, and reduce the risk by keeping business logic in your own services and letting the platform just handle transport.
Can you combine a platform with custom-built integrations?
Yes, and in practice it's the most common setup. Standard flows between well-known systems go on the platform, while business-critical or high-volume connections are built as custom services. The combination gives you the platform's speed where it's enough and full control where you need it.