A VZU tool · web-app-builder.vzu.ca
Web App Builder.
Engineer-grade React/Next.js scaffolding with the NetWit runtime baked in. MCP-native. One click to Cloudflare Pages.
VZU Web App Builder is a scaffolder for engineers. The operator gets a typed Next.js codebase wired to the NetWit runtime, with MCP server registration, RBAC at the agent level, audit trail on by default, and a Cloudflare Pages deploy target. The output is a real Git repository, version-controlled from the first commit, owned by the operator, and deployable on a branch preview in seconds. Web App Builder is a tool inside the VZU family, operated by Virtual Zero Unbound Inc.
What ships
Six capabilities.
Lead capability
NetWit runtime baked in.
02
Next.js App Router, typed.
Server Components, Server Actions, route handlers, typed clients. The scaffolder picks the right primitive per route and leaves a working build on day one.
03
MCP server registration.
Every external tool is an MCP server, declared in code, with a typed schema. New tools plug in without refactoring the app shell.
04
RBAC at the agent level.
Permissions are enforced at the agent, not the user. The agent sees what the user is allowed to see. The audit trail records every call.
05
Cloudflare Pages deploy.
Branch previews, edge functions, and Workers for the runtime. Push to main, ship to production. Rollback is a single command.
06
Observability wired in.
Logs, traces, and metrics from the first deploy. The runtime emits structured events; the operator gets a dashboard on day one.
The deep view
On the runtime, MCP, and the engineer experience.
Web App Builder exists because most "AI app" scaffolds pretend the runtime is someone else's problem. VZU's position is that the runtime is the moat. Every app scaffolded here is wired to the NetWit runtime from the first commit. The runtime handles agent calls, RBAC, the audit trail, and the MCP server registry. The app code stays focused on routes, components, and domain logic.
The MCP story is the same one VZU ships across the whole family. Every external tool — a CRM, an email platform, a payment provider, an internal API — is described as an MCP server with a typed schema. The app calls the tool by name. The runtime resolves the call, enforces the permissions, records the audit trail, and returns a typed result. A new tool is a new MCP server file. The app shell does not change.
The deploy target is Cloudflare Pages by default. The scaffolder produces a `wrangler.toml`, an `_headers` file, and a Workers entry point for the runtime. The operator pushes to a branch, gets a preview URL, and ships to production with a merge. Vercel and self-hosted Node are also valid; the codebase is standard Next.js, and the deploy instructions ship in the README.
The operator owns the codebase end to end. Web App Builder is a starting line. The scaffolder writes the boilerplate, wires the runtime, registers the MCP servers, and produces a deployable artifact. After that, the operator's engineers do the rest. There is no proprietary glue to keep paying for. The runtime itself ships as a Worker or a Node process; the operator can fork it, audit it, and host it themselves.
Web App Builder is one of twelve VZU tools operated by Virtual Zero Unbound Inc. The full set includes App Builder, Frontend Design, Frontend Design Expert, Fullstack Dev, UI/UX Pro Max, UI/UX Designer, Landing Page Builder, Code Review, Prompt Engineer, MiniMax XLSX, and Web Scraper. Each tool shares the same NetWit runtime standards and the same operator-owned output.
The process
How it works.
- 01.
Scope the scaffold.
The operator lists the routes, the data sources, and the MCP servers. VZU maps the list to a scaffold, picks the deploy target, and produces a fixed-fee quote.
- 02.
Scaffold and wire.
VZU runs the scaffolder, writes the typed clients, registers the MCP servers, and pushes a working Next.js repo to the operator's Git provider. The first deploy lands in under an hour.
- 03.
Build the product.
The operator's engineers work against the typed SDK. The runtime handles auth, RBAC, and audit. New MCP servers can be added without touching the app shell.
- 04.
Ship, observe, iterate.
Branch previews, edge deploys, structured logs. The operator owns the runtime, the codebase, and the data plane. VZU stays in the loop for code review and the next iteration.
The runtime
NetWit, audited end to end.
Every app scaffolded with Web App Builder is auditable from the runtime up. RBAC at the agent level. Audit trail on by default. SOC 2 in active pursuit, ISO 27001-aligned.
Other VZU tools
Questions
Frequently asked.
- Is this just a Next.js starter kit?
- No. Web App Builder scaffolds a Next.js app, but the value is the NetWit runtime wired in. RBAC, MCP, audit trail, observability, and Cloudflare Pages deploy are not bolt-ons. They ship with the first commit.
- Can I use a different framework?
- Web App Builder targets Next.js because Server Components, Server Actions, and route handlers fit the agent-driven app shape. For Astro work, see Landing Page Builder. For visual app work, see App Builder.
- Do I own the code?
- Yes. The scaffold is a real Next.js codebase in your Git provider. The runtime is a Worker or a Node process you can audit and host. There is no proprietary glue.
- How is this run?
- Web App Builder is operated by Virtual Zero Unbound Inc., the holding entity behind the VZU brand family. The team works out of Vancouver, Dubai, Mumbai, and Bangalore.
- What if the runtime is overkill?
- If you are shipping a marketing site, see Landing Page Builder. If you are shipping a content-heavy editorial site, Astro is the right target. Web App Builder is the right answer when the work needs agents, RBAC, and an audit trail.
Next step
Brief VZU on Web App Builder work.
Send a one-paragraph brief. We reply in one business day with a scaffold outline, the MCP server list, and a fixed-fee pilot you can put on the calendar.