The part nobody tells you about self-hosting: you’ll do this setup more than once

The first time you stand up Vaultwarden, Uptime Kuma, and Paperless-ngx, it’s a fun Saturday project. You click through Community Scripts, pick your settings, watch the containers come up, and you’re proud of your homelab.

Then, six months later, a drive fails. Or you’re rebuilding on a new node. Or you fat-fingered a container and it’s easier to nuke it than fix it. Now you’re doing the exact same setup again, except this time you’re trying to remember what resource sizing you picked, which bridge you used, whether you hardened it the same way as last time, and you’re doing it from memory instead of documentation, because who writes documentation for their own homelab.

That second time is what this kit is actually for.

What it is

An Ansible playbook that deploys all three apps (or just one, your call) as clean, unprivileged Proxmox LXC containers, sharing one consistent base-hardening pattern instead of three different one-off setups. Point it at your Proxmox host, run one command, and you get the same result every time, whether it’s the first time or the fifth.

• playbook.yml, the main playbook, deploy one app or all three
• roles/vaultwarden/, Bitwarden-compatible password manager
• roles/uptime-kuma/, uptime and status monitoring for everything else you self-host
• roles/paperless-ngx/, document scanning, OCR, and search
• roles/common/, the shared provisioning logic (template download, container creation, base hardening) that keeps all three consistent with each other
• inventory.example.ini, copy to inventory.ini and fill in your own host details

This is the exact pattern used to stand up production services on a real running cluster, not a demo written for a blog post. Each app gets its own lightweight LXC, unprivileged where possible, on whatever bridge or VLAN you tell it to use.

“Can’t I just use Proxmox Community Scripts for free?”

Yes. You can, and if you only ever plan to set one of these up once, that’s a completely reasonable answer, and I’d rather tell you that straight than pretend otherwise.

Here’s specifically what the $19 is actually buying you instead:

It’s infrastructure-as-code you own, not a script that runs once and disappears. A Community Script installs an app and its job is done. This playbook lives in your own repo, under your own version control. You can read every line, change what it does, and run it again next year exactly the same way.

One coordinated deploy, not three separate one-off scripts. All three roles share the same base-hardening logic, the same conventions for resource sizing, the same approach to networking. Three different Community Scripts were written by different people at different times with different assumptions about how your container should be set up. This is one consistent system.

It’s your actual disaster-recovery plan, not just an installer. The real payoff isn’t the first time you run it. It’s the day your Proxmox host dies, or you’re standing up a second node, or a container gets corrupted and rebuilding from scratch is faster than fixing it. Instead of re-Googling how you configured Paperless-ngx eight months ago, you run one command and you’re back, with the same setup you had before.

You can extend it. Add your own role for the next app you want to self-host, change the default resource sizing, point it at a different bridge, wire it into whatever automation you’re already running. It’s a starting point that’s yours to build on, not a black box.

If none of that is worth $19 to you, the free scripts are genuinely a fine choice. I’d rather lose that sale than pretend this is something it isn’t.

What you get for $19

• All three roles, plus the shared common role, working together out of the box
• A real playbook you can read top to bottom, no obfuscation
• Free updates as the kit improves, at no extra cost
• A direct line to request the next app you’d want added (these kits get built based on what people actually ask for, not a random roadmap)

Being straight about where this stands

This is a new kit from a new site. There’s no pile of five-star reviews to point at yet, because we just launched. What I can tell you honestly: this is the same pattern already running production services on a real Proxmox cluster today, not something written just to sell. If you’re an early buyer, you’re also the reason the second and third kits get built faster, since your feedback shapes what comes next.

The guarantee

If it doesn’t work for your setup, or it’s just not what you expected, ask for a refund. No form to fill out, no runaround. A $19 digital download isn’t worth either of us arguing about.

Requirements

• A Proxmox VE host reachable over SSH, with a user that can run pct (doesn’t need to be root)
• Ansible 2.15+ on your control machine
• A Debian 12 LXC template already downloaded, or let the playbook fetch one for you

Get it

Checkout is handled by Stripe. This is a digital download, no physical shipping.

P.S. If you’re on the fence because you could technically do this with free scripts, that’s the right instinct to have, and the section above is the honest answer either way. If what actually matters to you is not doing this setup from scratch the next time something breaks, that’s what the $19 buys.