Home / Compare
An honest comparisonWe are not neutral — we sell one of these options. So here is the version we would want to read: what each approach is genuinely good at, what it costs, and when you should pick something other than us.
At a glance
| What you are comparing | The usual market pattern | EngineHost |
|---|---|---|
| Pricing | Quote-only. Prices are negotiated privately and rarely appear on the vendor's own website. | Four tiers published on this site, from $199/mo |
| Commitment | Annual licences and multi-year agreements are the norm for commercial engines. | Month-to-month, no setup fee, no minimum term |
| Three-year cost, mid-size | Published third-party estimates put commercial engines between $235K and $900K+ across three years. | $21.6K (Standard) to $43.2K (Professional) at list price |
| BAA | Typically negotiated, and often only surfaced at the enterprise tier. | Signed in the signup flow at every tier, including $199 |
| The engine itself | Proprietary engines with their own scripting model — moving off is a rewrite project. | Open Integration Engine, an open-source project under MPL 2.0 |
| Migrating from Mirth | Channels are rebuilt in the new engine's own language before you can go live. | Channels import as-is; the analyzer reports per-channel exceptions first |
| Support | Tiered contracts, often capped by case count, with 24×7 sold as an upgrade. | Uncapped support at every tier; 24×7 on-call from Professional |
| Getting your work out | Export formats vary and off-boarding is usually a services engagement. | Channel configs are versioned and exportable on demand |
| Time to first value | Sales cycle, then an implementation project measured in quarters. | Sign up and point the agent at an engine the same afternoon |
Three-year cost estimates for commercial engines are published by mirth.support and vary widely by deployment size and negotiated discount. We have described general market patterns rather than any single vendor's current terms — check the specifics with whoever you are evaluating, because those terms change.
Pick the right one
Right for you if you already have engineers who know the engine and want to keep the pager in-house. Our Monitor tier exists for exactly this case — keep your engine, borrow our alerting.
Right for you if you are a large health system with an existing vendor relationship, a dedicated interface team and budget approved on an annual cycle. We are not trying to displace that.
Right for you if your problem is reaching hundreds of provider organisations, not running the handful of interfaces your own operation depends on.
Right for you if you run somewhere between three and thirty interfaces, you do not want a full-time interface engineer on call, and you would like to know the price before the first meeting.
The Mirth question
The open-source line of Mirth Connect ended at version 4.5.2 and has not received security patches since. Open Integration Engine picked up that lineage as a community-run fork, and its 4.6 release remediated 24 CVEs that the older code still carries. If you are running 4.5.2 in production today, that is the gap worth understanding — regardless of who you decide to host with.
If another option is the better fit for your setup, we would rather tell you now than onboard you into the wrong one.
EngineHost is an independent service built on Open Integration Engine and is not affiliated with, endorsed by or sponsored by NextGen Healthcare. Mirth® and Mirth Connect® are registered trademarks of NextGen Healthcare, Inc.