VZU Customer · SaaS · Vancouver
VZU AI Pods.
A Vancouver SaaS company uses VZU AI Pods (Developer + Tester) as a subscription delivery squad. The pods run on the Netwit Agentic OS, with token-based metered capacity and a human supervisor in the loop. The pods write and test code against the operator's repo, with the operator setting the gates for what ships.
The story
What the operator is doing.
A Vancouver SaaS company uses VZU AI Pods (Developer + Tester) as a subscription delivery squad. The pods run on the Netwit Agentic OS, with token-based metered capacity and a human supervisor in the loop. The pods write and test code against the operator's repo, with the operator setting the gates for what ships.
Customer details (company name, contact, full deployment scope) are shared under NDA. The case study above describes the work, the deployment model, and the result.
The deployment
What shipped.
- ·Developer + Tester pods
- ·Token-based metered capacity
- ·Human-supervised, Netwit runtime
The engagement
How the work happened.
The deployment: the runtime is configured for the operator's specific workflow. The MCP servers are built for the operator's specific systems. The RBAC profile is set to the operator's specific roles. The audit trail is configured for the operator's specific regulator. The deployment is a 2-4 week engagement, with the operator's team working alongside the VZU team. The deployment is the proof.
The economics: the operator pays for the runtime, the model inference, and the audit trail storage. The pricing is published, the math is published. The operator can estimate their bill before the engagement. The economics are the right answer for the operator who has tried to build this in-house and has decided that building is more expensive than buying.
The shape of the engagement: weekly working sessions with the VZU team. Daily Slack access. A shared Notion for the architecture, the audit trail, the deployment runbook. A staging environment for the operator to test against, separate from production. A 30-day production pilot before the annual contract. The shape of the engagement is the shape of a working relationship.
What the operator gets: a production deployment of the brand on the Netwit runtime, with the audit trail on from day one, with the RBAC profile set, with the MCP servers in place, with the operator's team trained on the runtime. The operator gets a runtime, not a vendor relationship. The operator gets the source of truth on the audit trail. The operator gets the build, not the lock-in.
The engagement
How the work happened.
The deployment: the runtime is configured for the operator's specific workflow. The MCP servers are built for the operator's specific systems. The RBAC profile is set to the operator's specific roles. The audit trail is configured for the operator's specific regulator. The deployment is a 2-4 week engagement, with the operator's team working alongside the VZU team. The deployment is the proof.
The economics: the operator pays for the runtime, the model inference, and the audit trail storage. The pricing is published, the math is published. The operator can estimate their bill before the engagement. The economics are the right answer for the operator who has tried to build this in-house and has decided that building is more expensive than buying.
The shape of the engagement: weekly working sessions with the VZU team. Daily Slack access. A shared Notion for the architecture, the audit trail, the deployment runbook. A staging environment for the operator to test against, separate from production. A 30-day production pilot before the annual contract. The shape of the engagement is the shape of a working relationship.
What the operator gets: a production deployment of the brand on the Netwit runtime, with the audit trail on from day one, with the RBAC profile set, with the MCP servers in place, with the operator's team trained on the runtime. The operator gets a runtime, not a vendor relationship. The operator gets the source of truth on the audit trail. The operator gets the build, not the lock-in.
The handoff
From pilot to production.
The handoff to the operator: after the pilot, the operator's team is trained on the runtime. The training is 2 days, on-site or remote, with a real working session. The training covers the architecture, the audit trail, the RBAC, the MCP integration, the deployment model. The training is the handoff. The training is when the operator takes ownership.
The post-handoff state: the operator owns the runtime. The VZU team is on-call, but the operator's team runs the day-to-day. The audit trail is owned by the operator. The RBAC is set by the operator. The MCP servers are built by the operator (or by VZU on contract). The operator is the operator. The runtime is the runtime. The handoff is the proof.
Similar work?
Brief VZU on a similar brief.
The same shape, on a different operator. Two-week pilot, fixed-fee, with a real ship date.