I’ve been quietly building something on nights and weekends, and it’s finally real enough to write about. It’s called VBWD — a self-hosted, source-available full-stack SDK for building web and mobile products. The short version: it’s the boring 80% of every SaaS (accounts, billing, payments, an admin panel, apps) already switched on, so you can spend day one on your actual idea.

One backend, every surface. There’s a single Python backend, and from that one source of truth you get a Vue/TypeScript web app, a native iOS SDK and a native Android SDK. You write the logic once; all three clients consume it. For a solo builder, that’s the difference between shipping everywhere and shipping on one platform while promising the rest “later.”

Full VBWD Documentation — https://vbwd.cc/docs

Github VBWD Platform — https://github.com/VBWD-platform/

Agnostic core, gnostic plugins. The core knows almost nothing about your business on purpose. Everything specific is a plugin that toggles on or off without a restart — shop, marketplace, booking, subscriptions, a token/credit economy, datasets, a CMS, an encrypted office suite. You carry only the weight you actually use.

One idea holds it together. Whatever you sell — 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. Add a new way to make money and it inherits pricing, tax, discounting and reconciliation for free. One
ledger, not five.

AI-native, not AI-bolted-on. VBWD is MCP-native: platform actions are exposed as tools an LLM agent can discover and safely invoke under role-based access — not a chatbot scraping a UI, but agents that can actually do things (check a balance, grant access, place an order) with a full audit trail. As AI agents start shopping and operating on people’s behalf, being agent-callable stops being a gimmick and
becomes a channel.

Payments without lock-in. It’s provider-agnostic — cards, regional rails, and non-custodial crypto that settles straight to your own wallet – and adding a new gateway is a fraction of the usual code.

It’s self-hosted and the source is open to read, which for me is the whole point: I want to build on infrastructure I own, not rent a black box. It’s still a pet-project: I own the bugs and the uptime — but it already does more than I expected. More soon.