"To launch a startup you first build the boring 80%." Accounts, auth, billing, payments, an admin panel, a mobile app — months of undifferentiated plumbing before you touch the one thing that makes you a business. That assumption is why most ideas die in the scaffolding. The VBWD full-stack SDK is a bet that the plumbing should come switched-on, so a founder can spend week one on the idea, not the infrastructure.

One backend, every surface

The core promise is uncomfortable for most stacks: a single Python backend serves a Vue/TypeScript web front end, a native iOS SDK and a native Android SDK — from the same source of truth. You are not maintaining three separate API integrations and three notions of "a user." You write your logic once; the web, iOS and Android clients consume it. For a two-person team, that is the difference between shipping on all three platforms and shipping on one and promising the rest "later."

You enable capabilities, you don't build them

VBWD's core is deliberately agnostic; everything specific is a plugin that toggles on or off without a restart. Building a startup becomes a question of which capabilities you switch on:

• Selling a subscription product? Enable subscription — plans, add-ons, recurring billing.
• A marketplace? marketplace plus withdraw for vendor payouts.
• A booking business? booking — appointments, rooms, seats, slots.
• A credit or token economy? token_payment, metered and prepaid.
• Selling data or digital goods? dataset. Content and a blog? cms.
• An AI assistant or agent-callable surface? the chat/LLM modules and mcp.

Payments are provider-agnostic — Stripe, PayPal and a dozen regional rails, plus non-custodial crypto that settles to your own wallet — and adding a new one is a fraction of the usual code. You carry only the weight you use.

The one idea that keeps it coherent

Under all of it sits a single principle: everything sellable — a subscription, a booking, a token top-up, a marketplace commission, a dataset licence — is declared as an invoice line item against one shared interface, and an event-based contract engine keeps the balance between what a customer owns and what they owe. That means you don't wire up a separate billing story per feature. Add a new way to make money and it inherits pricing, tax, discounting and reconciliation for free. Your startup's ledger stays one ledger.

A week-one plan

Concretely, a founder can move fast:

• Day 1–2: clone the public SDK, run the install recipe, and pick the plugins your idea needs.
• Day 3–5: model what you sell as line items, wire your one differentiated screen on the web app, and turn on a payment provider.
• Week 2: ship the same product to iOS and Android from the SDK, and let the CMS carry your landing page and blog.

You still build the part that matters — the actual product, the taste, the go-to-market. The platform just refuses to make you rebuild accounts, a multi-surface API, billing and payments first.

The honest boundary

VBWD is a substrate, not a business plan. It won't find product-market fit, write your positioning, or run your operations — self-hosting means you own uptime, backups and updates. What it removes is the generic, expensive foundation that usually eats a startup's first three months. It is source-available, so nothing about your own spine is a black box you rent, and the licence stays free for commercial use well past the point most startups reach.

If you'd rather spend week one on your idea than on plumbing, the platform is open. Read the documentation, clone the public SDK at github.com/VBWD-platform/vbwd-sdk-public, or get in touch.

VBWD is source-available under BSL 1.1 — free for commercial use while annual VBWD-attributable sales stay under the value of 6.7 BTC per year.