Stop Renting Your SaaS Stack: Why It’s Time to Self-Host — and How to Start Right Now

Hosted platforms take a cut of your revenue and hold your customer list. Own your stack instead: this is the case for self-hosting VBWD, plus the few commands to install it right now.

Download, install, and own your stack.

You don’t own the business you think you own

Here’s an uncomfortable question for anyone running a subscription product, a membership, a paid newsletter, or a small SaaS on a hosted platform: if that platform changed its terms tomorrow, raised its fees, or simply decided your niche wasn’t welcome anymore, what would you actually keep? Your customers’ email addresses, maybe. A CSV export, if you’re lucky. But not the billing relationship, not the payment history, not the running system your revenue depends on. You’ve been paying every month to rent something you can never own.

That arrangement is comfortable right up until it isn’t. This article makes the case for the alternative — self-hosting your own stack with VBWD — and it does so honestly, including the parts that ask something of you. By the end you’ll know whether owning your stack is the right call, and if it is, you’ll have the exact commands to start in a few minutes.

The real cost of renting

Hosted platforms sell convenience, and they charge for it in two ways: a cut of your revenue, or a fixed monthly fee that climbs as you grow. Look at what the popular options take. Substack takes roughly 10% of subscription revenue. Gumroad takes around 10% per sale. OnlyFans takes about 20%. GoHighLevel starts at around $497 a month before you’ve earned a cent. These are approximate figures and they change, but the direction never does: the more successful you become, the more you pay.

Run the arithmetic on a percentage cut. If you build a membership doing $10,000 a month and the platform takes 10%, that’s $1,000 every month — $12,000 a year — for hosting a system you could run yourself for the price of a coffee subscription. Cross into six figures of monthly revenue and the platform’s cut alone would pay several full-time salaries. You are, in effect, giving a silent partner an equity-sized stake for infrastructure that costs almost nothing to operate.

The fees are only the visible cost. The deeper one is control. On a rented platform you don’t own the payment integration, the subscription logic, the data model, or the customer relationship at the infrastructure level. You can’t inspect the code. You can’t change how billing behaves. You can’t move your running system somewhere cheaper without rebuilding it. And if the platform deplatforms your category — which happens to entire industries with little warning — your business stops, not because you did anything wrong, but because you were a tenant.

What you own instead with VBWD

VBWD is a self-hosted, source-available platform for exactly this kind of business. You download it, you run it on your own server, and the whole thing is yours. It’s licensed under BSL 1.1, which means it is free for commercial use while your annual VBWD-attributable sales stay under the value of 6.7 BTC — a threshold most independent operators will never approach — and it converts to the fully open Apache-2.0 license on its scheduled change date. You can read the full terms and the free-tier story on the pricing page. There’s no percentage of your revenue leaving every month. There’s no per-seat meter. What you earn is what you keep.

And you’re not starting from an empty repository. VBWD ships with the parts a subscription business actually needs, already built:

User accounts and authentication
Subscription billing, with tax handling and invoices
A token system for usage-based or credit-based products
A built-in CMS for your pages and content
Multi-provider payments — Stripe, PayPal, and YooKassa
An admin backoffice for managing users, plans, and invoices
A plugin system so you can extend it without forking the core
Outbound webhooks for wiring VBWD into the rest of your tools
AI bots for chat and automation

Under the hood it’s a conventional, well-understood stack: Python and Flask on the backend, PostgreSQL for data, Redis for caching and queues, Vue 3 with TypeScript on the frontend, all packaged with Docker. Nothing exotic, nothing you’ll struggle to hire for or reason about later. You can see how the pieces fit together in the architecture overview, and the documentation walks through configuration and day-to-day operation.

The economics of running it are the mirror image of renting. A small EU VPS — the kind that costs around €12 to €16 a month — is enough to run the whole platform for a growing product. That figure doesn’t move when your revenue does. Your hosting bill at $1,000/month of sales and your hosting bill at $50,000/month of sales are the same bill.

What self-hosting honestly asks of you

This is the part most pitches skip, so let’s be direct. When you own the stack, you own everything about keeping it healthy. That means you’re responsible for uptime, for backups, for TLS certificates, and for applying security patches. A cheap VPS with no backup strategy is a single point of failure, and if it dies at 2am, no support desk is picking up — that’s on you.

None of this is hard in the way rocket science is hard. Managed database backups, automated certificate renewal, and a second server for redundancy are all solved, documented problems, and the docs cover them. But they are real work and real responsibility, and you should go in clear-eyed. If you would genuinely rather pay a platform 10% or 20% of your revenue precisely so that you never have to think about a server again, then a hosted platform is the honest choice for you, and you should take it without guilt. Self-hosting pays off when you value ownership, margin, and control enough to accept the operational weight that comes with them. For a lot of independent operators, that trade is obvious. For some, it isn’t. Only you know which you are.

Install it in a few minutes

If you’ve decided ownership is worth it, there’s nothing stopping you from having VBWD running today. On a machine with Docker installed, the full setup is four commands:

git clone https://github.com/VBWD-platform/vbwd-sdk-public.git vbwd
cd vbwd
./recipes/dev-install-ce.sh
make up

The first command downloads the platform. The install recipe wires up the backend, both frontend apps, and their dependencies in the right order. make up starts the services — the API, PostgreSQL, and Redis — behind Docker. When it finishes, you have a running subscription platform on your own machine: accounts, billing, CMS, admin backoffice, and payments, all live, all yours to configure. From there the documentation takes you through connecting a payment provider, creating your plans, and deploying to that small VPS for production.

Start on your laptop first. Click through the admin, create a plan, look at how invoices and tax are handled, poke at the plugin system. You’re not committing to a migration by doing this — you’re spending ten minutes to see, concretely, what owning your stack feels like before you decide anything.

Stop renting. Start owning.

Every month you stay on a hosted platform, you pay for the privilege of not owning your own business’s foundation, and the bill grows with your success. VBWD offers the other path: a real, running, source-available platform you install once and keep — free for commercial use under BSL 1.1 while you’re growing, built on a stack you can actually understand, and cheap to operate on hardware you control. The trade is honest work in exchange for ownership and margin.

If that trade makes sense to you, take the next step now: download and install VBWD, run the four commands above, and have your own platform running before the end of the day. The tenant pays forever. The owner pays once. Decide which one you want to be.