Frequently asked questions.

No. Open Integration Engine continues the Mirth Connect codebase, so channels, transformers and code templates import as-is. The migration analyzer reads your channels.xml export and reports the specific exceptions — Java 17 changes, XML parser calls, older date utilities — per channel, so you know what needs attention before you commit to anything.

The open-source line of Mirth Connect ended at 4.5.2 and has not received security patches since. Open Integration Engine is the community-run continuation of that codebase, distributed under MPL 2.0; its 4.6 release remediated 24 CVEs that 4.5.2 still carries. It is the same lineage, actively maintained.

For fewer than twenty channels, a typical cutover is one to two days of work once the analyzer report is clean. We run both engines in parallel on live traffic until you are ready to flip over, so there is no single moment where everything depends on the move having been perfect.

Yes, at every tier including the $199 Monitor plan. You sign it inside the signup flow — the exact agreement text, your signature, the signing IP and a SHA-256 hash of the document are all stored together, and the record is append-only.

We are running a SOC 2 Type II programme; we are not going to claim a certification we do not yet hold. What exists today: US-hosted infrastructure with a private data plane, encryption in transit and at rest, a hash-chained audit log enforced by database triggers, and nightly restore-drilled backups. Ask us for the current state of the programme and we will tell you plainly.

Monitoring works on health signals — queue depths, error rates, heap, last-message timestamps — not message bodies. The public status page, if you turn it on, shows health signals only and never message data. Access to a hosted engine is logged in the append-only audit trail.

One channel is one source with its destinations. A feed that reads from your LIS and writes to two downstream systems counts as one channel, not three. If your setup makes the count ambiguous, we will work it out with you before you buy.

Standard carries a 99.5% SLA and Professional 99.9%, both measured on the hosted engine. Enterprise agreements are written to your requirements. If we miss an SLA we credit it — and because billing is monthly, the exit is never blocked by a contract you are stuck inside.

Yes — that is exactly what the Monitor tier is. You install a small agent next to your existing Mirth, OIE or BridgeLink instance and get alerting, dashboards and history without moving a single interface. Many customers stay there.

Hosted engines sit behind an MLLP/VPN and SFTP edge with TLS managed for you. In most cases the sending system points at a new endpoint and nothing else about it changes; where a partner insists on a fixed IP or a site-to-site tunnel, that is part of onboarding rather than an extra product.

On Professional and Enterprise, an on-call engineer — 24×7, uncapped, not metered by case count. On Standard, alerting runs around the clock and human response is business hours. The distinction is deliberate and it is on the pricing page rather than buried in an addendum.

Yes. A hosted engine is still your engine — your team keeps access. On Professional and above, channel configurations are versioned by content hash and promoted dev → staging → prod, with a one-click rollback and an audit trail of who deployed what.

Billing is month-to-month, and channel configurations can be exported on demand. Because the engine underneath is open source, an export is something you can actually run somewhere else rather than a file that only works inside our product.