Capability
Per-customer isolation, every mode.
Every mode deploys the proxy into infrastructure dedicated to your organization. The modes differ in who operates it and where the control plane runs; your data is never mixed with anyone else's.
Single-tenant isolation by design.
The data plane always lives in customer-isolated infrastructure and owns your audit trail. In Fully Managed and Self-Hosted, only hashed, aggregate metadata reaches the Meilynx control plane, and raw payload never does. In Sovereign the control plane runs inside your boundary too, and nothing reaches Meilynx.
Managed or self-hosted · isolated either way
Application
Your apps & agents
Meilynx Proxy
Validators · streaming · audit emission
Audit Trail
WORM archive · hash chain · examination export
Raw prompts & responses never leave this boundary.
Per-customer isolated data plane in every deployment mode
Telemetry
metadata
Bundles
policy-as-code
Managed SaaS
Policy authoring
Versioned bundles · policy-as-code
Compliance console
Posture · waivers · examination packages
Telemetry rollup
Metadata only · token counts · rule outcomes
No raw payload data ever reaches the control plane.
Pick who operates it.
Start Fully Managed for the fastest path to a governed data path, choose Self-Hosted where residency requires it, and Sovereign where nothing may leave your boundary.
~1 day
Fully Managed
Meilynx operates the proxy inside per-customer isolated infrastructure. The fastest path to a governed, audited data path.
On request
Self-Hosted
You operate the proxy and the audit storage in your own environment, for strict-residency deployments, with Meilynx operating the control plane.
Per engagement
Sovereign
You operate the proxy, the control plane and the verifier inside your own boundary, with no connection to Meilynx, for air-gapped and disconnected environments. Keys stay in your KMS or HSM.
What changes between modes.
A per-mode view of what runs where, and who operates it.
| Dimension | Fully Managed Meilynx operates per-customer infrastructure · ~1 day | Self-Hosted Customer operates the proxy and storage | Sovereign Customer operates everything, disconnected |
|---|---|---|---|
| Control plane | Meilynx Live | Meilynx Live | Customer, inside your boundary Per engagement |
| Connection to Meilynx | Policy pull and metadata only Live | Policy pull and metadata only Live | None Per engagement |
| WORM immutability | Retention-locked object storage Live | Customer-managed object storage Customer | Your object storage, write-once Per engagement |
| Retention floor | 6 yr prod · 30 d staging · 1 d test (FINRA 24-09) Live | Customer-set (proxy default: 90 d) Customer | Customer-set Customer |
| Encryption at rest | AES-256-GCM + per-customer CMEK Live | Customer-managed Customer | Your KMS or HSM Per engagement |
| Integrity Pack | Included Live | Customer-operated Customer | Signed with a key you hold Per engagement |
| Verification surface | Hash chain · examiner-verifiable Live | Hash chain · customer-operated Customer | Hash chain · verified offline against your trust root Per engagement |
| Time evidence | RFC 3161 timestamps from two independent authorities Live | Public timestamp authorities, or your own Customer | Your own timestamp authority Per engagement |
| Cryptography | TLS 1.2 or later in transit Live | TLS 1.2 or later in transit Customer | FIPS 140-3 validated cryptography Per engagement |
| Proxy operated by | Meilynx Live | Customer Customer | Customer Customer |
Time evidence: a timestamp over the audit chain shows that the anchored records existed by the stated time and are unchanged since. Records written after the latest anchor, and the completeness of the record set, are outside what a timestamp attests.
Read the proxy you run.
Customers get source access to the proxy under mutual NDA, so a security reviewer can answer what the binary does before it goes into the data path.
Supply-chain trust
The first question a security reviewer asks, what this binary does, gets answered by reading the code under NDA, not by taking our word for it.
Find the right mode for your organization
We'll map your residency and operating constraints to Fully Managed, Self-Hosted or Sovereign.