The whole interface workflow, in one product
MessageFoundry includes an engine, browser console, VS Code extension, and test tools. Configure interfaces, run them as a service, and inspect messages from one toolkit. All components are in Early Access.
Watch connection status and message flow
The engine serves a browser console with connection status, throughput, and tools to investigate messages.
- Live dashboard — every connection's status and throughput in one view.
- Search and inspect any message, with a readable view of its HL7 structure.
- Delivery & audit trail — see exactly what happened to a message, and who looked at it.
- One-click replay — re-send a stored message after you've fixed the cause.
- Never touches the database — it drives and observes the engine only through the one local API.
Configure and test interfaces in VS Code
Use setup wizards to generate connections and routes. Write Python for custom logic.
- Setup wizards — guided New Connection and New Route flows generate the wiring so you don't start from a blank file.
- Validate as you save to catch configuration errors in the editor.
- Dry-run Test Bench — run a real message through a route and see the before/after, without touching a live system.
- Stage → Promote — push a reviewed change to a running engine when you're ready.
- Pipeline-ready — interfaces are plain Python in git, so they review in pull requests and test in your CI like any other code.
- AI assistance, PHI-safe — an in-editor assistant that helps author and migrate, sending only code, never message bodies.
Run the engine as a service
Run the engine on your servers or in your private cloud, with no graphical interface required.
- Runs as a background service — install it as a Windows service with the included scripts.
- Headless and self-hosted — no GUI required; deploy it where your PHI already lives.
- Durable delivery includes automatic retries, dead-letter replay, and active-passive failover. No separate broker is required.
- Independent per destination — a slow or down peer never holds up the others.
- One local API — the console and the editor both attach to it; the deployment shape is a config choice.
A single interface measured about 50 messages per second on anonymized, representative traffic, with durable, ordered delivery. Actual capacity depends on your workload and infrastructure. Interfaces share resources; measure aggregate throughput before sizing a deployment. Read the sizing guide →
Test an interface before it goes live
Use the included test tools with synthetic data during development and in continuous integration, which runs checks on each change.
- Send / receive bench — drive inbound and outbound endpoints interactively as you develop.
- Automated scenario runner — assert routing and transform behavior on every change, in CI.
- Synthetic data generator — realistic, PHI-free HL7 for load and edge-case testing.
- Commit gate — validate configuration before it can ship.
- Use synthetic data to check interface behavior without patient data.
Try the toolkit
Start with a sample route, then test your own interface.