Skip to content
VZU
VZU OS Agent running Agent 03 of 12

KAI.

Backend + infra engineer.

Kai is the VZU Stack agent. Full-stack engineering: database, API, queue, worker, frontend, infra, deploy, monitoring. The agent you call when the work is foundational.

  • Capability

    VZU Stack

  • Category

    engineering

  • Runtime

    NetWit OS

  • Tools

    5

AGENT · 03
engineering

Powers

VZU Stack

stack

The role

What KAI does

KAI is the dedicated agent behind VZU Stack. It runs every time the operator briefs the vzu stack capability. It owns the goal, the toolset, the memory, the audit trail.

The goal

What KAI is trying to achieve

"Stand up a multi-tenant, production-grade full-stack system with database, API, frontend, infra, monitoring, and observability."

The capability

What it powers

KAI powers the VZU Stack capability in the VZU family.

Visit stack.vzu.ca →

The toolset

5 MCP actions KAI can call.

Every action is exposed as an MCP server (Model Context Protocol). The agent receives the action manifest, decides which action to call, calls it, and continues reasoning. The audit trail records every call.

  • mcp.db.migrate

    Apply database migrations

  • mcp.api.deploy

    Deploy the API to staging/prod

  • mcp.queue.worker

    Start the background worker

  • mcp.infra.terraform

    Apply infrastructure as code

  • mcp.monitor.grafana

    Set up monitoring dashboards

The memory schema

What KAI remembers between calls.

  • The data model
  • The API contract
  • The infra config
  • The monitoring config

The brief

A real demo brief.

"Stand up a multi-tenant SaaS API on Cloudflare Workers. PostgreSQL via Hyperdrive. R2 for assets. Queues for async work."

Below is KAI's actual execution trace for this brief — every step, every MCP call, every observation, every audit trail entry.

The execution trace

What KAI did.

Live execution trace from a recent KAI run. The agent was briefed: Stand up a multi-tenant SaaS API on Cloudflare Workers. PostgreSQL via Hyperdrive. R2 for assets. Queues for async work.. Each line is a step. Particles flow on the rail. The audit trail streams at the bottom.

kai@vzu-os — trace.log live
  1. 01
    kai read brief

    read brief

  2. 02
    kai thinking: multi-tenant saas. cloudflare workers + hyperdrive. 8-12 weeks.

    thinking: multi-tenant saas. cloudflare workers + hyperdrive. 8-12 weeks. : multi-tenant saas. cloudflare workers + hyperdrive. 8-12 weeks.

  3. 03
    kai mcp.db.schema

    tenants, users, organizations, plans, subscriptions, events

  4. 04
    kai mcp.db.migrate

    applied 12 migrations to staging

  5. 05
    kai mcp.api.deploy

    hono + trpc + zod, deployed to workers

  6. 06
    kai mcp.queue.worker

    queues: email, billing, webhooks, exports : email, billing, webhooks, exports

  7. 07
    kai mcp.infra.terraform

    r2 buckets, hyperdrive bindings, d1 for flags

  8. 08
    kai mcp.monitor.grafana

    dashboards: requests, errors, latency, queue depth : requests, errors, latency, queue depth

  9. 09
    kai ship. 10 weeks. 47 services. 99.97% uptime. done

    ship. 10 weeks. 47 services. 99.97% uptime.

kai@vzu-os $

Audit trail · 7 entries

streaming
  • T+00:00:00 brief.received 01
  • T+00:01:30 architecture.drafted 02
  • T+00:04:00 data.model.finalized 03
  • T+02:00:00 db.migrations.applied 04
  • T+05:00:00 api.deployed.staging 05
  • T+08:00:00 infra.applied 06
  • T+10:00:00 brief.completed 07

The numbers

KAI, by the numbers.

Four KPIs. Animated count-up on scroll. Sparkline shows the recent trend. Delta indicator shows the trajectory.

  • KPI · 01 now

    10 weeks

    Median brief duration

    13%
  • KPI · 02 now

    47

    Services deployed

    9%
  • KPI · 03 now

    99.97%

    Uptime

    17%
  • KPI · 04 now

    12

    Migrations

    8%

Get in touch

Brief KAI.

The orchestrator handles the routing, the audit trail, and the enforcement. KAI handles the work. The operator owns the goal.