A self-hosted, PHI-safe interface engine
MessageFoundry runs entirely on your own infrastructure — on-premises or in your private cloud. PHI never leaves your environment: no vendor cloud, no third-party processor, and no telemetry of message contents. You hold the data, the keys, and the network.
What self-hosting means in practice
PHI stays on your infrastructure
Self-hosted isn't a deployment option bolted onto a cloud product — it's the whole model.
- No vendor cloud, no processor — message contents are never sent to a managed service.
- No telemetry of PHI — you control what, if anything, leaves your network.
- You hold the keys — message bodies are encrypted at rest with AES-256-GCM in your store.
Runs where your data lives
One engine, your environment — a data center, a VM, or your private cloud account.
- Installs from PyPI —
pip install messagefoundry, on Python 3.14+. - Zero-config on SQLite, scaling to PostgreSQL or SQL Server for production.
- Runs headless, including as a long-lived Windows service; one config repo drives every environment.
Secure by default
- TLS enabled by default (TLS 1.2+, incl. MLLP-over-TLS); plaintext is supported for endpoints that can't do TLS, within your secure network perimeter.
- Authenticated & audited — local accounts, MFA, Active Directory, RBAC, and a tamper-evident audit trail.
- Built to recognized standards — NIST SSDF, the HIPAA Security Rule (800-66), and an OWASP ASVS Level 3 self-assessment. See the evidence →
No lock-in, no per-interface fees
- Open source under AGPL-3.0 — read every line, run as many interfaces as you like.
- No cloud subscription and no per-interface licensing — your interfaces are plain Python in your own repo.
- A low-cost commercial license is available from the non-profit when copyleft terms don't fit. Licensing →
Data sovereignty, by construction. With a cloud or iPaaS engine, your PHI flows through someone else's systems. With MessageFoundry it doesn't move at all — the engine comes to your data. That's what PHI-safe means here. Compare the models →
Related guides
Frequently asked questions
Is MessageFoundry self-hosted?
Yes. MessageFoundry runs entirely on your own servers — on-premises or in your private cloud. It installs from PyPI, starts zero-config on SQLite, and scales to PostgreSQL or SQL Server. There is no vendor cloud and nothing is sent to a managed service.
What does PHI-safe mean?
Because MessageFoundry is self-hosted, PHI never leaves your infrastructure. There is no third-party processor and no telemetry of message contents — you hold the data, the encryption keys, and the network. Message bodies are encrypted at rest with AES-256-GCM.
Can I run MessageFoundry on-premises or in my own private cloud?
Both. MessageFoundry runs headless wherever your data lives — a hospital data center, a VM, or your own private cloud account. It can run as a long-lived Windows service, and a single config repository can drive Test, Production, and more.
Does MessageFoundry support a HIPAA-compliant deployment?
Yes — compliance is a property of your whole deployment, and MessageFoundry is built to support it: self-hosted PHI, TLS enabled by default, message bodies encrypted at rest, authenticated and audited access, and controls mapped to the HIPAA Security Rule (NIST 800-66). You stay in control of your environment.