OIE + OpenShare
vs Iguana.
Iguana (by iNTERFACEWARE) is a developer-friendly integration engine with visual programming tools and Lua scripting, lightweight and built for agile development. OIE + OpenShare delivers open-source licensing, zero engine costs, and a modern experience layer. Here’s the honest comparison.
Developer-friendly tools vs open-source freedom.
Iguana and OIE + OpenShare both appeal to technically-minded integration teams, but with different trade-offs.
Open Integration Engine
OIE is the community fork of Mirth Connect, free under MPL 2.0. Binary-compatible with Mirth Connect, same channels, same API, same extensions. JavaScript-based transformation scripting. OpenShare adds a purpose-built browser admin console, VPN-free remote access via Gateway, and direct encrypted data exchange, organization-to-organization, via Exchange.
- Open-source under MPL 2.0, free engine
- JavaScript scripting, familiar to most developers
- Purpose-built browser admin (OpenShare Console)
- VPN-free remote access + built-in direct exchange
Iguana by iNTERFACEWARE
Iguana is a commercial integration engine designed specifically for developer agility. Known for visual programming tools and Lua scripting, a lightweight environment well-suited to rapid interface development and quick prototyping. Lighter-weight than enterprise platforms. Per-channel licensing.
- Visual programming + Lua scripting
- Designed for rapid developer iteration
- Lightweight and agile
- Per-channel licensing (commercial)
Feature-by-feature comparison.
OIE + OpenShare vs Iguana. Open-source breadth vs developer-first tooling.
| Capability | OIE + OpenShare | Iguana (iNTERFACEWARE) |
|---|---|---|
| Engine type | OIE (open-source fork of Mirth Connect) | Iguana (proprietary, by iNTERFACEWARE) |
| Open source | ✓ | ✗ |
| License | MPL 2.0, free | Per-channel (commercial) |
| Browser adminOpenShare Console adds DICOM viewer, channel analytics, real-time message browsing | OpenShare Console (purpose-built) | Built-in web-based admin |
| VPN-free remote accessOpenShare Gateway; Iguana requires traditional network access | ✓ | ✗ |
| Direct data exchangeIguana does not include a native org-to-org exchange network | Built-in, E2E encrypted | ✗ |
| HL7 v2 / FHIR / X12 | ✓ | ✓ |
| DICOM supportOIE + OpenShare Console includes a built-in DICOM viewer | ✓ | Limited |
| Scripting languageIguana's Lua environment is a genuine developer ergonomics differentiator | JavaScript (familiar, widely known) | Lua (lightweight, developer-friendly) |
| Developer ergonomicsIguana's visual tooling and Lua scripting are well-regarded for quick prototyping | Modern browser-based, JS scripting | Visual programming + Lua, purpose-built for rapid dev |
| Quick prototypingIguana is designed for developer agility and fast iteration | Familiar Mirth Connect patterns | Purpose-built for agile development |
| Vendor support | Community + Saga IT | iNTERFACEWARE (commercial) |
An honest comparison.
Both tools are developer-friendly, but they make different bets.
- Zero engine licensing cost (MPL 2.0 open-source)
- No per-channel fees
- OpenShare Console: purpose-built browser admin with DICOM viewer + analytics
- VPN-free remote access via OpenShare Gateway
- Built-in direct encrypted data exchange (not available in Iguana)
- JavaScript scripting, familiar to most developers
- Open stack, no vendor lock-in
- Developer ergonomics: visual programming tools purpose-built for rapid development
- Lua scripting: lightweight, flexible, well-suited to quick iteration
- Lighter-weight footprint than full enterprise engines
- Commercial support from iNTERFACEWARE
- Quick prototyping workflow for developer-driven teams
The bottom line: Iguana’s Lua scripting and visual programming tools are a genuine developer ergonomics differentiator for teams that prioritize rapid prototyping. If your team loves Lua and wants a purpose-built developer workflow, Iguana is worth evaluating. If you want open-source freedom, zero engine licensing, and modern operational tooling (browser admin, VPN-free access, direct exchange) built in, OIE + OpenShare is the stronger platform choice.
Frequently asked questions.
How does Iguana compare to OIE + OpenShare?
Iguana (by iNTERFACEWARE) is a developer-friendly integration engine known for visual programming tools and Lua scripting, a lightweight, agile approach to healthcare integration. OIE + OpenShare provides a similar integration foundation with open-source licensing (MPL 2.0), a modern browser-based admin console, VPN-free remote access, and built-in direct data exchange. Iguana leads in developer ergonomics and Lua scripting flexibility; OIE + OpenShare leads in cost (free engine license) and built-in operational tooling.
What scripting language does Iguana use?
Iguana uses Lua as its primary scripting language, which gives developers a lightweight, flexible scripting environment for message transformation and routing. OIE (as a Mirth Connect fork) uses JavaScript for transformation scripts, which is familiar to a wider developer base. Both approaches are code-driven; Iguana’s Lua environment is considered particularly ergonomic for rapid interface development.
Does OpenShare work with Iguana?
OpenShare (Console, Gateway, Exchange) is designed to run on top of OIE and other Mirth Connect-compatible engines. It is not compatible with Iguana, which uses a different engine architecture. Evaluating OIE + OpenShare as an alternative to Iguana would involve migrating interface logic to OIE.
Is Iguana open source?
No. Iguana is a commercial product by iNTERFACEWARE with per-channel licensing. OIE is open-source under MPL 2.0 and free to use, run, and modify. OpenShare Console and secure remote access are always free; exchanging data on the network is a flat per-server monthly membership.
Which is better for quick prototyping: Iguana or OIE?
Iguana is specifically designed for quick prototyping and developer agility, the visual programming tools and Lua scripting environment are well-suited to rapid iteration. OIE + OpenShare offers a JavaScript-based transformation environment with a browser-based admin console that is generally accessible to developers familiar with the Mirth Connect ecosystem. For teams already comfortable with Mirth Connect, OIE requires minimal learning curve. For teams that prefer Lua or lightweight visual tooling, Iguana may offer faster initial development.
