OpenShare: Healthcare Data Gateway Now in Open Beta

OpenShare is live. The healthcare data gateway we have been building on top of the Open Integration Engine is now in open beta at openshare.health, and you can create a free account today.

The short version: OpenShare is the experience layer for your integration engine. Already run OIE, Mirth Connect, or BridgeLink? It installs as one plugin on the server you have. Starting fresh? The Linux and Windows installer ships OIE with the plugin included.

Either way, you get a modern browser console for the engine, secure remote access that dials outbound only (no open ports, no inbound firewall changes), and direct, end-to-end encrypted exchange with other organizations: HL7, FHIR, DICOM, and the files your channels already move. Your engine and your PHI stay on your own infrastructure.

OpenShare Console dashboard with fleet health, throughput charts, and channel metrics — The OpenShare Console: your fleet, live, in a browser tab.

Why we built it

When NextGen took open-source Mirth Connect commercial in 2025, the community carried the codebase forward as the Open Integration Engine. Saga is an active contributor to OIE and part of its support ecosystem, and the fork solved the big problem: the engine itself has a future.

The experience around the engine is another story. Administration still means a desktop Java client. Remote access still means inbound firewall rules. And moving imaging to another organization usually means a cloud middleman that copies your studies onto its servers and bills you per study.

OpenShare is our answer to that second problem: keep the engine you trust, replace the experience around it.

Timeline from the 2025 Mirth Connect license change, to the community fork that became the Open Integration Engine, to the OpenShare open beta, to openshare.health going live today

What ships today

Five capabilities are live in the beta:

Console. Administer channels from any browser: build, deploy, and browse messages, with advanced mode when you want the full editor. No Java client.
Gateway. Reach your own servers securely from anywhere. Connections dial outbound only, so there are no open ports to manage.
Exchange. Find partner organizations in the Contact Directory, send a scoped sharing agreement, and move data gateway to gateway once both sides accept.
Monitoring. Fleet health, throughput, and alerts across every connected engine, live from the first connection.
DICOM Viewer. Review studies in the browser as they arrive.

Pre-built device Drivers are coming later; tell us which connectors you need first.

Move images without per-study fees

Cloud image networks meter your data and keep a copy of it. OpenShare moves studies and messages directly between organizations, end-to-end encrypted with WebRTC DTLS, and nothing in the middle can read the traffic.

Pricing follows the same idea: we bill the bytes, not the study. A routine CT costs about eight cents to move over the relay, and direct peer-to-peer transfers are never metered at all. In the strictest environments you can turn the relay off and run direct-only.

Swimlane diagram of two organizations exchanging data through OpenShare: the directory and sharing agreement are coordinated through OpenShare signaling, then the transfer itself flows directly between the two organizations, end-to-end encrypted, bypassing OpenShare entirely

What the open beta includes

Everything on your own side is free, during the beta and after it: the full Console, Gateway access, monitoring, and DICOM viewing on one server (two in a free organization). During the open beta, connecting is free too: exchange with up to three partner organizations, with 10 GB of relayed transfer a month included (past that, transfer pauses until the month rolls over).

When the beta ends, running your own servers stays free. A membership ($500 per server per month) is what buys Contact Directory access and the power to initiate connections, and every connection needs just one paying member, who can cover up to 20 partners. Receiving stays free.

Comparison matrix of OpenShare entitlements during the open beta versus when the beta ends: running your own servers is free in both, beta connects up to three partner organizations free, and direct peer-to-peer transfer is never metered in either

Up and running in five minutes

Install the plugin. Drop it into your existing OIE or Mirth Connect server, or download the OIE + plugin installer we built for Linux and Windows (macOS coming soon).
Open the Console. Sign in from any browser. Monitoring is live from the first connection.
Connect and exchange. Find a partner in the directory and send a sharing agreement.

OpenShare connect wizard: choosing what to share with a partner organization — The connect wizard walks both sides through a scoped sharing agreement.

Coming from Mirth Connect? The migration guide shows how the plugin rides along with the channels you already have. No rebuild, no channel moves.

Where this fits

OpenShare comes from the same team that builds MirthSync and works in Mirth Connect and OIE consulting every day. The OpenShare product page has the full tour, and if you are weighing engine options first, start with OIE vs BridgeLink vs Mirth Connect.

Create a free account, or take a look around openshare.health.

OpenShare Is Live: The Healthcare Data Gateway, in Open Beta