Summary
peat-mesh-node is a single-formation tactical node. Enterprise/cloud deployments need a dedicated gateway service — peat-gateway (separate repo) — that provides:
- Multi-org tenancy — multiple organizations, each with independent formations (app IDs), isolated key material, per-org IDAM, and scoped CDC sinks
- CDC (Change Data Capture) — stream CRDT document changes to Kafka, NATS, Redis Streams, webhooks
- AuthZ pass-through — per-org OIDC/SAML federation for enrollment (Keycloak, Okta, Azure AD, CAC/mTLS)
- Admin UI — SvelteKit web dashboard for org/formation management, topology, documents, certs, CDC monitoring
- Zarf/UDS packaging — first-class UDS capability with Helm chart, UDS Package CR, SSO, network policies, Grafana dashboards, air-gapped bundle
Architecture
See ADR-0011 for full design.
Separate repo (defenseunicorns/peat-gateway) depending on peat-mesh as a library. Feature-flagged sinks (kafka, nats, redis-streams, webhook), identity providers (oidc, saml), and backends (postgres).
Implementation Phases
Phase 1: Foundation
Phase 2: CDC
Phase 3: Identity Federation
Phase 4: Admin UI
Phase 5: Zarf / UDS Packaging
Phase 6: Production Hardening
Summary
peat-mesh-nodeis a single-formation tactical node. Enterprise/cloud deployments need a dedicated gateway service —peat-gateway(separate repo) — that provides:Architecture
See ADR-0011 for full design.
Separate repo (
defenseunicorns/peat-gateway) depending onpeat-meshas a library. Feature-flagged sinks (kafka, nats, redis-streams, webhook), identity providers (oidc, saml), and backends (postgres).Implementation Phases
Phase 1: Foundation
peat-gatewayrepoPhase 2: CDC
Phase 3: Identity Federation
Phase 4: Admin UI
Phase 5: Zarf / UDS Packaging
Phase 6: Production Hardening