Zen Mesh Documentation
Status: PUBLIC_CONTRACT_DRAFT. Page status is noted per capability. Not a production-live claim.
Welcome to the Zen Mesh documentation. Zen Mesh delivers webhooks and events to private networks — no inbound ports, no VPN, no kernel modules.
Start Here
| If you are... | Start here |
|---|---|
| New to Zen Mesh | What is Zen Mesh? — overview, architecture, and evaluation path |
| New evaluator | Customer Journey — full onboarding map |
| First 15 minutes | First 15 Minutes — structured evaluator walkthrough |
| Deploying | Quick Start — UI-first setup in the dashboard |
| Checking status | Current Status — per-capability maturity matrix |
| Evaluating fit | Use Cases — see if Zen Mesh fits your needs |
Learn the Model
| Topic | Page |
|---|---|
| Runtime objects | Zen Mesh Concepts — template, blueprint, flow, endpoint, target, trace, evidence |
| Control surfaces | Control Surfaces — UI, Customer API, MCP, CLI, Git |
| Traffic lifecycle | Traffic Lifecycle — endpoint → flow → attempt → DLQ → retry → replay → trace → evidence |
| Evidence and trust | Evidence and Trust — Integrity receipts, trace/evidence relationship, non-claims |
Build and Evaluate
| Topic | Page |
|---|---|
| API deep dive | API Overview — all API surface groups, maturity, public-contract boundary |
| API status by group | API Status Matrix — per-group read/write maturity |
| UI to API map | Reference: UI/API Map — UI area to API route to status |
| Customer API | Customer API — programmable contract surface with endpoint-group-level read/write status |
| MCP | MCP Overview — AI agent and operator tool surface |
Operate and Troubleshoot
| Topic | Page |
|---|---|
| Delivery failures | Delivery Failures — failure classification, retry, recovery |
| DLQ | Dead Letter Queue — failed delivery preservation and recovery |
| Retry | Retry — single and batch retry |
| Replay | Replay — event replay from retained payload |
| Troubleshooting | Troubleshooting First Delivery — symptom → cause → action |
| Traces | Traces / Evidence Spine API — delivery trace spine |
| Saved Payloads | Test/template payloads (see Delivery section) |
Trust and Evidence
| Topic | Page |
|---|---|
| Non-claims | Non-Claims — explicit scope boundaries |
| Current Status | Current Status — single-source capability status matrix |
| Evidence overview | Evidence Overview — index of all evidence areas |
| Runtime evidence | Runtime Convergence — delivery-mode convergence, relay, and topology evidence |
| Trust evidence | Trust Lifecycle — enrollment, mTLS, and trust evidence |
| Validation map | Validation Map — evidence mapping and validation status |
| Evidence integrity | Evidence Integrity — evidence mechanism and integrity boundaries |
| Compliance | Compliance-to-Feature Graph — NIST, SOC2, ISO, PCI-DSS, HIPAA |
Machine-Readable
| Resource | Location |
|---|---|
| Capability Manifest | manifest.json |
| Compliance Map | compliance-map.json |
| Non-Claims | non-claims.json |
| AI Context | llms.txt |
| Evidence index (www) | https://www.zen-mesh.io/evidence |
| Full Context | https://www.zen-mesh.io/llms-full.txt |
Also Available
- Customer API — programmable contract surface with endpoint-group-level read/write status
- MCP — Model Context Protocol server for programmatic access
See Current Status for plan readiness by capability. All proofs are local/sandbox unless stated otherwise.