Getting Started
Architecture
Control plane, data plane, and agent mesh — designed for multi-cloud enterprises.
Updated 2026-07-19
Zynvora separates a globally available control plane from customer-owned data planes. Metadata, auth, and orchestration stay in the control plane; data processing stays in your VPC or SaaS data warehouses.
Control plane
- Identity, SSO, RBAC, audit, and policy engines
- Pipeline / workflow orchestration and agent scheduling
- Zynvora Mission Control dashboards, billing, and FinOps aggregation
- Catalog, lineage, and quality metadata services
Data plane
- Connectors to warehouses, lakes, streams, and SaaS APIs
- Optional Zynvora runners in your Kubernetes clusters
- Notebook and GPU compute pools with budget guards
Agent mesh
Specialized agents collaborate through the Chief AI Orchestrator along a fixed requirement pipeline: Planner → Architecture → Security → Data Engineer → Validation → human Approval → Deploy → Monitor → Optimize. High-risk actions never bypass the approval gate. Phase D closes the loop with autonomous RCA, remediation (retry / failover / regenerate SQL), and continuous FinOps optimization when production fails.
| Layer | Residency | Customer control |
|---|---|---|
| Control plane | Zynvora regions or self-hosted | SSO, policies, encryption keys (CMK) |
| Data plane | Customer cloud / on-prem | Network, compute, data access |
| Agents | Either (policy gated) | Tool scopes, approval workflows |
Need help?
Talk to Support or book an enterprise workshop with Solutions Engineering.