VZU OS · The Agent Operating System
12 specialized agents. One orchestrator. MCP-native integrations. SOC 2 / HIPAA / ISO 27001 posture. Audit trail by default. The runtime that powers every VZU capability, every VZU brand, every VZU engagement.
VZU OS is the agent operating system that powers the VZU family. It runs 12 specialized agents — Atlas, Vega, Kai, Nova, Pixel, Echo, Sketch, Launch, Sentinel, Oracle, Quill, and Hunter — under a central orchestrator. The agents communicate via MCP (Model Context Protocol), enforce RBAC at the agent level, and produce an audit trail by default. VZU OS is operated by Virtual Zero Unbound Inc. and runs on the NetWit Agentic OS runtime in cloud, hybrid, or air-gapped on-prem.
The orchestrator
The VZU orchestrator is a multi-agent runtime. It takes a brief, decomposes it into subtasks, routes each subtask to the right agent, observes the result, and replans if needed. The orchestrator enforces RBAC at the agent level and produces a complete audit trail for every brief.
Click any agent to see its execution trace.
Live demo
Below is a real agent run, slowed down so you can see every step. Tap the run button, or just scroll the demo into view. Each step lights up. The audit stream fills in. The cursor blinks. This is what the runtime looks like from the inside.
Brief
Build a multi-tenant booking dashboard for service businesses. Calendar views, customer management, Stripe Connect integration.
read brief
thinking: brief is "build a multi-tenant booking dashboard". scope: 2 weeks.
mcp.data.schema > generate schema: tenants, services, customers, bookings, payments
thinking: stripe connect requires 2-day payout. need to scope webhook handler.
mcp.code.generate > next.js 15 + prisma + stripe-connect-express
mcp.code.generate > component library: Calendar, CustomerList, BookingForm
mcp.deploy.staging > ship to staging.atlas.vzu.ca
mcp.test.run > 47 integration tests passing
ship. 14 days. 4 deploys. audit trail: 23 entries.
Audit stream · 0/8
How VZU OS works
Step · 01
A real brief from a real operator. The goal, the data, the regulator, the deadline. The brief is the contract.
Step · 02
The orchestrator decomposes the brief into subtasks, routes to the right agents, and sets the audit posture.
Step · 03
The agents run. Each one calls MCP servers, observes, replans. Every call is logged in the audit trail.
Step · 04
The orchestrator reviews the work, the audit trail, and the operator's RBAC. The result is signed, sealed, delivered.
Orchestration patterns
The VZU orchestrator supports three core patterns. The right pattern depends on the brief. Each pattern is animated — particles flow, the orchestrator pulses, supervisors loop back.
Sequential hand-off. Each step waits for the prior step to complete. The simplest pattern. The most auditable.
Use case
Brief: build the schema, then build the API, then build the UI. Atlas (schema) → Kai (API) → Nova (UI).
Independent subtasks run in parallel. Results combined by the orchestrator. Used when the brief splits cleanly.
Use case
Brief: refactor backend, frontend, and audit at once. Kai + Nova + Sentinel in parallel. Combined by the orchestrator.
A delegates, observes, re-delegates. The most powerful pattern. The most audited.
Use case
Brief: build a multi-tenant system with auth, billing, and observability. Atlas (supervisor) → {Kai, Vega, Sentinel}. Atlas re-plans until the brief is met.
The network
Tap any agent to see its trace, its toolset, and its audit trail. The orchestrator sits at the center; the agents work the edges.
The runtime, visualized
Every brief, every audit trail, every MCP call — visualized below. The orchestrator moves between relay, parallel, and supervisor patterns based on the brief. The agents are alive, the audit trail is on.
An execution trace
Below is the actual execution trace from a recent VZU OS run by Atlas (VZU Build). The agent was briefed: build a multi-tenant booking dashboard. Here is every step it took, the audit trail it produced, and the KPIs it hit.
read brief
thinking: brief is "build a multi-tenant booking dashboard". scope: 2 weeks. : brief is "build a multi-tenant booking dashboard". scope: 2 weeks.
generate schema: tenants, services, customers, bookings, payments : tenants, services, customers, bookings, payments
thinking: stripe connect requires 2-day payout. need to scope webhook handler. : stripe connect requires 2-day payout. need to scope webhook handler.
next.js 15 + prisma + stripe-connect-express
component library: Calendar, CustomerList, BookingForm : Calendar, CustomerList, BookingForm
ship to staging.atlas.vzu.ca
47 integration tests passing
ship. 14 days. 4 deploys. audit trail: 23 entries. : 23 entries.
Audit trail · 8 entries
14 days
Median brief duration
12,400
Avg lines of code
8
Deploys per brief
100%
Tests passing
The integration story
Every VZU agent calls its work through MCP — Model Context Protocol. MCP is the open standard for tool calling. Each MCP server advertises a manifest of actions (name, description, input schema, output schema). The agent receives the manifest, decides which action to call, calls it, and continues reasoning.
This is the cleanest way to call an action. Stateless. Structured inputs. Structured outputs. Explicit error semantics. Fast response times. The patterns that work in production. The patterns that fail in production are also narrower — stateful actions that hold long-running connections, actions that depend on user-specific context the agent doesn't have, ambiguous error responses, actions that are too slow for an interactive loop.
The VZU OS enforces the patterns that work. Every MCP action is stateless. Every action has a single responsibility. Every action returns a typed result. Every action has a fast response time. The audit trail records every call.
The compliance posture
VZU OS is the compliance boundary. Access control is enforced at the agent level, not the user level. Change management is enforced on prompts, models, and action definitions, with every change versioned and auditable. Monitoring is enforced on every action call, every model call, every agent decision, with the full conversation history retained for the auditor.
The runtime ships as a binary. Cloud (Canadian, US, or EU region). Hybrid (runtime on operator hardware, model API-called). Fully on-prem (runtime, model, and tools on operator infrastructure, including air-gapped). The same code, the same audit trail, the same RBAC, regardless of where it runs.
The shape
12
Specialized agents
one orchestrator
3
Orchestration patterns
relay · parallel · supervisor
50+
MCP actions
across the runtime
1
Runtime
NetWit Agentic OS
Featured traces
Full-stack app builder.
React/Next.js engineer.
Backend + infra engineer.
Editorial UI designer.
Motion + WebGL designer.
WCAG accessibility auditor.
The full cast
Get in touch
The runtime handles the orchestration, the audit trail, and the enforcement. The operator owns the goal.