Mirth Connect Licensing Explained: Open Source vs Commercial
Mirth Connect licensing changed significantly in 2025, and many organizations are still working out what it means for budgets, security updates and long-term plans. For years, Mirth Connect was known as a free, open-source healthcare integration engine with optional paid extensions and support. NextGen Healthcare has since moved newer releases to a commercial licence. This neutral explainer covers what changed, which features are gated, total cost of ownership and your realistic options. Last reviewed September 2026; verify current terms with NextGen before deciding.
How Mirth Connect Licensing Has Changed
Mirth Connect began as an open-source project and became one of the most widely deployed healthcare integration engines. NextGen Healthcare, which owns Mirth, historically offered the core engine free under an open-source licence, with commercial extensions and support subscriptions available separately. In 2025, NextGen announced that newer Mirth Connect releases would be available only under a commercial licence. Older open-source versions remain in use, but they no longer receive new official releases from NextGen.
The Historical Open-Source Model
For many years, the Mirth Connect core engine was free to download and use, which made it popular with hospitals, labs and startups needing capable integration without large licensing budgets or procurement cycles.
What Changed in 2025
NextGen moved newer Mirth Connect versions to commercial licensing. Organizations wanting current releases, security fixes and official support now need a commercial agreement, based on NextGen's published terms. Confirm details directly with NextGen.
What Happens to Older Versions
Existing open-source versions continue to run and can still be used under their original licence terms. However, they do not receive new features or official security updates from NextGen going forward.
Why the Change Matters
Many business cases, including healthcare interoperability consulting roadmaps, assumed a free core engine. The change affects budgets, risk assessments and vendor comparisons, especially for organizations running large numbers of channels on older releases.
Community Responses
Community forks based on the last open-source release have appeared, aiming to continue open development. Evaluate any fork carefully for maintenance activity, security practices, support options and long-term sustainability. Maturity varies considerably.
Is Mirth Connect Free?
The question is Mirth Connect free now has a nuanced answer. Older open-source versions remain free to use, but newer releases require a commercial licence, and even older versions carry real costs through infrastructure, skilled staff, security management and support. For organizations handling PHI, running unsupported software also creates compliance and risk management considerations. Understanding each cost element helps leadership make informed decisions rather than relying on outdated assumptions about free integration software.
Older Open-Source Releases
Older versions released under open-source terms can still be used without licence fees. The trade-off is no new official security updates, bug fixes or compatibility improvements from NextGen. Risk grows over time.
Newer Commercial Releases
Current and future releases require a commercial licence from NextGen. Pricing depends on NextGen's terms and your agreement, so request formal quotes rather than relying on third-party estimates. Negotiate multi-year terms carefully.
Security Update Considerations
Unpatched software handling ePHI increases risk and must be addressed in your HIPAA risk analysis. Compensating controls, such as network isolation and monitoring, reduce but do not eliminate that risk.
Support Availability
Commercial agreements typically include vendor support. Organizations on older versions rely on internal expertise, community resources or third-party support partners, which should be evaluated carefully for responsiveness. Verify partner credentials and references.
Compliance Documentation
Auditors and customers may ask how you manage vulnerabilities in your integration engine. Document your version, patch strategy, compensating controls and roadmap, regardless of which licensing path you choose. Update it annually.
Features Historically Gated Behind Commercial Tiers
Even before 2025, some Mirth Connect capabilities were available only through commercial extensions or subscriptions. These features matter most for larger or regulated environments needing high availability, advanced security management or enterprise administration. Knowing which capabilities require paid tiers helps organizations compare Mirth fairly with other engines. Always confirm the current feature list and packaging with NextGen, because extension bundles and names can change between releases and agreements. The main categories are listed below.
Advanced Clustering
Native clustering for high availability has been a commercial capability. Organizations needing active-active processing must include clustering licences in cost comparisons with other integration engines. Alternatives like active-passive failover may suit smaller budgets.
Advanced Security and Access Management
Features such as role-based access control, LDAP authentication and certificate management extensions have been offered commercially. These capabilities support HIPAA access control and audit requirements in larger teams. Confirm current packaging first.
Advanced Alerting and Channel History
Enhanced alerting and channel change history extensions help operations teams detect problems and track configuration changes, supporting both reliability and audit control obligations for regulated environments. External tools can supplement these features.
Specialized Connectors
Some connectors and interoperability extensions have been commercial. Check whether your required connectors, such as specific FHIR or protocol capabilities, are included in your chosen licence tier. Missing connectors mean custom development.
Vendor Support Tiers
Support subscriptions have offered different response times and service levels. Match the tier to your uptime requirements, because critical clinical interfaces need faster vendor escalation than batch feeds. Compare response commitments.
Total Cost of Ownership and Your Options
Licensing is only one part of Mirth Connect total cost of ownership. Infrastructure, databases, high availability, monitoring, staffing, training and support often cost more than the licence itself over five years. A fair comparison includes all of these, along with migration costs if you change engines. Our Mirth Connect consulting team helps organizations model these costs neutrally, including options that do not involve us or Mirth. Contact our team for a neutral cost model.
License Current Mirth Versions
Purchasing a commercial licence provides current releases, security fixes and vendor support. This suits organizations with large Mirth estates, strong Mirth skills and requirements for vendor-backed support. Budget for renewals annually.
Stay on an Older Version Temporarily
Some organizations remain on older versions while planning. This can be reasonable short term, with strong compensating controls and a documented risk decision, but it is not a permanent strategy.
Evaluate Community Forks
Community forks may offer continued open development. Assess governance, release frequency, security response, compatibility with existing channels and support availability before trusting one with clinical interfaces. Pilot on non-critical channels first.
Migrate to Another Engine
Alternatives include Rhapsody, Corepoint, Cloverleaf and cloud integration platforms. Migration costs are significant, so compare five-year total costs, not just licence fees, before deciding to move. Our HL7 integration team supports migrations.
Reduce Engine Dependency
For API-heavy environments, some workloads can move to FHIR integration services or custom healthcare API development, leaving the engine to handle only legacy HL7 feeds. This can lower licensing needs over time.
Frequently Asked Questions
Is Mirth Connect still free?
Older open-source versions of Mirth Connect can still be used without licence fees, but they no longer receive official updates. NextGen Healthcare moved newer releases to commercial licensing in 2025. Organizations wanting current versions, security fixes and vendor support need a commercial agreement. Verify current terms directly with NextGen.
Is Mirth Connect open source?
Mirth Connect was historically open source, and older releases remain available under their original open-source terms. Newer releases from NextGen are commercially licensed. Community forks based on the last open-source version have appeared, but organizations should evaluate their maintenance, security practices and support before using them in production.
How much does a Mirth Connect licence cost?
Pricing depends on NextGen's current terms, deployment size, required extensions and support level, so there is no single public price. Request a formal quote from NextGen. When comparing costs, include infrastructure, staffing, high availability, monitoring and support, because these often exceed licence fees over five years.
Can we keep using an older Mirth version?
You can continue running older open-source versions under their original licence terms. However, they will not receive new official security updates. For environments handling PHI, document this in your HIPAA risk analysis, apply compensating controls like network isolation and monitoring, and plan a long-term strategy.
Which Mirth features require a commercial licence?
Historically, capabilities such as advanced clustering, role-based access control, LDAP authentication, advanced alerting, channel history and some specialized connectors have been commercial. With newer releases now commercially licensed overall, confirm exactly which features and extensions are included in each tier directly with NextGen before purchasing.
Should we migrate away from Mirth Connect?
Not automatically. Migration is expensive and risky, so compare five-year total costs for licensing current Mirth, staying temporarily on an older version, adopting a community fork or moving to another engine. The right answer depends on your channel count, skills, uptime needs, budget and risk tolerance.
Need a Neutral Mirth Cost Model?
Our integration engineers are ready to help. Free consultation, no obligation.