Why teams leave
The complaints we hear most about legacy engines
Across KLAS Research, G2, and community forums, the same frustrations with legacy interface engines come up again and again. They're real and recurring — and they're what MessageFoundry was designed to answer. Quotes below are representative and anonymized; where we're not there yet, we say so.
Representative of public feedback across KLAS Research, G2, and community forums — anonymized, with competitor names removed. See sources & notes.
Priced to punish growth
Per-connection fees, per-transaction charges, and a separate bill for web services, FHIR, and alerting. As your interface count climbs, the license grows with it — automatically.
MessageFoundry — Open source under the AGPL: no per-interface, per-connection, or per-transaction fees, and nothing held back as a paid add-on. Web services, REST, FHIR, and alerting are part of the open engine — never a separate license.
Tools — and talent — from a different era
Obsolete scripting languages you can't hire for, version-locked desktop clients, and certifications that run $1,500–$3,500 a head before anyone is productive.
MessageFoundry — Set up interfaces with guided wizards, or use plain Python — one of the most widely known languages, no proprietary DSL to staff for — in VS Code with a PHI-safe AI assistant. No costly certification, and no version-locked desktop client to install.
Version control as an afterthought
No native Git, configuration locked inside the engine's internal database, and manual, error-prone promotion between environments with no automated testing.
MessageFoundry — Your integration is plain Python in your own Git repo — every change a reviewable pull request. A check build-gate dry-runs messages and fails CI on a broken route, and reviewed, tested changes promote DEV → PROD with no config drift.
You find out when a clinician calls
Rudimentary monitoring and channels that stop silently — with recovery that can mean hours of failover while the engine re-verifies every stored message.
MessageFoundry — A live console — connection dashboard, message search, delivery and audit trail, one-click replay — plus a count-and-log invariant: every message is a recorded outcome, so a stalled channel surfaces instead of vanishing. Recovery is replay from the durable store, not a multi-hour integrity scan.
Critical CVEs, slow patches
Exploited, unauthenticated RCE vulnerabilities, multi-step patch paths, and updates that have silently deleted security configuration on install.
MessageFoundry — Open source you can audit line by line and patch on your own schedule. Built through a secure development lifecycle (NIST SSDF) with SAST, dependency, and secret scanning on every build, and secure by default — RBAC, a hash-chained audit trail, and AES-256-GCM encryption at rest. Config lives in Git, so an update can't silently erase it.
Locked in while the vendor changes hands
Proprietary languages and internal config databases make migration prohibitively expensive — while the engine itself gets passed between owners and rebrands, with support drifting after each deal.
MessageFoundry — Your configuration is yours — generated by wizards or written in Python, versioned in your own repo — and your messages live in standard databases; no proprietary language or config database to escape. And as an open-source, non-profit project, it can't be acquired, relicensed, or deprioritized out from under you; worst case, you still have the code.
Where we're not there yet, we say so. The incumbents still lead on connector breadth and proven scale, and a few capabilities — inbound REST/SOAP/FHIR listeners and SMART on FHIR — are on our roadmap, not in Early Access. See the gaps we own below and the roadmap on the features page.
