How OIE compares
An honest look at Open Integration Engine alongside BridgeLink and Mirth Connect, including where the others are strong.
| Feature | OIE | BridgeLink | Mirth (open source) | Mirth (commercial) |
|---|---|---|---|---|
| License | MPL 2.0 | MPL 2.0; some parts Business Source (restricted) | MPL 2.0 | Proprietary |
| Free, no paid tiers | Yes | Tiered licensing | Yes | Paid |
| Plugins, free and open | All free, MPL 2.0 | Vary by license tier | Core only | Paid extensions |
| Open source web administrator | Yes | Restricted | No | No |
| Community-governed, vendor-neutral | Yes | Single vendor | Single vendor | Single vendor |
| Open-source foundation | Applied | No | No | No |
| Commercial support | Independent vendors | Vendor-led | Community + vendors | Vendor-led |
| Actively developed | Yes | Yes | No | Yes |
| Mirth-compatible | Yes | Yes | Yes | Yes |
Independent vendors also support BridgeLink and Mirth Connect. The distinction is that OIE has no controlling vendor; its support ecosystem is vendor-neutral. Comparison based on publicly available information and each project's own published licenses, as of August 2026.
Where OIE is different
OIE builds on the open source foundation that Mirth Connect established, and takes that openness further. Every OIE plugin is free and MPL 2.0 licensed, with nothing held back for a paid tier. Capabilities that cost extra elsewhere are open in OIE: the TLS Manager handles certificate management comparable to NextGen's paid SSL Manager extension, and Role Based Access Control provides user permissions comparable to NextGen's paid User Authorization extension. Both are free and community-maintained.
BridgeLink open-sources its engine under MPL 2.0, but ships its web administrator under the Business Source License, which by its own terms is "not an Open Source license" and may not be used with any integration engine other than BridgeLink. OIE has a web-based administrator as well, and like every OIE plugin it is fully open under MPL 2.0, reusable without restrictions.
OIE also has the most active open development and community of the group. The work happens in public on GitHub, and an active Discord is where many experienced Mirth practitioners now help each other day to day.
Built to stay independent
OIE is governed by its community today, not by any single vendor. To protect that independence for the long term, the project has applied to join the Eclipse Foundation, a vendor-neutral home for open source software. That process is underway. The goal is simple: no one company can ever take OIE private, change its license, or put it behind a paywall.