ENGIntegration engines

The engine after Mirth Connect

Mirth Connect stopped being open source in 2025. Open Integration Engine (OIE), hosted by the Eclipse Foundation, carries it forward. We guide you to it with our own tools, and run it with you.

OIEThe engine

Why Open Integration Engine

The engine running your interfaces has to outlast any contract. Three reasons to choose OIE, and one about us.

  • Free, for goodHosted by the Eclipse Foundation under a free licence: no company can close its code again, as happened to Mirth Connect.
  • AliveAn active community, releases that keep coming, and security fixes that don't wait on a vendor's goodwill.
  • Known down to the codeWe know its code, not just its settings: that is what lets us build solid extensions and fix things at the source when needed.
HOWHow we work

From the first inventory to go-live

  1. 01

    Take the measure

    Systems, message types, volumes, weak points. Often the first complete inventory your team has had in hand.

  2. 02

    Build and validate

    Scope set with you, then every interface validated on your real traffic before cutover, not on samples.

  3. 03

    Go live, and keep working together

    Up-to-date documentation, access that stays yours, and a team that runs the engine alongside yours: upgrades, performance, security, day after day.

ALTNot ready to change yet

Still on Mirth Connect or BridgeLink

If the time to change engines has not come, let's talk anyway. We have known these engines since their first versions, and we can support you until migrating is the right decision for you, not for us.