TL;DR
- "Cloud integration platform" covers three different deployment models: cloud-only, hybrid (a cloud control plane with a runtime agent in your network), and fully on-premise or self-hosted.
- Zapier, Make, and Tray.ai are cloud-only. Boomi, MuleSoft, SnapLogic, Azure Logic Apps, and Koodisi offer real on-premise options. Workato's on-premise agent still depends on Workato's cloud.
- Settle the deployment model before comparing features or price. It's the one requirement you usually can't negotiate.
A cloud integration platform is an integration platform as a service (iPaaS) that connects applications, data, and APIs from infrastructure the vendor runs. In practice the label covers very different architectures. Some platforms are cloud-only with no exceptions, some run a hybrid model with an agent inside your network, and a few can run entirely on infrastructure you control. That deployment model, more than any feature, decides whether a platform is usable for a regulated team.
This guide compares how today's main cloud integration platforms deploy, what "hybrid" and "on-premise" really mean, and what to ask before you shortlist one. If you're looking for the data side of the topic, start with what cloud data integration is.
Cloud, hybrid, and on-premise: what each model means
- Cloud-only: the vendor runs everything. Your systems connect to the vendor's cloud over the internet. Nothing is installed in your network.
- Hybrid: design, management, and monitoring stay in the vendor's cloud, while a runtime agent inside your network executes integrations and reaches private systems. Data can stay inside your network, but the agent usually needs a connection back to the vendor.
- On-premise or self-hosted: the runtime, and sometimes the whole platform, runs on infrastructure you control, so it keeps working without the vendor's cloud.
Cloud integration platforms compared by deployment model
| Platform | Deployment options | Runs without the vendor's cloud? |
|---|---|---|
| Boomi | Managed Atom Cloud, customer-managed on-premise Atom, IaaS, clustered Molecule | Yes; the most mature hybrid model in the category |
| MuleSoft | CloudHub 2.0 (managed), Runtime Fabric (customer-managed Kubernetes), self-managed servers | Yes, through Runtime Fabric or self-managed runtimes |
| SnapLogic | Cloudplex (managed), Groundplex (customer-managed on-premise or private cloud) | Yes, through Groundplex |
| Koodisi | Cloud, hybrid with an on-premise agent, or on-premise | Yes, with on-premise deployment |
| Azure Logic Apps | Consumption (multi-tenant), Standard (single-tenant), Hybrid Deployment Model through Azure Arc (GA 2025) | Yes, through the Hybrid Deployment Model |
| Workato | Cloud, with an On-Premise Agent for private networks | Partly; the agent needs an outbound connection to Workato's cloud |
| n8n | Self-hosted (Docker or Kubernetes) or managed cloud | Yes, if self-hosted, but you run all of it |
| Celigo | Cloud, with a Celigo Private Cloud option on dedicated infrastructure | Partly; dedicated cloud, not customer-managed |
| Power Automate | Cloud flows on Microsoft's cloud; desktop flows run on local Windows machines | No standalone on-premise deployment |
| Zapier | Cloud only | No |
| Make | Cloud only | No |
| Tray.ai | Cloud only | No |
For a wider comparison that also covers pricing and fit, see our guide to the best iPaaS platforms in 2026.
Why deployment model matters more than price
Price is negotiable. Deployment model usually isn't. If a regulation, contract, or security policy says data must stay inside your network, a cloud-only platform is out before you compare a single feature. That's why capable tools like Zapier, Make, and Tray.ai often don't make it past the first round in banking, healthcare, or government: they're not worse, they're incompatible with a hard requirement.
The difference between hybrid and on-premise matters too. Workato's On-Premise Agent is useful, since it lets Workato reach systems inside your network, but it still takes its instructions from Workato's cloud. Boomi's Atom and SnapLogic's Groundplex can run on infrastructure you manage. If "on-premise" means "no dependency on the vendor's infrastructure", ask that exact question. Almost every vendor will answer yes to "do you support on-premise" in some form.
For when an agent-based setup is the right answer, see hybrid integration: when you need an on-premise agent.
Questions to ask before you shortlist a platform
- If the on-premise component loses its internet connection, does it keep running, or does it stop?
- Does the hybrid or on-premise option cost extra, or is it limited to an enterprise tier?
- Can the on-premise component run in an air-gapped network, or does it need outbound access for licensing or telemetry?
- Where do logs, payloads, and credentials live in each model?
- For self-hosted options, who owns patching, certificate renewal, backups, and scaling?
Where Koodisi fits
Koodisi deploys as managed cloud, as hybrid with an on-premise agent that reaches systems inside your network, or fully on-premise for teams that need everything on their own infrastructure. The same governance, API management, and observability apply in every model, so moving a workload from cloud to on-premise doesn't mean switching tools. See how Koodisi handles security, or book a demo to talk through your deployment requirements.
Frequently asked questions
What is a cloud integration platform?
A cloud integration platform is an iPaaS that connects applications, data, and APIs from vendor-run cloud infrastructure. Many also offer hybrid or on-premise options for systems that can't be reached from the public cloud.
What's the difference between a hybrid and an on-premise integration platform?
A hybrid platform keeps its control plane in the vendor's cloud while an agent inside your network runs the integrations. An on-premise platform runs on your own infrastructure without depending on the vendor's cloud. Both keep data inside your network, but only on-premise keeps working if the connection to the vendor goes down.
Which iPaaS platforms have no on-premise option?
Zapier, Make, and Tray.ai are cloud-only. Power Automate's cloud flows are cloud-hosted, though its desktop flows run locally on Windows.
Is self-hosted the same as on-premise?
Both run on infrastructure you control. The difference is support and governance: n8n's free Community Edition is self-hosted and you operate all of it, while commercial runtimes such as Boomi's Atom or SnapLogic's Groundplex are built for enterprise hybrid deployment with vendor support.
Do on-premise deployments get the same updates as cloud?
It depends on the vendor. Most hybrid platforms push runtime updates on a regular schedule, sometimes a little behind cloud. With a self-hosted platform, you apply updates yourself and control the timing.
The takeaway
"Cloud integration platform" isn't one category. It spans cloud-only tools, hybrid platforms with an agent in your network, and platforms you can run entirely yourself. Confirm the deployment model first, then ask what happens when the on-premise component loses its connection to the vendor. That answer tells you more about fit than any feature list.