Stop hand-coding billing, auth, CMS, and payment integrations on every client project. Build on a platform you can resell.
VBWD is a self-hosted, open-source SaaS stack purpose-built for agencies that ship booking systems, software stores, AI-metered tools, and member portals. Plugin-per-feature so you compose instead of fork; token-based billing so your clients have recurring revenue from day one; 20+ payment rails so you stop saying "let's also add Mollie / SBP / OXXO".
Three patterns every agency over five people knows. None of them require better designers, better PMs, or a better sales pipeline. They require a platform you can resell — so the same boring 60% never gets rebuilt.
Every new client wants auth, billing, CMS pages, an admin panel, and "just a checkout". Your team writes that again — maybe with Stripe, maybe with PayPal, maybe with a local rail because the client is in São Paulo or Bangkok. Eight weeks gone before the first client-specific feature lands.
Symptom: your senior engineers spend half their time reproducing scaffolding they could ship from a template.
The client pays you to build, then signs an SLA at maybe 15% of project cost annually. Hosting is on their bill, not yours. You don't get a cut of their customer revenue — even though the platform you built is making them money daily.
Symptom: last year's clients pay nothing this year; the pipeline has to refill from zero every quarter.
A self-hosted Python + Vue platform whose core is intentionally agnostic — every domain behaviour ships as a plugin trio (backend + admin + user UI). Multilingual, brandable, includes CMS, plan engine, payment marketplace, token wallet out of the box.
Each feature is one repo (e.g. vbwd-plugin-booking).
You compose; you never patch the core. Enable / disable plugins per
instance via admin UI — no redeploy.
Tiered plans, add-ons, prorated upgrades, dunning, invoicing, cancellation. Stripe / PayPal / 20+ local rails preselected per market. You stop writing checkout for the third time this year.
Every user has a token balance. Meter any feature against it — AI calls, exports, downloads, premium views. Sell token bundles as add-ons. Your client's customers top up; you get a cut.
Six instances per €30 VPS, each on its own subdomain with its own brand & CMS. Spin up a new client in an afternoon, not a week.
booking.paid, subscription.cancelled,
lead.captured on the same bus. Plug into the client's
PMS / CRM / BI without writing glue code.
Marketing edits landing pages, blog posts, packages — without shipping. Per-locale, per-access-level. Already what your clients hire you for in WordPress, but inside the same stack.
Plugins to enable, rough ship window, live demo to show. Pick two and start.
For: independent hotels, B&Bs, hostels.
Plugins: booking · cms · stripe · paypal · meinchat
Ship in: 2 weeks for an MVP, 6 weeks production.
Demo: /project/hotel/
For: dental groups, diagnostic labs, telemed clinics.
Plugins: booking · cms · subscription · meinchat · email
Ship in: 4 weeks (compliance review = main path).
Demo: /project/doctor/
For: co-working, studios, courses, workshops, retreats.
Plugins: booking (capacity = N) · cms · shop · discount
Ship in: 2-3 weeks; same plugin, different config.
Demo: hotel deck applies — capacity-mode toggle.
For: indie SaaS bundles, OSS maintainers, plugin shops.
Plugins: ghrm · subscription · stripe · taro · analytics
Ship in: 3 weeks; GitHub OAuth + plan-gated repos.
Demo: /project/softwarestore/
For: creators selling LLM-backed tools (writing, tarot, image).
Plugins: chat · taro · token-bundles · subscription · stripe
Ship in: 1 week; reskin the existing taro plugin.
Demo: any vertical's /dashboard/taro route.
For: digital goods, supplements, branded merch.
Plugins: shop · discount · stripe · cms
Ship in: 3 weeks; inventory + warehouse already built.
Demo: shop.vbwd.cc.
meinchat · subscription), multi-language landing engine
(cms · theme-switcher), and "anything + payments" — your
custom plugin on the existing billing/auth/CMS.
VBWD ships as two repos — vbwd-sdk for
laptop dev, vbwd-platform for production. Same plugin
contract, same docker layout. Promoting from one to the other is a
config change, not a rewrite. On top of that, three multi-site
patterns cover every client scale.
github.com/VBWD-platform/vbwd-sdk
Umbrella: backend + fe-user + fe-admin + every plugin as
submodule. ./recipes/dev-install-ce.sh → full stack
up in <5 min on a laptop, seed data + admin login.
github.com/VBWD-platform/vbwd-platform
Scrubbed, multi-tenant. GHCR images, per-client compose
templates, GitHub Actions deploy, Hestia nginx. What you run
for paying customers.
Multisite SaaS. Single app, single Postgres,
many domains — tenant resolved from Host header,
CMS picks brand + content. Cheapest, fastest, co-mingled data.
Multi-tenant with isolation. Same image; per-client compose + per-client Postgres DB. Subdomain + own admin + plugin set. Data isolated, ops shared. The default pattern.
Regulated / sovereign. Own VPS, own region, own
image build. Same plugin contract; ship vbwd-platform
as-is or fork. The expensive option — quote accordingly.
Every user account on every instance has a token balance. Meter any backend handler against it with three lines of Python; charge for consumption; sell top-up bundles as add-ons. The wallet, the purchase flow, the audit log, the admin moderation — already shipped. You design the price; the platform handles the rest.
Decorate a handler with @meter("ai.chat", cost=10)
and that endpoint deducts 10 tokens per call. The platform handles
insufficient-balance refusals, audit log entries, and per-user
usage analytics.
1000 tokens = €9, 5000 = €39. Sell them
as one-shot purchases inside the same checkout the user already
knows — Stripe / PayPal / local rail. Auto-credit on payment.
"Pro plan = €29 + 2000 tokens / month". Subscription renews top-up automatically. Unused tokens roll over or expire — the admin picks the policy per plan.
/dashboard/taro on any instance) is the reference: an
LLM-backed feature that bills tokens per reading. Reskin it for any
AI-feature your client wants to monetise — same wallet, same surface,
different prompts.
Two prices to think about: what you pay VBWD per client instance, and what you charge the client for setup + monthly. The gap is yours. Below: the standard partner deal, plus the three margin lines you can stack on top.
You onboard a 30-room boutique hotel. Quote: €4,500 setup + €600/mo. You pay VBWD €99/mo for the instance. Hotel sells token-backed loyalty points to repeat guests: ~€800/mo of token sales → your 20% = €160/mo extra. Net per client: ~€660/mo recurring after VBWD cost. Five hotel clients = €3,300/mo MRR. Year two: that's your runway, not your pipeline.
A demo on your laptop. A first client in production. A long-term partner deal that compounds.
A live walkthrough of the platform — pick the vertical that matches your strongest client lead (hotel, doctor, software store, AI-feature, or your own custom) and we'll show the moving parts on the existing demo, then sketch the delivery plan for that specific client. No slideware after this deck.
47 public repos under
github.com/VBWD-platform.
Start with vbwd-sdk for the umbrella + dev-install
script. BSL 1.1, you can git clone it in 30 seconds.
Reply to this deck or:
partners@vbwd.cc
Subject: "agency · <the project shape>"
You get a calendar link the same day.
git clone https://github.com/VBWD-platform/vbwd-sdk &&
cd vbwd-sdk && ./recipes/dev-install-ce.sh brings the
whole stack up on your laptop in <5 min. Walk in with concrete
questions instead of generic ones.
Once the first client is live and the model has landed, the long-term deal kicks in. You're a partner: a listed studio on the VBWD page, first look at new plugins, voting weight on the roadmap, and a recurring cut of every token bundle your clients' end-users buy.
You charge the client: €350-€2,500/mo depending
on instance + your services on top.
You pay VBWD: €99/mo per live instance, flat.
You earn: 20% of every token-bundle the client's
users buy, paid quarterly, paid for the lifetime of the client.
Top partners hit 30% after the third client lands.
Studio listing on
vbwd.cc/partners with the verticals you specialise in.
First-look access to new plugins before they hit
the public catalogue.
Roadmap weight. Partner asks rank above community
asks. We sometimes ship features because partners need them.
Direct line to engineering. Shared Slack, async
PR review on your plugins.
We pitch you in. Each vertical case study is also a partner case study — your logo + a paragraph + a link to your project.
Build a plugin a third agency could resell? List it in the catalogue. Standard 70/30 revenue split with us as platform — that means your margin on someone else's clients too.
No annual partner-fee escalations. Same per-instance rate as your first client. Predictable. The token-revenue share keeps compounding as your portfolio grows.
Twelve slides is a lot to read. The short version: VBWD is the sellable platform underneath your next ten client projects. Booking systems, software stores, AI tools, member portals — same stack, your brand, recurring revenue you didn't have last year.