The same proxy in the data path that gives you cost per successful outcome also enforces policy at the edge — model allow-lists, PII redaction, prompt safety — and produces the tamper-evident audit log your examiners will actually accept.
The 10-minute talk you just heard was about one signal. The architecture underneath does three jobs.
A note from the founder
I’m Cassio. After more than a decade building infrastructure at Microsoft and Google — most recently as a tech lead on Google Cloud’s capacity safety team — I started Meilynx to build the AI governance layer I wished my own teams had. If that’s a problem you’re sitting with, I’d like to hear about it.
cassio@meilynx.com— direct, not a CSM inbox
Meilynx is a transparent proxy between your applications and every LLM provider — OpenAI, Anthropic, Azure, Google. One env-var change routes traffic through it; no SDK swap, no app rewrite. From that single position in the data path it enforces policy pre-request and post-response, writes a hash-chained audit log your examiners will accept, and attributes spend to teams, features, and outcomes. Raw prompts and responses never leave your perimeter. The proxy is going Apache 2.0 at SOC 2 GA — design partners get source access today under mutual NDA.
Inbound
Request
Outbound
Provider
Audit substrate
ClickHouse · WORM archive · Cryptographic hash chain
Every request, response, and policy decision captured to immutable storage in your environment. Examination-ready evidence — never delegated to the control plane.
Request
From your application
Policy
Model allow/deny · schema
PII / MNPI
Real-time detection
Cost
Per-request · budgets
Tools
Agent allow/deny
Provider
OpenAI · Anthropic · Azure · Google
Audit substrate
ClickHouse · WORM archive · Cryptographic hash chain
Capturing every call · 7-year retention
<50ms p99 added latency. Shadow mode supported for safe rollout.
You came for the cost story. The proxy ships the FinOps slice today: outcome ingestion, hierarchical budgets, pre-request cost gates, and model-mix recommendations from observed traffic. This is the surface you can deploy this week and demo next.
Spend per successful outcome — by feature, customer segment, and model. Hierarchical budgets with pre-request gates that block expensive calls before they happen. This is the FinOps slice of the talk.
The same proxy in the data path that gives you cost-per-outcome also enforces policy pre-request and post-response, and produces a tamper-evident audit log examiners will accept. When governance lands on a security review, this is the architectural answer.
Pre-request and post-response rules in the data path. Block, redact, mask, or log. Shadow mode on every rule for production safety.
SHA-256 hash chain across every audit record — sequence-numbered and cryptographically linked. Pluggable WORM backend in the customer's environment. Direct mapping to named regulatory controls.
Full taxonomy with industry mappings lives at meilynx.com/#regulations.
Per-customer isolated infrastructure in every mode.
The proxy and audit substrate run in infrastructure dedicated to your organization — managed by us, run by you, or in a Bring-Your-Storage configuration where the audit lands in your store. In every case the trust boundary holds: only telemetry metadata — token counts, rule outcomes, latencies — reaches our control plane. Raw payload never does.
FinOps leaders see the cost story before the security review starts — and you're often the one who brings the architecture conversation to your CISO. If your team is sitting with the question, the design partner program is how we make those conversations productive. Direct roadmap influence, named engineering support, source access under mutual NDA today, and 6 months of free use — in exchange for honest feedback and a willingness to be referenced when we both have something worth talking about.
What you get
What we ask
Strong fit
We’d rather go deep with five than shallow with twenty.
Apply to Cohort I
No form. No qualification gate. Founder-to-buyer conversation. We respond within 48 hours.
For the FinOps-only visitor
If you’re here for the FinOps story specifically and governance isn’t your problem to solve — the cost correlation capability is available standalone. Reach out at hello@meilynx.com — no design partner commitment required.
