Netwit · VZU lead brand · 2026
Netwit.
The lead VZU brand. Agentic AI automation for the enterprise. Multi-agent orchestration. MCP-native integrations. RBAC at the agent level. On-prem by default.
The product
What is Netwit?
Netwit is the lead VZU brand — the agentic AI automation platform. Netwit is the runtime the other 11 brands in the VZU family ship on, and the product VZU sells to enterprise operators who need multi-agent orchestration with an enforced perimeter, a real audit trail, and a deployment model that respects the regulator.
Netwit is Vancouver-built and runs globally — in cloud, in hybrid, and fully on-prem (including air-gapped). The same runtime ships to operators in Canada, the United States, the UAE, India, the UK, and beyond, through the VZU regional entities. Netwit is the product. The regions are the routes to market.
The flagship process
How Netwit works, in five steps.
A real brief becomes a real product. The runtime handles the orchestration, the audit trail, and the enforcement. The operator owns the goal.
-
Step 01
Brief
A real brief. A real problem. A real operator. The brief sets the boundary of the engagement — what the system needs to do, what data it can touch, what regulator it answers to, and what success looks like at 90 days. Netwit ships on the brief. The brief is the contract between the operator and the runtime.
-
Step 02
Model the work
The work is decomposed into a goal, an action set (implemented as MCP servers), an audit posture, and a memory schema. The Netwit runtime gets the goal, the integrations, and the rules. The model of the work is the contract between the operator and the runtime.
-
Step 03
Orchestrate
The runtime plans the steps, dispatches the agents, observes the results, and replans. Multi-agent orchestration handles the cases where the work splits (parallel) or where a worker needs to be re-tasked (supervisor) or where the steps are strictly sequential (relay). Every call is logged in the audit trail.
-
Step 04
Enforce the perimeter
RBAC checks every action call. The audit trail records who, what, when, with which model. Compliance posture (SOC 2, HIPAA, ISO 27001, PIPEDA) is enforced by the runtime, not bolted on. The data never leaves the operator's perimeter when on-prem is selected.
-
Step 05
Operate
A quarterly or annual contract. The on-call is 24/7. The audit trail is on from day one. The runtime gets updated, the agents get retrained on real outcomes, and the operator's posture improves over time. The work compounds.
The five steps are the same regardless of the brief. The complexity lives in the runtime, not in the operator's workflow.
How this works, in plain words. The animation is decorative; the text is the source of truth.
The capabilities
What Netwit builds.
01 · Multi-agent orchestration
Relay, parallel, supervisor.
Three orchestration patterns. The runtime picks the right one per blueprint. The agent plans, invokes actions, observes results, and replans.
02 · MCP-native integrations
Every action is an MCP server.
Model Context Protocol is the first-class integration story. 150+ system integrations, typed inputs, typed outputs, full audit trail on every call.
03 · RBAC at the agent level
The agent sees what the user is allowed to see.
Permissions are enforced at the agent, not at the user. Every action call is checked against the perimeter. The audit trail records who, what, when, with which model.
04 · On-prem by default
The runtime ships as a binary.
Drop it on a server. Drop it on air-gapped hardware. Cloud, hybrid, or on-prem — the same code ships in every mode.
05 · SOC 2 / HIPAA / ISO 27001
Compliance posture, enforced.
The runtime is the compliance boundary. SOC 2 in active pursuit. ISO 27001-aligned. HIPAA-aware deployment available. PIPEDA-friendly Canadian cloud region by default.
06 · Audit trail by default
Every action has a reason.
Every reason is in the audit trail. The audit trail is on from the moment the page returns. The audit trail is the regulator\'s form.
The runtime
Four primitives, one runtime.
01 · The goal
What the operator wants done.
A goal is what the system is trying to achieve. It is given to the runtime in natural language or in a structured form. The runtime plans the steps to achieve the goal. The goal is the contract between the operator and the runtime.
02 · The actions
What the agent can invoke.
An action is what the agent can do to make progress on the goal. Every action is an MCP server. The agent reads the action list, decides which to call, calls it, gets the result, and continues. The action does not need to know how the agent is implemented. The agent does not need to know how the action is implemented.
03 · The memory
What the agent knows between calls.
A memory is what the agent retains across calls. The conversation history. The working state. The durable record. The memory is owned by the runtime, with the retention policy set by the operator. The audit trail is the long-term memory.
04 · The perimeter
What the agent is allowed to do.
A perimeter is the boundary of what the agent is allowed to do. The runtime checks every action call against the perimeter. The perimeter is set by the operator. The perimeter is what makes the system auditable. The perimeter is what the regulator sees.
The regions
Where Netwit runs.
Netwit is the product. VZU is the operating group. Netwit is built in Vancouver and ships through VZU regions across four continents. The regions are the routes to market. The runtime ships the same code to every region.
- Vancouver, Canada · CA VZU Headquarters
Where Netwit is built. Where VZU is incorporated. Where the CEO sits. The runtime ships from here, with engineering support in Bangalore.
- Dubai, UAE · AE VZU MENA region (Plex Dubai)
One of several VZU regions. Plex Dubai carries Netwit services into the MENA market — UAE, Saudi, and the wider GCC.
- Mumbai, India · IN VZU South Asia region (Wahix India)
Wahix India carries Netwit services into South Asia. Custom software, mobile, enterprise ERP/CRM, and government + healthcare IT.
- London, UK · GB VZU EMEA support
Shoreditch. VZU's Europe, Middle East, and Africa commercial region. Enterprise sales, partnerships, and the European customer base.
- Bangalore, India · IN VZU Engineering
Indiranagar. The engineering team that builds Netwit. Reports into VZU HQ in Vancouver.
Netwit is the product. Vancouver is HQ. Dubai is one of several regions. The same runtime ships the same code to every operator in every region.
How it runs
Three deployment modes, one runtime.
Mode 01
Cloud
Canadian region for PIPEDA. US region otherwise. EU region available. The fastest path to production. The default for new operators.
Mode 02
Hybrid
The runtime on the operator's hardware. The model API-called from the cloud. The data stays in the operator's perimeter. The runtime's audit trail records every cross-boundary call.
Mode 03
On-prem
The runtime, the model, and the integrations all on the operator's infrastructure. Including air-gapped. The right answer for the regulator that requires everything inside the perimeter.
The compliance posture
SOC 2 · HIPAA · ISO 27001 · PIPEDA.
SOC 2
The runtime is in active pursuit of SOC 2 Type II. The audit window opens Q3 2026. The runtime is the compliance boundary. The audit trail is the auditor's form.
HIPAA
The runtime ships with HIPAA-aware infrastructure. On-prem deployment available for operators under HIPAA. The AI Scribe service (built on Netwit) is in production with a healthcare operator under PIPEDA + HIPAA.
ISO 27001
The runtime is ISO 27001-aligned. The operator's ISO 27001 program is layered on top of the runtime, with the runtime providing the access control, change management, and monitoring primitives.
PIPEDA
The default cloud region is Canadian, for PIPEDA compliance. The data residency is enforced by the runtime, not by convention. The audit trail is on from day one.
The operators
Who Netwit serves.
Canadian enterprise
Operators under PIPEDA. Healthcare providers, professional services, public-sector-adjacent teams. Default cloud region is Canadian. On-prem available. The audit trail is the regulator's form.
US enterprise
Operators under HIPAA, SOC 2, and US state privacy law. Cloud or on-prem. The runtime enforces the perimeter the US operator sets.
MENA operators
UAE-based and GCC-based operators. Served through the Plex Dubai region. Multilingual support, MENA-tuned deliverability, and Canadian-built infrastructure.
Global platforms
Operators shipping across multiple regions. The runtime ships the same code in cloud, hybrid, and on-prem — so the same agent blueprint runs in Canada, the US, the UAE, India, and the EU without rework.
The brands on the runtime
What ships on Netwit.
- PostMTA — Self-hosted email delivery. The inbox that doesn't break.
- InboxGrove — SMTP infrastructure with IP warm-up and deliverability operations.
- Voice Agently — AI voice agents, 24/7, in the operator's brand voice.
- TrackSphere — Real-time delivery tracking with proof of delivery.
- Agentic OS — The flagship runtime. This page. (See also: the legacy Agentic OS page.)
- AI Agent Marketplace — Twelve ready-to-deploy agents on the Netwit runtime.
The rest of the portfolio — Voice Agently, PostMTA, InboxGrove, TrackSphere, Plex Dubai, Wahix India, Eventek, and the AI Agent Marketplace — are listed on the about page.
FAQ
Questions, answered.
- What is Netwit?
- Netwit is the lead VZU brand — the agentic AI automation platform. Netwit is the runtime the other 11 brands in the VZU family ship on, and the product VZU sells to enterprise operators. Built in Vancouver, available globally through VZU regions.
- Is Netwit the lead brand in the VZU family?
- Yes. Netwit is the lead brand in the VZU family. The other brands (Voice Agently, PostMTA, InboxGrove, TrackSphere, BookFlow, CareConnect, Plex Dubai, Wahix India, Email Marketing Arabia, Eventek, Track, and the AI Agent Marketplace) all ship on the same Netwit runtime.
- Where is Netwit built?
- Netwit is built by the VZU engineering team out of Vancouver, Canada (VZU Headquarters) and Bangalore, India (VZU Engineering). The product ships the same code in every region.
- Which regions does Netwit operate in?
- Netwit is the product; VZU is the operating group. Netwit ships globally through VZU regions: Vancouver (HQ, where the runtime is built), Dubai (VZU MENA, operated by Plex Dubai), Mumbai (VZU South Asia, operated by Wahix India), London (VZU EMEA support), and Bangalore (VZU engineering).
- Is Dubai the only region Netwit operates in?
- No. Dubai is one of several VZU regions where Netwit ships. The runtime is built in Vancouver and ships through VZU regions in Canada, the UAE, India, and the UK. Plex Dubai carries Netwit services into MENA; it is not the home of the runtime.
- How is Netwit different from Zapier or a workflow engine?
- Netwit is an agent runtime, not a workflow recorder. A workflow engine executes a script; an agent plans, invokes actions, observes results, and replans. The runtime enforces RBAC at the agent level, ships the audit trail by default, and deploys in cloud, hybrid, or on-prem.
- Can Netwit run on-prem?
- Yes. The runtime ships as a binary. It runs in cloud (Canadian, US, or EU region), in hybrid mode (the runtime on the operator hardware, the model API-called), or fully on-prem (runtime, model, and integrations on the operator infrastructure, including air-gapped).
- Who builds Netwit?
- Netwit is built by the VZU engineering team in Vancouver and Bangalore, with the operator being Dhiraj Chatpar, founder of AdaptUs Group Inc. (the holding company for the VZU family).
Get in touch
Ship Netwit in two weeks.
Email the team. Reply in one business day. The pilot is priced, the architecture is real, the ship date is real. The runtime ships the same in cloud, hybrid, or on-prem — in Vancouver, Dubai, Mumbai, London, or Bangalore.