Here is the shape of almost every commercial AI app, whatever industry it's in. You need a backend with accounts, data, and business logic. You need an AI layer that reasons over that data. You need a web app and, if you're serious, an iOS app and an Android app. And you need to get paid — subscriptions, billing, tax, the whole unglamorous machine. Founders spend most of their first year building that skeleton, over and over, before their actual idea ships. VBWD is the skeleton, in a box.
The pitch is simple: VBWD is a full-stack constructor for commercial AI applications, and "full-stack" means genuinely all of it.
The word that matters is one. One backend serves your web app, your iOS app, and your Android app. One billing system. One entitlement model that answers "is this user allowed to do this?" the same way everywhere. Instead of building — and then forever reconciling — three subtly different implementations of your product, you build the logic once and every client speaks to it.
VBWD isn't an app. It's the parts an app is made of, plus the rule that lets you assemble them without fighting the framework: the core is agnostic, and your industry lives in a plugin.
The core knows about users, money, events, permissions, and AI connections. It knows nothing about your vertical — gyms, legal intake, tutoring, property management, clinics, retail. That domain logic goes into a plugin that registers its routes, models, and screens through seams the core already exposes, and the core never learns your vocabulary. An automated check fails the build if core code so much as references a plugin. That discipline is what makes it a constructor rather than a template: you extend at designed seams instead of forking the engine, so adding your feature never means rewriting billing, and upgrading never means re-applying your patches.
Browse the plugin catalogue and the architecture and you'll see the pattern: commerce, content, messaging, bots, datasets — each a plugin, each composable, each something you'd otherwise spend months building.
Because the core is industry-neutral and the vertical is a plugin, the same construction kit builds wildly different commercial AI apps:
In each case the founder builds the one thing that is actually theirs — the domain logic and the AI experience — and inherits the rest.
The AI layer is designed the way 2026 actually needs. Your plugins don't each hold their own model key; they resolve a central LLM connection you configure once, so you swap providers or point at a model you host without touching a dozen call sites. Bots ground their answers in your content through retrieval, so they speak with your knowledge rather than a model's guesswork. The built-in MCP server makes your app legible to AI agents — increasingly how software gets used. And because the repository ships with instructions for AI coding agents, a tool like Claude Code lands in a codebase that tells it how to extend correctly, so building your plugin is faster still. See the developer docs for how the AI seams fit together.
The last piece is the one that turns a project into a business: monetisation isn't a later integration, it's already wired in. Subscriptions, trials, invoicing, tax that reconciles, a marketplace take, payments across regions and rails — configure them, don't build them. Your first paying customer is a settings change away, not a quarter away.
And the economics are built for founders. VBWD is source-available under BSL 1.1 and free for commercial use while your VBWD-attributable sales stay under the value of 6.7 BTC a year. You can build a real, revenue-generating AI product on it, commercially, owing nothing, until you're genuinely at scale. See the pricing page for the tiers above that.
It's a construction kit, not a finished product — the app is still yours to build, and that was always the interesting part. It's self-hosted, so someone runs the server. And a framework that does this much has a shape; working with its seams is far faster than fighting them, but there's a shape to learn. If your idea is genuinely a thin wrapper over a single API call, you don't need this. If it's a real commercial AI application — backend, AI, web, mobile, and money — this is the year of plumbing you get to skip.
Every founder building a commercial AI app pays the same entry fee: months rebuilding the backend, the mobile clients, the billing, and the AI plumbing before the actual product appears. VBWD is that entry fee, paid once, for everyone — a constructor where the skeleton is done and your idea is the only thing left to build. Clone it, add your plugin, ship to web, iOS, and Android from one backend, and charge for it from day one. Start at vbwd.cc, read the docs, or go straight to the source on GitHub.