Definitions: what exactly do we mean?
The terms "API integration", "integration platform" and "middleware" are often used interchangeably in practice. For the rest of this article we use the following definitions so that we can compare like with like.
API integration
A direct point-to-point integration between two software systems via their APIs. One system calls the other's API; the infrastructure in between consists of a thin adapter or integration layer that you build and host yourself. We cover this type of integration in detail on the smart API integrations page.
Integration platform (iPaaS)
A central middleware layer, delivered as SaaS, that connects multiple systems via prebuilt connectors. iPaaS stands for Integration Platform as a Service. Well-known names: Zapier, Make (formerly Integromat), Workato, Boomi, MuleSoft, Tray.io, SnapLogic and Frends. You buy a subscription and build flows in a visual editor or low-code environment.
Middleware (older term)
The term middleware is still used, especially in enterprise settings, for ESB-style products such as webMethods, TIBCO or Talend. Conceptually, an iPaaS sits in the same layer, but cloud-native. A classic ESB often lives on-premises, requires its own operations and needs a product team to maintain the logic; an iPaaS shifts that burden to a SaaS vendor. If you want to know more about when to build an integration layer yourself, our page on building middleware covers the practical side, going deeper into the trade-off between building it yourself, a hybrid approach or fully SaaS.
So what is "API management"?
For completeness: API management is a separate category of tooling (Kong, Apigee, AWS API Gateway, Azure API Management) that secures, throttles and documents your own APIs. It is not an integration layer in the sense of this article; it is the shield around your own APIs. An organisation can have API management, an iPaaS and custom integrations at the same time; they solve different problems.
API integration = you build the integration yourself. iPaaS = you rent a platform that runs the integration for you. Middleware is the umbrella term for the intermediate layer, wherever it runs. API management is about your own APIs, not the integrations between systems.
When do you choose an API integration?
A direct API integration is generally the right choice when the scope is small, the logic is specific, or the requirements for performance, security and control are high. These are the patterns we see most often in teams that opt for custom development:
- A small number of systems. You are connecting two or three systems that work together in a fixed setup, such as an ERP to a web shop or a CRM to marketing automation. The number of flows stays manageable.
- A one-off technical integration. There is no roadmap with thirty integrations; one solid integration is enough and should then simply keep working without someone having to tinker with it all the time.
- Specific business logic. The integration has to do more than map fields: you have rules around the source of truth, conditional transformations or orchestration steps that a visual flow editor cannot handle.
- Performance and volume. You process hundreds or thousands of events per minute. iPaaS platforms charge per operation and can become expensive at peak volume; a custom integration has a fixed run cost.
- Security requirement: no data via a third party. In regulated industries (healthcare, finance, government), the business owner sometimes explicitly wants customer data not to pass through an external SaaS. A custom integration on your own infrastructure avoids that.
- Limited budget for subscriptions. A one-off build budget is sometimes easier to justify than an ongoing iPaaS subscription that scales per user or per task.
- Your own developer team is available. You have people who can take over maintenance, investigate log failures and roll out API version updates when SaaS vendors change their contracts.
In these scenarios, a custom integration is almost always technically more elegant and financially more attractive in the long run. The downside: you invest once in design and build, and you are yourself responsible for monitoring, retry strategy and API updates of the connected systems. That last point is often underestimated: a SaaS vendor may announce a breaking change in its API only a few months ahead, and you then have to plan time to move your integration along with it. If you want to weigh this up in detail for one specific integration, we have described our experience with point-to-point integrations on the page about smart API integrations.
When do you choose an integration platform?
An iPaaS is preferable as soon as the number of integrations grows, or as soon as non-developers need to be able to adjust flows. The typical triggers:
- Five or more systems. Beyond that number, point-to-point integrations become exponentially more expensive to maintain. A central hub reduces the number of integrations from O(n²) to O(n).
- Many different integrations over time. Marketing regularly adds a tool, finance switches invoicing software, sales adopts a new enrichment vendor. An iPaaS makes connecting new systems cheap and fast.
- Non-developers need to adjust flows. An operations colleague who can add a field to a Zapier zap themselves saves a ticket a week. For business-owned automation, iPaaS is strong.
- Fast time-to-market. A proof of concept on an iPaaS can be up and running within a few working days, whereas a custom integration quickly takes several sprints.
- Plenty of standard SaaS in your stack. For Salesforce, HubSpot, Slack, Stripe, Shopify, NetSuite and hundreds of other mainstream tools, ready-made connectors are available. You no longer build an API client — you pick a trigger and an action.
- Multi-tenant context. SaaS vendors that need to deliver the same pattern for hundreds of customers can scale faster on an iPaaS foundation than with custom integration code for each customer.
What you give up: vendor lock-in on the iPaaS platform, ongoing subscription costs and a ceiling on complexity. What a visual flow editor can't do often requires a "callout" to an external function — and then you're technically back in custom territory, at least in part. An iPaaS also adds an extra link to your data path: outages on the platform's side hit all your flows at once, and debugging often runs through a vendor portal rather than your own logs. That's not a blocker, but it is something to factor explicitly into your architecture choice.
The hidden costs of an iPaaS
Besides the subscription, there are three cost items that are often missing from quotes: licences for premium connectors (Salesforce, NetSuite and SAP usually charge a surcharge), training for your operations team so they can read the flows, and designing your own "connector strategy" once several teams start building their own zaps. That last one is not a technical problem but a governance problem: without clear agreements, you end up with hundreds of undocumented flows that nobody dares to switch off.
Cost comparison: what shifts?
We deliberately leave out figures here — they depend heavily on your scope, your provider and your volume. What we can do is lay the cost structures side by side, so you can run the numbers for your own scenario.
| Cost item | API integration (custom) | Integration platform (iPaaS) |
|---|---|---|
| Initial | One-off design and build costs | Onboarding and setup, often in days |
| Ongoing | Hosting + maintenance + monitoring | Subscription per task / operation / connector |
| Scaling points | Fixed run cost; peak volume costs little extra | Costs scale linearly or per task with volume |
| Adding integration no. 2 | Comparable scope, development costs again | Often just an extra connector fee |
| API version update | Your own responsibility | Included in the subscription |
As a rule, the break-even point lies somewhere around five to ten integrations. Below that, a direct API integration is usually cheaper; above it, a platform pays off because the number of integrations grows faster than the subscription costs.
When calculating the iPaaS cost, don't forget to base the task price on your peak volume, not your average. Many teams are caught out by a double-cost month after a marketing campaign or seasonal peak.
Three real-world scenarios
Scenario 1 — Mid-market: HubSpot + Shopify + Loket + Slack
A growing mid-market company wants to connect lead flow, e-commerce, payroll and internal communication. Four mainstream SaaS products with good public connectors. Here an iPaaS (Zapier, Make or n8n) is a logical start: quick to go live, low initial investment, and non-developers can adjust flows. As volume grows, an upgrade to a mid-market iPaaS (Workato, Tray.io, Frends) can make sense. The big win isn't in the first integration but in the sixth or seventh: marketing wants to connect a review tool, finance wants to automate accounts receivable, and operations can build those integrations themselves without raising a developer ticket every time.
Scenario 2 — Enterprise: 50+ systems with complex business logic
A large organisation with a legacy ERP, its own data warehouse, multiple CRMs after a merger and strict audit requirements. This is where an enterprise iPaaS (MuleSoft, Boomi, SnapLogic) comes into play, possibly combined with a custom integration platform layer. We have described this type of architecture on our page about enterprise software development: governance, observability and standard patterns carry more weight there than time-to-market.
Scenario 3: Custom Bullhorn ↔ Exact integration with complex rules
A staffing company wants to integrate its ATS (Bullhorn) with its accounting software (Exact). It sounds simple, but there is a thick layer of business logic in between: which field is the source of truth in the event of a conflict, how do you handle contracts that are later reversed, what do you do with duplicate candidate records, and how do you process a correction entry when a week that was already invoiced is subsequently undone? Here an iPaaS loses out to a custom integration, because the business rules don't fit in a visual flow editor and because the audit trail the accountant wants to see has specific formatting requirements. This is exactly the type of work where our experience with integrations between business systems makes the difference: the integration itself isn't the real work, the business logic on top of it is.
Hybrid is usually the answer
In practice, we rarely see an organisation settle entirely on one model. Most mature integration landscapes opt for a mix: an iPaaS for the bulk of standard flows, and custom API integrations for the specific cases where the iPaaS platform falls short.
- iPaaS for 70 to 80 per cent of standard flows. Lead routing, notifications, simple field syncs, escalations. Quick to build, easy to explain, cheap to maintain.
- Custom API integration for the 20 to 30 per cent that is specific and complex. Master data management, critical real-time flows, high-volume transactions or regulated data flows.
- Your own integration layer as orchestrator. A thin, custom middleware layer on top of your iPaaS and your custom integrations that contains the business logic, provides an audit trail and gives you an escape route if you ever want to switch iPaaS vendors.
This "best-of-both" model is not a compromise but a deliberate architectural choice. The crux is where you draw the line, and that line also shifts as your stack matures.
iPaaS market overview (brief and neutral)
The iPaaS market has grown considerably over ten years and has since become segmented. A rough breakdown, without preference:
Low-end and no-code
- Zapier: market leader in long-tail connectors, ideal for proofs of concept and business-owned automation.
- Make (formerly Integromat): visually stronger than Zapier, well suited to more complex flows without developer skills.
- n8n: open-source, self-hostable alternative, popular with teams that want to keep control of their data.
- Pipedream: code-first with visual components, popular with developers who want to prototype quickly.
Mid-market
- Workato: strong in HR and finance, with advanced governance.
- Tray.io: flexible, with good API management.
- Frends: Finnish platform with a strong position in the Netherlands and the DACH region, strong in its low-code and pro-code combination.
Enterprise
- MuleSoft: part of Salesforce, strong in API management and governance.
- Boomi: pure-play iPaaS with a broad connector library.
- SnapLogic: strong in data integration and AI-augmented flow design.
- Software AG webMethods: heir to the classic ESB, popular in heavy industry and government.
- Workato Enterprise: Workato's enterprise tier with dedicated governance and compliance features.
ETL and reverse ETL (data layer)
- Fivetran: managed data pipelines to your warehouse.
- Airbyte: open-source alternative, modular and self-hostable.
- Hightouch: reverse ETL: pushes data from your warehouse back into operational tools.
This list is not exhaustive and changes quickly: vendors merge, pricing models change and positions shift. What remains true is that there is a real difference between "I want to connect two tools" and "I want an integration strategy for an entire organisation", and the right vendor is rarely in another segment.
How we advise on the choice
When clients ask us for advice on integration strategy, we generally work through six steps before making a recommendation. Depending on the scope, this usually takes a programme of several sprints:
- Inventory of current and expected integrations. Which systems are in place now, which are on the roadmap, and which are being phased out? This step often already brings to light a number of "shadow integrations" that nobody officially knows about, such as Excel exports that someone emails every week.
- Volume calculation. How many events per minute does each integration process at peak and at average load? This figure determines the cost model of iPaaS vendors.
- Compliance requirements. GDPR, sector-specific regulations (NEN 7510 for healthcare, DNB guidelines for finance), data residency and any requirements around audit logging. For some organisations, an iPaaS vendor that does not host your data in the EU is ruled out immediately.
- Team capabilities assessment. Do you have an in-house dev team that can build and maintain API integrations itself, or do you depend on a partner? For organisations without their own dev capacity, iPaaS is almost always the starting point.
- Three-year roadmap fit. Which direction is the organisation heading? An acquisition strategy means integrating many different stacks, which suits iPaaS well. A specialisation strategy with deep vertical software is a better fit for custom development.
- Migration path if iPaaS becomes necessary later. If you start with custom integrations, it pays to build a thin abstraction layer up front, so you can switch to an iPaaS later without having to touch your applications again.
The outcome is not one-size-fits-all advice. It is a well-founded choice that fits your organisation, your stack and your roadmap, and it refers explicitly back to the six points above, so that in a few years' time you can still check why you chose model A or B. If you want to browse the wider knowledge base for related topics, our knowledge base overview page has further articles on integration, architecture and software strategy.
Frequently asked questions
What is the practical difference between API integration and an integration platform?
An API integration is a direct, often custom-built integration between two systems via their APIs. An integration platform (iPaaS) is a central SaaS layer that connects multiple systems through prebuilt connectors. The first is custom and single-purpose; the second is platform software on which you assemble flows yourself.
Which iPaaS platforms are popular in the Netherlands?
In the Dutch mid-market, we see Zapier and Make for lighter use cases, Workato and Tray.io for more serious business flows, and Frends is gaining ground. In an enterprise context, MuleSoft, Boomi and SnapLogic dominate, with webMethods still strongly present in legacy environments. For data pipelines, Fivetran is the de facto choice in the Netherlands.
iPaaS subscription or building in-house: which is cheaper?
Below five integrations, building in-house is generally cheaper; above that, the balance tips towards iPaaS. The break-even point depends on your volume and your maintenance costs, not just on the initial budget. Calculate the subscription based on your peak volume rather than your average, as that is the most common miscalculation.
Can a company without its own dev team use an integration platform?
Yes, that is in fact one of the strengths of iPaaS. Tools such as Zapier and Make are built for non-developers, and even mid-market platforms such as Workato deliver good results with an operations team that can think in terms of flows. For more complex integrations, a partner or consultant is still recommended, even if you manage the flows yourself.
When should you migrate from iPaaS to custom?
The typical triggers are costs that outgrow your volume, flows that become too complex for the visual editor, or a compliance requirement that rules out external processing. It is rarely a big-bang migration; usually a handful of critical flows move to custom builds while the rest stays on iPaaS.
What about GDPR when using an iPaaS vendor?
Under the GDPR, an iPaaS vendor is a processor, so you need to sign a data processing agreement. Key things to check up front: where the servers are located, which sub-processors are used, how long data is retained, and whether an EU-only tier is available. For special category personal data (healthcare, sensitive profiles), it pays to go through each data flow with a privacy officer to establish whether processing via an external SaaS fits within your record of processing activities at all.