AGPL v3 · Open Source · Pulsar-Native

Enterprise middleware.
Without the licence bill.

Open-M is the open-source integration platform built for the real enterprise stack — 160+ connectors, YAML-defined pipelines, and a Kubernetes-native runtime. Replace MuleSoft and TIBCO without a six-figure annual contract. Open-M can also run embedded existing middleware components as microservice within Open-M. This way the investments made in existing middleware platforms can still be utalized.

🏭 SAP IDoc inbound
UTL-X Map inline
☁️ Salesforce opportunity
🔔 Workday fulfillment
📦 EDIFACT DESADV D96A
status: RUNNING
throughput: 4,210 msg/s
latency p99: 18ms
delivery: at_least_once
replicas: 3

Replacing or complementing

MuleSoft® TIBCO webMethods® IBM App Connect® Azure Integration Boomi®

The problem

Great integration technology,
broken pricing model.

💸
Per-connector licensing

MuleSoft charges separately for SAP, Workday, Salesforce, and ServiceNow connectors. A realistic enterprise stack of 12 connectors can exceed €250,000 per year before a single pipeline runs.

🔒
Proprietary runtime lock-in

TIBCO BW and MuleSoft runtimes are black boxes. Your pipeline definitions, mapping logic, and operational tooling are entirely trapped inside a vendor's ecosystem.

☁️
Cloud-only pricing coercion

Platform vendors increasingly force cloud-managed deployment at SaaS price points — even for enterprises with on-premise, hybrid, or air-gapped requirements.

Open-M changes this

All 160+ connectors included. YAML pipeline definitions that you own. Kubernetes-native runtime you deploy anywhere. Apache Pulsar as the broker. No per-connector tax. Ever.

ANNUAL COST ESTIMATE — 12 ENTERPRISE CONNECTORS

MuleSoft Anypoint — Premium tier € 280,000 +
TIBCO BusinessWorks — Enterprise € 190,000 +
IBM App Connect Enterprise € 160,000 +
Open-M — all 160+ connectors € 0

Estimates based on publicly disclosed list pricing and connector pack costs. Actual vendor quotes vary. Open-M is AGPL v3 — free for internal enterprise use. Commercial licences available for managed service operators.

Connector coverage

Every system your enterprise actually runs.

160+ connectors across SAP, Oracle, Microsoft, Salesforce, Workday, EDI, healthcare, financial protocols, and cloud platforms. Built on Apache Camel 4.x where excellent components exist. Built native for the connectors that matter most and have no good open-source equivalent.

160+ Total connectors
26 Launch-ready (P1)
0 Per-connector cost
🏭
SAP RFC / BAPI / IDoc
P1 · Native build
☁️
Salesforce
P1 · Apache Camel
👔
Workday
P1 · Native build
🔧
ServiceNow
P1 · Apache Camel
📄
EDIFACT
P1 · Native build
📋
X12 / ANSI EDI
P1 · Native build
🏦
IBM MQ
P1 · Apache Camel
Apache Kafka
P1 · Apache Camel
🔷
Microsoft Dynamics 365
P2 · SDK-wrap
🏗️
Oracle Fusion Cloud
P2 · SDK-wrap
🏥
HL7 v2 / FHIR R4
P1–2 · Apache Camel
💳
SWIFT / ISO 20022
P2 · Native build
🅰️
AWS S3 / SQS / SNS
P1 · Apache Camel
🔵
Azure Service Bus / Blobs
P1 · Apache Camel
📁
FTP / SFTP / AS2
P1 · Apache Camel
145+ more connectors
View full registry →

Architecture

Built on standards you already trust.

Open-M is not built from scratch on a new runtime that becomes a liability when the project stalls. Every layer uses proven, production-battle-hardened open-source infrastructure.

01
Apache Pulsar as the native broker

Every message on the bus is wrapped in an MPPM envelope — a standard contract carrying correlation ID, schema reference, delivery guarantee, and a step-history window. Pulsar provides exactly-once, at-least-once, and at-most-once delivery natively.

02
YAML pipeline definitions you own

Pipelines are declared in a versioned, human-readable YAML descriptor. No proprietary GUI lock-in. Store pipeline definitions in Git, review them in pull requests, deploy them via CI/CD.

03
Kubernetes-native from the ground up

Open-M runs as a Kubernetes operator. Deploy to any cluster — on-prem, cloud, hybrid, or air-gapped. The IDE renders cluster placement and replica topology directly on the canvas.

04
UTL-X — mapping that lives on the arrow

Lightweight, pure, stateless field mapping that executes inline without an extra hop. Complex mappings and external calls use a full mapping component. Right tool for each job.

OPEN-M RUNTIME STACK
VS Code Extension + Web Dashboard
React Flow canvas · YAML editor · Live telemetry
Control Plane API
Pipeline deploy · Schema Registry · Mapping Registry
Kubernetes Operator
Connector pods · Pipeline instances · DLQ · Replay
Apache Pulsar Broker
MPPM envelope · Topic routing · Delivery guarantees
Connector Adapters (160+)
Apache Camel 4.x · Native builds · SDK-wraps
External Systems
SAP · Salesforce · Workday · IBM MQ · EDI · Cloud

Licensing

Open source with a clear commercial model.

Open-M is AGPL v3 — the same licence as UTL-X. Free for internal enterprise use. Commercial licences available for managed service operators and OEM embedding.

🏢
Internal Enterprise Use

Run Open-M inside your own infrastructure to integrate your own systems. No licence fee. No restrictions on the number of connectors, pipelines, or message volume.

Deploy to your own Kubernetes cluster
Build proprietary connectors for internal use
All 160+ connectors included
No per-connector or per-processor charges
Commercial Licence

Required when Open-M is offered as a managed service, embedded in a commercial product, or distributed to third parties. Enables proprietary modifications without AGPL disclosure requirements.

Offer Open-M as a hosted managed service
Embed in commercial products and OEM
Keep proprietary modifications private
Enterprise support SLA available
👐
Open Source Contribution

Contribute connectors, bug fixes, or features back to the project under AGPL v3. Community connectors are reviewed and maintained by the Open-M team.

All contributions welcome via GitHub
Connector bounty programme (coming soon)
Named contributor recognition
Contributions must be AGPL v3 compatible

Ready to cut the
integration tax?

Deploy your first pipeline in under 10 minutes. No vendor calls required.