Your Own Subscription Platform for the Price of a Coffee: The €12 Weekend Build

For the cost of a few coffees and a free weekend, you can have a real, self-hosted subscription platform running. Nothing to lose — here’s how to download, install, and build.

Download, install, and own your stack.

It is Friday evening. You have an idea for a small subscription product — a members’ area, a paid newsletter, a token-metered tool, a niche SaaS — and the usual wall in front of it: signup flows, billing, tax, invoices, an admin panel. Weeks of plumbing before you can charge a single euro. What if, instead, you spent the price of a few coffees and a free weekend, and had the whole thing running on a real server by Sunday night?

That is not a sales promise. It is roughly what a small VPS and a Saturday afternoon actually buy you with VBWD. This article walks through the experiment honestly: what it costs, what you type, what you get, and — just as important — what it is not.

The €12 box

You do not need a cluster. VBWD is a self-hosted platform built on Python/Flask, PostgreSQL, Redis, and a Vue 3 / TypeScript frontend, all wrapped in Docker. The whole stack — API, database, cache, admin backoffice, user-facing app — fits comfortably on a small EU VPS. The kind you can rent for around €12–16 a month from any of the usual providers: two shared vCPUs, a few gigabytes of RAM, an SSD.

That is the entire financial risk of this experiment. One month of a cheap box is the cost of two or three decent coffees. If you decide by Sunday that it is not for you, you destroy the server and you are out roughly the price of a lunch. There is no license to buy up front, no seat count, no sales call. The barrier to trying is close to zero, and that is the whole point of doing it as a weekend build rather than a quarter-long project.

The install, with the real commands

Spin up a fresh Ubuntu box, install Docker and Docker Compose, then clone the public SDK and let the install recipe do the rest. Four commands:

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

The dev-install-ce.sh recipe pulls the backend and the frontend apps, wires up their dependencies, and prepares the database. make up brings the services online: the Flask API, PostgreSQL, Redis, and the two web apps. Give it a few minutes on a small box — Docker has images to pull and a database to migrate. When it settles, you have a running platform with pre-built user accounts, an admin backoffice, and the full billing engine already wired together. If a step trips over a missing dependency, the documentation covers the common prerequisites and environment variables.

Nothing here is a mock. The admin login works. The registration flow works. The invoice generator produces real invoices. You are looking at the same codebase you would run in production, just on a €12 box instead of a €200 one.

What to build first

Resist the urge to configure everything at once. The satisfying version of this weekend is narrow: get one real thing working end to end. Three moves are enough.

One subscription plan. Open the admin backoffice and create a single tiered plan — say a €9/month membership. The billing system handles the recurring charge, applies tax, and generates invoices without you writing any of that logic. Register a test user, subscribe them, and watch the invoice appear. That loop — signup, subscribe, invoice — is the part most people spend weeks on. Here it already exists.

A landing page. VBWD ships with a CMS, so you do not need a separate site builder to explain what you are selling. Write a short landing page, drop in the embeddable pricing widget so visitors can see the plan and subscribe, and you have a front door. It will look plain until you style it — that is fine for a weekend proof.

One plugin. The platform is built around a plugin system, and that is where your actual product idea lives. Enable one and feel how the seam works — a token system for metered usage, an AI bot, webhooks that fire on subscription events into whatever you already run. You are not trying to ship the plugin this weekend; you are checking that the extension point is real and that your idea fits it. It does or it does not, and you will know by Sunday.

By the end of the afternoon the honest scorecard is: accounts, a plan, tax-correct invoices, a payable landing page, and one plugin proving the platform bends to your idea. That is a lot of ground for the cost of a coffee run.

Free while you are small

Here is the part that makes the experiment genuinely low-risk rather than just cheap to start. VBWD is source-available under the Business Source License 1.1. In plain terms: you can read the code, run it, self-host it, and use it commercially for free as long as your annual VBWD-attributable sales stay under the value of 6.7 BTC. Cross that line and you need a commercial license — but if you are crossing it, the platform is doing its job and the license is a rounding error against the revenue. And the license is time-boxed by design: each release converts to the permissive Apache-2.0 license on a schedule, so the code you run today does not stay locked forever.

So the weekend build costs you a €12 server and nothing in software, and it stays that way through the entire range where a new product is finding out whether anyone will pay. You are not signing up for a percentage of every transaction from your first sale. The full terms are laid out on the pricing page, and if you want to see exactly how sales are attributed and counted, the billing details spell it out. Read them before you build on it — do not take my paraphrase as the contract.

What it isn’t

An honest weekend needs an honest warning. Self-hosting means you own the operational side. There is no support desk keeping the lights on: uptime is yours, TLS certificates are yours, security updates are yours, and — the one people skip — backups are yours. Before you put a single real customer on this, set up automated PostgreSQL backups and test that you can restore them. A subscription platform without backups is a liability, not an asset, and no software can make that responsibility go away.

Nor is this a magic revenue button. It gives you the machinery to charge people; it does not give you people to charge. The plan, the landing page, the invoices — all of that is plumbing that works from day one, but the demand still has to come from you. Do not read a running admin panel as traction. It is capability, not customers.

And if, after reading the operations paragraph, your gut says “I would rather pay someone a percentage than babysit a server” — that is a completely legitimate answer. A fully hosted platform where uptime and backups are someone else’s problem may be the honest choice for you, and it is worth the cut. VBWD is for the person who would rather own the box, the data, and the bill. Know which one you are before you commit a weekend.

Start this weekend

If you are still reading, you are the kind of person who owns the box. So here is the concrete challenge: rent a €12 VPS tonight, and by Sunday have a real subscription platform — accounts, a plan, tax-correct invoices, a landing page — running under your own domain. The downside is a lunch’s worth of money and a Saturday. The upside is that you stop reading about building a product and actually have one to point at.

Grab the code and the install recipe from the VBWD SDK download page, run the four commands above, and see how far you get before the weekend is out. Nothing to lose but a few coffees — and something real to show for it.