About Meibel

Built because the governance gap was obvious — and nobody was closing it at the right layer

Meibel started in 2025 after watching enterprises deploy LLMs against production data with no redaction, no audit log, and no tenant boundaries — then discover the gap when a compliance review asked for records that didn't exist.

Kevin McGrath, CEO & Co-Founder of Meibel
Founder & CEO

Kevin McGrath

CEO & Co-Founder

Kevin spent more than a decade in enterprise data governance and security. His earlier career included a compliance engineering role at a regulated financial services firm, where he spent three years building the internal tooling that ingestion pipelines needed to satisfy SR 11-7 model risk requirements — a context that gave him an unusually precise read on what regulated organizations actually ask for in an AI audit package. He then led GRC tooling at a multi-tenant SaaS, where the problem of isolating customer data across a shared LLM deployment was not hypothetical.

In early 2025, after watching two separate enterprise teams hit the same wall — deploying LLMs against production data without a policy layer, then scrambling to reconstruct prompt histories for a compliance review — he founded Meibel in Denver. The core insight that shaped the architecture: governance controls that depend on application developers making the right choices fail at scale. The control has to live at the infrastructure layer, between the application and the model API, where it cannot be bypassed by a developer shortcut or a missed code review.

Meibel is in private beta with three enterprise organizations across financial services, healthcare, and public sector. Kevin handles all security and enterprise inquiries directly. That is not a marketing claim about founder responsiveness — it is a function of the trust level this product category requires.

The team

A small team with backgrounds in distributed systems, enterprise data compliance, and LLM infrastructure.

Kevin McGrath
Kevin McGrath
CEO & Co-Founder

10+ years in enterprise data governance and compliance engineering. Earlier roles in regulated financial services and multi-tenant SaaS GRC tooling.

Infrastructure engineer, Meibel
Infrastructure Lead
Co-Founder & CTO

Distributed systems background. Designed tenant isolation architecture and audit log write path.

ML engineer, Meibel
ML Engineering
ML Engineer

NLP and entity detection background. Built the PII redaction model suite and custom pattern engine.

Design principles we won't compromise
Infrastructure, not application

Governance controls that depend on application developers making the right choices will fail. Infrastructure-layer enforcement is the only architecture that holds at scale.

Auditors ask for records, not promises

The organizations Meibel serves face real audits. We build tools that produce evidence, not attestations. If you can't query it, it doesn't count.

Security is a design constraint, not a feature

Tenant isolation and PII redaction aren't add-ons — they're the architecture. Every API is designed with the assumption that data from one context must never appear in another.

Founder-level accountability

Security inquiries go directly to Kevin. We're small enough to give enterprise customers direct access, and we believe that matters for the trust level this niche requires.

Meibel team working on LLM governance infrastructure
Working from our Denver office — 3001 Brighton Boulevard, Suite 240.

Thirty minutes. Your LLM deployment. Kevin on the call.

Request access and we'll walk through your specific compliance scenario — redaction taxonomy, tenant model, audit log schema — before you commit to anything.