Self-hosted appliance
Install MirthDash on an Ubuntu server inside your network. It reaches Mirth locally through the API, and Mirth never has to be exposed to the public internet.
Replace the Java admin console with a browser console that can run inside your network, as a managed private appliance, or through a future cloud-plus-agent model. Mirth does not need to face the public internet.
if (msg['PID']['PID.3']) { channelMap.put('mrn', msg['PID']['PID.3']);}Pick the deployment model that fits your security posture. In every model, the Mirth API stays protected behind your network, firewall, VPN, private tunnel, or local agent.
Install MirthDash on an Ubuntu server inside your network. It reaches Mirth locally through the API, and Mirth never has to be exposed to the public internet.
MirthDash runs as an isolated appliance for your team with DNS, SSL, updates, and health checks handled for you. Connect by VPN, tunnel, firewall allow-list, or future agent.
A lightweight local agent will sit near Mirth and make outbound-only secure connections to the cloud control plane, avoiding inbound Mirth API exposure.
MirthDash is designed so customer credentials, audit trails, and Mirth connectivity stay in the appliance or local network boundary. The licensing site, demo, and managed services stay separate from customer Mirth access, so teams do not have to put the Mirth API or admin credentials on the public internet.
Purpose-built for teams that need a modern, auditable control surface for daily Mirth work.
Watch channel state, queues, errors, events, alerts, and server health across Mirth Connect environments.
Edit scripts, filters, transformers, templates, maps, connector settings, and XML-backed configuration in the browser.
Snapshots, diffs, approvals, audit records, rollback pointers, and permission gates wrap every risky action.
Bring your own OpenAI or Claude key so AI can inspect channel context, explain logs, and help troubleshoot scripts.
Snapshots, diffs, approvals, and rollback checkpoints help keep channel changes reviewable before they touch production.
Run it inside your network, connect multiple Mirth servers, and give operators a single place to monitor, troubleshoot, and deploy.
Free is read-only. Every paid self-hosted tier can make guarded Mirth changes, with higher tiers adding AI, monitoring depth, scale, and support.
Read-only Mirth access only. Community/self-service
Guarded Mirth changes included. Self-service plus basic email
Guarded Mirth changes included. Email support and one-click updates
Guarded Mirth changes included. Priority support, offline updates, support bundles
For teams that do not want to run Ubuntu themselves, MirthDash can be operated as a managed private appliance with automated DNS, SSL, updates, and health checks. Mirth can stay private through self-hosting, a local agent, VPN, or strict firewall rules.
Managed single-tenant appliance with automated DNS, SSL, updates, and basic monitoring.
Priority managed appliance for higher-volume teams that want deeper monitoring and support bundles.
Add another isolated hosted appliance for an extra environment, region, or customer boundary.
Start self-hosted, move to a managed private appliance when you want us to run it, then add the local agent path when you want SaaS convenience without inbound firewall changes.
Self-hosted appliance Managed private appliance Cloud UI + local agent