An integration platform moves records between the systems you already bought, and is judged on the day a connector fails halfway through a run.
This guide ranks on error handling, replay and idempotency rather than connector counts. n8n sits in our robotic process automation guide rather than here, because it is bought as a workflow engine and priced like one.
AuthorHannah ReiterSenior Analyst, Business Applications
Vendors can pay for visibility on this page. It never changes what an entry
says about a product, including the criticism, and we earn nothing when you click through to a
vendor. How that works.
In short
What integration platform software does
An integration platform connects applications and data sources, transforms the records passing between them, and runs those flows on a schedule or in response to events.
Five things, in this order. Feature counts are not among them: they are the least useful
comparison in software, because every vendor ticks every box.
01
Setup effort in integration platform software
What the first ninety days of a integration platform software rollout cost in hours, not in licence fees. A product that needs a partner engagement before it does anything is a different purchase from one a team configures in an afternoon.
02
What integration platform software really costs
What the bill becomes once the modules a normal buyer of integration platform software needs are added, and whether you can read that number without a sales conversation.
03
Getting your data out of integration platform software
How your own data comes back out, in what format, and whether that export is included in the integration platform software contract or billed as a project.
04
Independence from the vendor
Whether you can buy integration platform software, run it and leave it on your own terms. This test decides most of the order on this page, and it is why the largest vendors in integration platform software often sit below the smaller ones.
05
Who the product is built for
The size and shape of company each integration platform software product was actually built for. Most regret in software comes from buying for a company you are not yet.
The fourth test decides most of the order on this page, and it is the reason the largest
integration platform software vendors sit below the smaller ones. A product with a published price, an export
that works and no mandatory implementation partner is a product you can leave.
A platform suite that arrives with a quote, a partner and a two-year commitment may well be
the better software and is still the harder decision to reverse. We rank integration platform software for the
buyer who has to live with that decision without a procurement department, which is a stated
bias rather than a hidden one.
We do not publish a score out of ten. A number like 8.4 is a judgement dressed as a
measurement, and nobody can check it.
What you can check is on this page: what each integration platform tool costs, where the vendor is
established, whether the price is published, and what we think it is bad at. Our full method
is on the how we work page.
Consumption-based on messages and connections, quoted
—
Organisations running SAP that must integrate with everything else
Estates with no SAP system at either end
Country is where the vendor is headquartered or contracts from, which is a
different question from where your data is hosted. Where the two tell different stories, the
entry says so.
Open source workflow engine where every step is real code
Ranked #1 of 12 in Best Integration Platform in 2026.
Open sourceSelf-hostablePublished pricingEurope
Windmill treats a flow as versioned code with a scheduler, retries, suspend-and-resume and approval steps around it, self-hosted if you want. Nothing is trapped: the scripts run anywhere Python or TypeScript runs.
The price of that independence is that every integration begins with reading an API document and handling the authentication yourself, so the time-to-first-flow is days rather than the afternoon Zapier or Make would take.
What stands out
Open source
Self-hostable
Code-first
Where it costs you
No connector catalogue; authentication is your work
Business users cannot build in it unaided
Right for
Engineering teams that want orchestration without giving up their code
Wrong for
Business teams connecting SaaS tools without developers
FranceOpen source self-hosted; cloud per seat and per compute, published
Visual scenarios priced by the operation, not the task
Ranked #2 of 12 in Best Integration Platform in 2026.
Free tierPublished pricingElsewhere
Make's canvas makes control flow visible, including the error routes that other tools hide in a settings panel, and per-operation pricing is published so the cost can be estimated in advance.
The counting is the part buyers get wrong: a scenario with eight modules processing two hundred records spends sixteen hundred operations per run. At real volumes the bill overtakes tools that looked more expensive per month.
What stands out
Visual builder
Published price
Operation meter
Where it costs you
Operations are consumed per module per iteration
Large scenarios become hard to read on the canvas
Right for
Operations teams building visible, branching automations at moderate volume
Wrong for
High-volume record synchronisation between core systems
Czech RepublicPer operation per month, published; free tier
Dutch iPaaS built around commerce, ERP and middleware hygiene
Ranked #3 of 12 in Best Integration Platform in 2026.
Pricing on requestEurope
Alumio was designed for the integration problem European commerce actually has: several systems of record that each believe they own the product data.
Its logging, retry and replay behaviour is built for that daily reality rather than demonstrated once in a sales deck, and Dutch hosting settles residency. Expect a quoted price, a partner-led implementation and a connector list that assumes your systems are commerce systems.
What stands out
Dutch hosting
Commerce focus
Error logging
Where it costs you
Pricing is quoted and usually partner-led
Connector coverage is narrow outside commerce and ERP
Right for
European commerce estates joining a shop, ERP, PIM and warehouse
Wrong for
Small teams wanting a published price and a self-serve start
NetherlandsSubscription quoted per environment and data volume
Finnish integration platform that runs agents wherever you need
Ranked #4 of 12 in Best Integration Platform in 2026.
Self-hostablePricing on requestEurope
Frends puts the execution agent where the data is, including inside a factory or a municipal network, while the design and monitoring stay central.
That hybrid model is the reason it wins deals that cloud-only tools cannot touch, and the process monitoring genuinely helps during an incident. It is traditional middleware in feel and in buying process: quoted pricing, trained developers, and a vendor relationship rather than a community.
What stands out
Finnish company
Hybrid deployment
Process monitoring
Where it costs you
Everything is quoted, with no self-serve entry
Community and third-party help are thin outside the Nordics
Right for
Nordic public sector and manufacturers with on-premises systems
Wrong for
Teams wanting to start today on a published price
FinlandQuoted per environment; cloud or on-premises agents
White-label integration layer that ships inside your own product
Ranked #5 of 12 in Best Integration Platform in 2026.
Self-hostablePricing on requestEurope
elastic.io exists so a software company can offer its customers integrations without building an integration platform first, with the runtime hosted in Germany or on the vendor's own infrastructure.
The connector tooling is open enough to extend. It is not sold at internal IT departments and does not suit them, and because pricing is a platform licence rather than a subscription, the evaluation starts with a sales conversation.
What stands out
Embedded iPaaS
German hosting
White label
Where it costs you
Wrong shape for internal IT integration work
New connectors require development, not configuration
Right for
Software vendors embedding customer integrations inside their own product
Wrong for
Internal teams connecting the applications they have bought
GermanyQuoted; licensed per platform, on-premises option
Embedded integration marketplace for SaaS companies to resell
Ranked #6 of 12 in Best Integration Platform in 2026.
Pricing on requestEurope
Cyclr gives a product company a working integration marketplace in weeks instead of the year it would take to build one, with maintained connectors and templates that your customers configure themselves.
The commercial terms follow that model, quoted per embedded application. When a connector needs behaviour outside the standard template you are dependent on Cyclr's roadmap, and the failure experience your customers see is only as good as the surface you expose.
What stands out
Embedded iPaaS
UK company
Connector library
Where it costs you
Deep connector customisation goes back to the vendor
Quoted commercial model aimed at product companies
Right for
SaaS vendors needing an integration marketplace in their product quickly
Wrong for
Internal integration projects between systems you bought
United KingdomQuoted per embedded application and connector set
The widest connector list, priced per task executed
Ranked #7 of 12 in Best Integration Platform in 2026.
Free tierPublished pricingNorth America
Zapier's connector list is the broadest anywhere, so the obscure application your marketing team bought is already supported, and a working automation takes an afternoon without a developer. That is genuinely valuable.
What it is not is reliable plumbing: failures land in a history view that nobody watches, replay is a manual exercise, and at volume the per-task price makes it the most expensive option here.
What stands out
Widest connectors
Published price
Task meter
Where it costs you
Replaying a failed batch is largely manual
The task meter punishes any high-volume flow
Right for
Business users connecting SaaS tools without involving IT
Wrong for
Core system integrations that must not silently drop records
United StatesPer task per month, published; free tier
Prebuilt integration apps between the usual commerce and finance systems
Ranked #8 of 12 in Best Integration Platform in 2026.
Pricing on requestNorth America
Celigo's integration apps encode the field mappings, edge cases and error queues that a team would otherwise discover over three painful months, which is why NetSuite-centred finance teams keep choosing it.
Errors surface in a dashboard built for accountants rather than engineers. Away from those well-travelled routes you are configuring a normal iPaaS at an enterprise price, and the meter counts flows and endpoints in ways that surprise people at renewal.
What stands out
Prebuilt flows
NetSuite focus
Error dashboard
Where it costs you
Value drops sharply outside its prebuilt routes
Flow and endpoint pricing is easy to misjudge
Right for
Finance and commerce teams on NetSuite, Shopify or the marketplaces
Wrong for
Unusual system pairs with no prebuilt integration app
Enterprise automation with recipes business teams can read
Ranked #9 of 12 in Best Integration Platform in 2026.
Pricing on requestNorth America
Workato sits between business users and engineering: recipes read like sentences, the governance and audit trail survive a security review, and the deep connectors into Salesforce, NetSuite and Workday handle the awkward objects.
It is priced accordingly. The uncomfortable part is that the licence shapes the design, because building ten small readable recipes can cost more than one large one nobody can follow.
What stands out
Recipe model
Governance controls
Quoted price
Where it costs you
Expensive, and quoted per recipe and connection
Splitting logic into clear recipes can raise the price
Right for
Enterprises wanting business-readable automation under IT governance
Wrong for
Companies whose integration budget is measured in hundreds
United StatesPer recipe and per connection, quoted
Long-running iPaaS with a runtime you can host yourself
Ranked #10 of 12 in Best Integration Platform in 2026.
Pricing on requestNorth America
Boomi's Atom runtime running inside your own network is the reason it persists in manufacturing, healthcare and government where the database cannot be exposed. Two decades of enterprise deployments mean few surprises.
The cost model is the friction: connection-based pricing turns every new system into a commercial conversation, and the tooling assumes a trained integration developer, so the platform is only as good as the person you hire to run it.
What stands out
Atom runtime
Hybrid deployment
Connection meter
Where it costs you
Each new endpoint is a pricing negotiation
Interface and developer experience show their age
Right for
Hybrid estates with systems that will never be internet-facing
Wrong for
Small teams or business users building their own flows
API-led integration for organisations that staff a platform team
Ranked #11 of 12 in Best Integration Platform in 2026.
Pricing on requestNorth America
MuleSoft answers a bigger question than integration: it manages APIs as products, with policies, versioning, a portal and a runtime you can deploy on your own Kubernetes. Organisations that need that governance get it.
Everyone else pays capacity-based pricing and specialist salaries to move records between two systems, which is why MuleSoft projects are the ones most often cited as costing several times their original estimate.
What stands out
API management
Salesforce owned
Capacity meter
Where it costs you
vCore capacity pricing is the most expensive model here
Needs specialist developers on staff or on contract
Right for
Banks and large enterprises building reusable APIs under governance
Wrong for
Point-to-point integration between a handful of applications
The integration layer that comes with an SAP landscape
Ranked #12 of 12 in Best Integration Platform in 2026.
Pricing on requestEurope
When SAP sits at one end of the pipe, having SAP at the other end of the tooling removes a class of problem: prebuilt flows, supported upgrade paths and EU hosting options.
The prebuilt content library is the real asset. Outside that landscape there is no reason to choose it, the consumption meter is hard to predict before running real volume, and the skills cost what SAP skills always cost.
What stands out
SAP landscape
German company
Prebuilt content
Where it costs you
Only makes sense inside an SAP landscape
Consumption pricing resists forecasting
Right for
Organisations running SAP that must integrate with everything else
Wrong for
Estates with no SAP system at either end
GermanyConsumption-based on messages and connections, quoted
An integration platform connects applications and data sources, transforms the records passing between them, and runs those flows on a schedule or in response to events. The differences that matter are rarely in the feature list, so this is
the order we would work through them.
01
Decide whether you need a published price
3 of the 12 tools here publish what they cost; the other 9 quote per organisation, which means a sales conversation before you can compare anything. If you are buying without a procurement function, start with the ones that publish: Windmill, Make, Zapier.
02
Work out what the first ninety days cost in time
Licence cost is the number in the contract; setup effort is the number that surprises people. Ask every shortlisted vendor who does the configuration, how long it took the last customer of your size, and what happens if that person leaves halfway.
03
Check the exit before the entry
Ask for an export of your own data in a format you can open, and ask whether it is included or billed as a project. A vendor that hesitates here is telling you what renewal negotiations will feel like in three years.
04
Match the tool to the size you are, not the size you plan to be
Most regret in this category comes from buying for a headcount that never arrived. The entry-level products here are not worse; they are aimed at a different company.
05
Decide how much the jurisdiction matters
These 12 vendors are established in 7 countries across 3 regions (Europe 6, North America 5, Elsewhere 1). Where a vendor is established decides which government can compel access to what it holds, which is a different question from where the servers are. For most buyers that is a factor, not a veto.
06
Consider whether you want the source
1 of these are open source, which means you can host them yourself and read what they do with your data. That control is real, and so is the maintenance it hands you.
Three different products are sold under one name
iPaaS, embedded integration and a workflow tool solve different problems, and buying across the boundary is the most common mistake in this market. An iPaaS connects the systems your company runs: Boomi, Celigo, Workato and Alumio are this. Embedded integration puts connectors inside a product you sell to your own customers, which is what Cyclr and elastic.io do, and no amount of configuration turns an internal iPaaS into that.
A workflow tool automates a process a person would otherwise do by hand, which is where Zapier, Make and Windmill live, and it becomes a liability when used as the transport for core records. The test is the record, not the feature list: if losing a message means an invoice is never raised, you are buying an iPaaS, whatever the demo showed you.
Decide whether the customer of this integration is internal or your own users.
Ask whether a lost record would be noticed the same day, or at the audit.
Do not buy embedded integration for internal projects, or the reverse.
What happens when a connector breaks mid-run
Every demo runs the happy path. The question that decides this purchase is what the platform does when the target system returns a timeout on record four hundred of a thousand. Four things matter: does it retry with a sensible backoff, does the failed record land in a dead letter queue rather than vanish, can you replay that queue after the other system recovers, and can you replay it without creating duplicates.
Alumio and Celigo build their interfaces around error queues; Zapier logs the failure and largely leaves the replay to you. Make the vendor demonstrate this during the trial with the target system switched off, and watch what the console shows you an hour later. If they will not do that demonstration, you have your answer.
Ask the vendor to kill a target system mid-run during the trial.
Check the failed records are queued and replayable, not just logged.
Confirm who gets notified on failure, and through which channel.
Idempotency is your job, not the platform's
Retries and replays only help if running the same record twice is harmless, and by default it rarely is: a retried order becomes two orders, a replayed invoice becomes a duplicate in the ledger. Platforms cannot fix this for you because only you know what makes a record the same record.
The work is choosing a stable business key, storing what has been processed, and making every write an upsert rather than a create. Windmill gives you the code to do it properly; Workato and Boomi have patterns for it but will happily let you build the flow without one. Nobody raises this in a sales meeting, and it is the single most common reason an integration project produces duplicate data in its first month.
Name the business key for every object you synchronise, before building.
Make writes upserts, not creates, wherever the target system allows it.
Test by running the same batch twice and counting the records afterwards.
The meter, and why connector counts do not matter
Vendors compete on connector numbers because they are easy to print, but nobody uses a thousand connectors; a typical estate has six systems and three that matter. What varies enormously is the meter. Zapier charges per task, Make per operation — which counts every module in every loop iteration — Boomi per connection, MuleSoft by vCore capacity, and Workato per recipe and connection.
Take one real flow, count how many records pass through it in a month, and price that same flow on each model. The differences run to an order of magnitude, and the cheap-looking per-month plan is often the expensive one at your volume. Ask what happens in the month a supplier sends a full catalogue refresh instead of a delta, because that month arrives every year.
Price one real flow at real volume on each vendor's meter, not the plan chart.
Ask what a full resynchronisation of your largest data set would cost.
Check that the six connectors you actually need are the maintained ones.
What goes wrong most often when buying integration platform software
Choosing on connector count. You will use six of them, and the one you need most will be the shallow one.
Using a per-task workflow tool as the transport for core financial records. It is not built to guarantee delivery, and the bill grows with volume.
Accepting a demo that never shows a failure. Ask for the target system to be switched off mid-run, and watch what the console says afterwards.
Leaving idempotency until after go-live. The duplicates arrive in week one, and cleaning them up costs more than designing the key would have.
07
Frequently asked questions
11 answers
What is the best integration platform in 2026?
Windmill leads our ranking of 12. Scripts in Python, TypeScript, Go or SQL become steps in a flow with retries, suspend and resume, and an approval step, all versioned in Git and runnable on your own machines.
The exit is complete because the logic is code you already own. It is not a connector catalogue: authentication to each SaaS system is your problem, and a business analyst will not build anything here alone.
How did you rank these integration platform tools?
On what separates products after the demo: how much setup the first ninety days take, what the price becomes once the modules a normal buyer needs are added, how your data comes back out, whether you can buy and leave it without a partner engagement, and who the product is genuinely for.
That fourth test is why the large platform suites usually sit lower here than their market share would suggest. Not on feature counts, and not on a score we invented.
Which integration platform tools publish their pricing?
3 of the 12, with the pricing model each one publishes:
Windmill: Open source self-hosted; cloud per seat and per compute, published.
Make: Per operation per month, published; free tier.
Zapier: Per task per month, published; free tier.
The other 9 quote per organisation.
Is there a free integration platform tool?
Make, Zapier offer a free tier or a free self-hosted edition. Read what the free tier excludes before you plan around it.
Which integration platform tools are open source?
Windmill. Open source means you can read what the product does with your data and run it yourself. It does not mean the hosted edition is free.
Which integration platform tools can you host yourself?
Windmill, Frends, elastic.io. The other 9 are sold as a hosted service only, which means the question of where your data sits is answered by the vendor, not by you.
Where are these integration platform vendors established?
In 7 countries across 3 regions: Europe 6, North America 5, Elsewhere 1.
Windmill is established in France.
Make is established in Czech Republic.
Alumio is established in the Netherlands.
Frends is established in Finland.
elastic.io is established in Germany.
Cyclr is established in the United Kingdom.
Zapier is established in the United States.
Celigo is established in the United States.
Workato is established in the United States.
Boomi is established in the United States.
MuleSoft Anypoint is established in the United States.
SAP Integration Suite is established in Germany.
Establishment decides whose courts and whose disclosure laws apply, which is a separate question from where the data is hosted.
What should you use instead of Windmill?
Make and Alumio are the next two on this page. Make is for Operations teams building visible, branching automations at moderate volume; Alumio is for European commerce estates joining a shop, ERP, PIM and warehouse.
All 12 are ranked here with what each one is bad at.
Who should not buy Windmill?
Business teams connecting SaaS tools without developers. No connector catalogue; authentication is your work.
Do you get paid for these rankings?
Vendors can pay for visibility, which affects where and how prominently a product appears. It does not change a word of what the entry says about that product, including the criticism, and it cannot buy inclusion for something that does not belong in the category.
We take no commission when you click through to a vendor and we do not know whether you bought anything. The full arrangement is on our disclosure page.
How often is this integration platform guide updated?
Whenever the facts move: a price change, an acquisition, a product that stops being maintained. The published and updated dates at the top of the page are real, and a review means someone went back to the vendor documentation rather than bumping a date.
These 12 products are the ones we judged worth ranking in integration platform. If yours belongs here and is missing, tell us what it does and who it is for, and we will look at it. Inclusion is an editorial call and it is not for sale — but nobody gets considered for a list they were never put in front of.
People land on this page with a shortlist to make, not a browsing habit to feed. That is a narrower audience than a banner reaches and a far more decided one.
Written by us, about you
We describe the product in our own words, say who it suits and say who it does not. A vendor never writes the entry and never sees it before it goes up.
A correction costs nothing
If a fact about your product is wrong here, tell us and we fix it, whether or not there is any money between us. That offer is older than any commercial arrangement on this site.
Placement is separate, and disclosed
Where a product sits in the ranking can be paid for, and the notice above the list says so on every page. What the entry says about the product is not for sale at any price.
We use analytics cookies only if you agree. See our privacy policy.
