For security reviewers
Raw prompts never leave your boundary.
The architecture, isolation model and comparison your security and vendor risk teams ask for. Your data plane runs in infrastructure dedicated to your organization and owns the audit trail.
Two planes. One trust boundary.
Your data plane runs in single-tenant infrastructure dedicated to you, and it owns the audit trail. The shared control plane distributes hash-pinned policy bundles and receives hashed metadata, never raw payload.
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.
Dedicated infrastructure for every customer and environment.
No shared data plane, no pooled storage, no other institution's traffic in your boundary. Fully Managed, Self-Hosted or Sovereign, the isolation is the same; the difference is who runs the infrastructure.
| 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.
Proxy source code is available to customers for review under mutual NDA.
Deployment modesBy the numbers
Added latency, p95
<0ms
Measured under sustained load, October 2026
Requests in the load test
0.0M
August 2026 campaign, zero failures
Retention floor
0yr
Write-once archive in Fully Managed production, per FINRA 24-09
Change to deploy
0env var
No SDK swap and no rewrite. About a day managed; self-hosted in your environment
Examiner-grade evidence from live traffic.
Meilynx enforces policy inline and keeps a record an examiner can verify on their own. The table compares it with the tools security teams already run.
| Capability | Meilynx | DLP / CASB | SIEM / log export | Build it yourself |
|---|---|---|---|---|
| Enforces policy inline, before the call leaves your perimeter | Yes | Partial | Partial | |
| Reads prompt and response content, including PII and MNPI | Yes | Partial | Partial | |
| Write-once, tamper-evident record rather than a log export | Yes | |||
| Curated examination packages per framework | Yes | |||
| Integrity an outside auditor can re-verify on their own | Yes | |||
| Detects agent drift and gates high-risk actions behind a second approver | Yes | Partial | ||
| Single-tenant data plane per customer and environment, never pooled with another institution | Yes | Partial |
A category comparison, not a product-by-product rebuttal. Most tools can log what your AI did. The rows below the first two are where examination evidence gets produced, or does not.
You can check the record yourself. An examiner or your own auditor can recompute the hash chain with an open verifier at any time. The proof does not depend on trusting Meilynx.
Independent verificationBring your security questionnaire
A 15-minute walkthrough of the architecture, the isolation model and the audit trail, with your security team in the room.