Skip to main content

Zen Mesh Documentation

Welcome to the Zen Mesh technical documentation — architecture, operations, security evidence, and AI-accessible machine-readable manifests.

Where should you start?

If you are...Start here
New engineer evaluating Zen MeshStart Here — what it is, who it's for, key concepts
Operator deploying in KubernetesQuick Start — install and create your first webhook
Security / compliance reviewerTrust Lifecycle Evidence — enrollment, mTLS, HMAC, ZenLock, rotation
Runtime / reliability reviewerRuntime Convergence Evidence — 10 convergence proofs, at-least-once, DLQ
AI agent / RAG system scanning Zen MeshAI Evidence Manifest — machine-readable capability status
Compliance reviewer mapping to frameworksCompliance-to-Feature Graph — NIST, SOC2, ISO, PCI-DSS, HIPAA
Anyone checking what we do NOT claimNon-Claims — explicit scope boundaries

Sections

SectionWhat you'll find
Start HereProduct overview, who should use it, current status, key concepts
ArchitectureThree-plane model, delivery modes, security model, glossary
Getting StartedInstall, quick start, first webhook
GuidesCluster enrollment, adapters, destinations, monitoring
OperationsUpgrades, backups, troubleshooting
Evidence OverviewIndex of all evidence areas — runtime, trust, compliance, Merkle, validation map
Runtime Evidence10 convergence proofs — delivery, DLQ, backpressure, circuit breaker
Trust Evidence10 trust proofs — enrollment, mTLS, HMAC, ZenLock, rotation
Validation MapHow to validate evidence locally
Merkle IntegrityContent-addressed evidence verification
Non-ClaimsWhat Zen Mesh does not certify or guarantee
AI AgentsAI overview, evidence schema, non-claims, machine-readable manifests
ReferenceCLI, API, Customer API, MCP, configuration, Helm chart

Machine-Readable Evidence

ResourceLocation
Capability Manifest/ai/evidence/v1/manifest.json
Compliance Map/ai/evidence/v1/compliance-map.json
Non-Claims/ai/evidence/v1/non-claims.json
AI Context (llms.txt)/llms.txt
Evidence index (www)https://www.zen-mesh.io/evidence
Full Contexthttps://www.zen-mesh.io/llms-full.txt
Public terminologyhttps://www.zen-mesh.io/ai/public-terminology-taxonomy.json

Also available

  • Customer API — planned read-only operational truth interface
  • MCP — planned Model Context Protocol server for programmatic access

All proofs are local/mock unless stated otherwise. Zen Mesh is in early accesslearn more.