iPaaS — Integration Platform as a Service
Integration Platform as a Service (iPaaS) denotes cloud-based integration tooling that connects ERP to e-commerce systems, CRM, marketplaces, supplier portals, BI tools, IoT platforms and departmental SaaS applications. iPaaS replaced the on-premises ESB-and-middleware stack of the 2000s with a cloud-native model: subscription-priced, pre-built connectors, visual flow designers, managed runtime. For mid-market in Germany, Switzerland and Austria, iPaaS has become the default integration tier for any organisation with five-plus systems exchanging data.
Core capabilities
- Connectors — pre-built adapters for common SaaS apps (Salesforce, HubSpot, Slack, Microsoft 365, Shopify, SAP, NetSuite)
- Visual flow designer — drag-and-drop construction of integration flows
- Transformation — mapping fields, converting formats (XML, JSON, EDIFACT, CSV)
- Orchestration — multi-step flows with branching, retry, error handling
- API management — publishing internal APIs with rate limiting and security
- Monitoring — real-time visibility into flow status, errors, throughput
- Hybrid deployment — on-premises gateways for connecting cloud iPaaS to on-prem ERP
Leading iPaaS vendors
Enterprise: MuleSoft Anypoint Platform (Salesforce, market leader), Boomi (Dell-owned, broad mid-market presence), Microsoft Azure Logic Apps and Power Automate, SAP Integration Suite, Workato, Informatica Intelligent Cloud Services — 50,000 to 1,000,000 EUR per year for mid-size deployments. Mid-market: Celigo, Jitterbit, SnapLogic, Tray.io — 30,000 to 200,000 EUR per year. Lightweight: Zapier (workflows under 50 steps), Make (formerly Integromat), n8n (open-source) — 1,000 to 30,000 EUR per year. In DACH mid-market, Microsoft Power Automate is dominant through Microsoft 365 bundling; Boomi and Celigo have strong NetSuite-centric installs; SAP Integration Suite is the default in SAP S/4HANA landscapes.
Common ERP integration patterns
(1) E-commerce to ERP: orders from Shopify or Shopware flow into ERP, with stock and price flowing back. (2) CRM to ERP: Salesforce or HubSpot synchronise customer master data and opportunities with ERP sales-order entry. (3) Marketplace orchestration: Amazon, eBay, Otto orders unified into the ERP with channel-specific order-status feedback. (4) Bank and payments: payment gateways (Stripe, PayPal, Mollie) integrate with ERP accounts receivable. (5) HR-to-ERP: personio, SAP SuccessFactors, Workday flow headcount and payroll allocations into ERP financial and project modules. (6) BI and analytics: ERP data lakes feed Power BI, Tableau, Qlik via scheduled extracts. (7) EDI for B2B: trading-partner EDI flows transformed into ERP-internal format and back.
Choosing the right iPaaS tier
Match iPaaS tier to integration complexity. Under 10 simple flows, low data volume: Zapier, Make or Power Automate Standard is sufficient. 10-50 flows, mid-volume, some transformation complexity: Celigo, Jitterbit, Boomi or Azure Logic Apps. 50+ flows, real-time requirements, complex orchestration, B2B EDI: MuleSoft, Boomi Enterprise, SAP Integration Suite, Workato. SAP-centric S/4HANA landscape: SAP Integration Suite for native compatibility, or Boomi/MuleSoft for multi-vendor heterogeneous landscapes. Cost discipline: iPaaS pricing is often per-connection or per-flow, and unused connections accumulate quickly. Quarterly cleanup is essential.
Related Topics
Frequently Asked Questions
Why not let the ERP do all integration itself?
Modern ERP includes integration modules (SAP Integration Suite, NetSuite SuiteScript, Dynamics 365 dual-write) and they are useful for ERP-led integration. iPaaS becomes the better choice when integration is not ERP-led — cross-system, between non-ERP applications, or when integrations need to outlive an ERP migration.
Is open-source iPaaS (n8n, Apache Camel) viable for production?
Yes for tech-savvy teams with operational maturity. n8n in self-hosted mode handles thousands of flows reliably. Apache Camel via Spring Boot is battle-tested at enterprise scale. Trade-off: lower licence cost, higher operational responsibility — you own monitoring, patching, scaling. Most mid-market organisations prefer commercial iPaaS for the SLA and reduced operations effort.
How does iPaaS handle on-premises ERP?
Cloud iPaaS connects to on-premises ERP via a lightweight gateway agent installed on-premises that creates an outbound connection to the iPaaS cloud. The gateway exposes ERP databases, APIs and file shares to the cloud-side flow runtime without needing inbound firewall rules. Microsoft, Boomi, MuleSoft and SAP all provide such gateways.