Integration Middleware for Mid-Market IT in Amsterdam (2026)

The verdict in three sentences

An integration middleware for a mid-market company costs 30,000 to 90,000 EUR depending on the number of connected systems and the level of orchestration. Its value is not connecting faster, but avoiding the spaghetti of 15 to 30 point-to-point connections that becomes unmanageable and fragile. In 2026, the choice is between iPaaS (Make, n8n, MuleSoft) and custom: iPaaS wins below 8-10 flows, custom beyond that or when governance and volume demand it.

Point-to-point vs middleware: the connection problem

Without middleware, each system connects directly to every other. The number of connections explodes quadratically, multiplying the points of failure.

Beyond 6-7 systems, point-to-point becomes a maintenance nightmare: every API change breaks several connections. Middleware centralizes orchestration and cuts integration incidents by about 50%.

iPaaS vs custom: which choice in 2026

The 2026 market offers mature iPaaS (Make, self-hosted n8n, MuleSoft) and the option of a custom integration bus. Here is the comparison.

The 2026 rule: start with iPaaS (self-hosted n8n is excellent on cost/control), and move to custom only when subscription costs, volume or governance needs exceed what iPaaS offers cleanly.

Mini case study

Julien, IT director of a 320-person industrial mid-market firm in Amsterdam, ran 9 systems (ERP, CRM, WMS, e-commerce, BI, payroll...) linked by 23 point-to-point connections cobbled together over the years. Integration incidents consumed about 1.5 person-days a week in fixes, i.e. around 35,000 EUR a year. He has a custom middleware built for 58,000 EUR, plus 8,700 EUR annual maintenance. Incidents drop 50%, new flows plug in within days rather than weeks, and payback is reached in under 2 years.

FAQ

At how many systems is middleware justified?

Generally beyond 6-7 interconnected systems. Below that, point-to-point or a lightweight iPaaS is enough; beyond it, middleware avoids the quadratic explosion of connections.

Should I start with iPaaS or go straight to custom?

Start with iPaaS (Make or self-hosted n8n): it is faster and cheaper. Move to custom when volume, subscription costs or governance depend on control that iPaaS cannot provide.

Does middleware really reduce incidents?

Yes: by centralizing orchestration and standardizing error handling and replay, a drop of about 50% in integration incidents is commonly observed.

What is the main risk of iPaaS?

Vendor lock-in and cost escalation with volume. Some enterprise iPaaS become very expensive at high traffic, which can justify moving to custom.

How long to deploy a custom middleware?

Expect 10 to 18 weeks depending on the number of flows and orchestration level. A wave-based approach lets you migrate the most critical connections first.

Let's scope your project. Tell us the number of systems to integrate, your flow volume and your governance constraints, and we will frame a scope between 30,000 and 90,000 EUR (or a cheaper iPaaS option if relevant). Detailed quote within 48 h. WhatsApp +221 77 596 93 33.