Your customer checks out with Stripe. ~3 minutes later they have a live, isolated instance of your app on their own subdomain — own database, own admin, optionally their own Stripe receiving their money. One Linux box. No Kubernetes.
$ # stripe checkout.session.completed → webhook fires…
Launch pricing for the first 25 buyers, wired to real sales — when they're gone, they're gone.
Delivered as private GitHub repo access, automatically, minutes after purchase.
I run a fleet of live products — nine of them — from one home server. HatchKit started as the ticketing system for my own Las Vegas club nights, became the white-label engine behind showhatch.com, and is now packaged so you can skip the six days of plumbing between "I have an app" and "customers provision themselves."
Every claim on this page is checkable: the production system is live at showhatch.com — sign up for the demo and watch a tenant build itself.
Yes — HatchKit is the exact engine behind showhatch.com, where storefronts self-provision in ~3 minutes after checkout. The Events template ran real Las Vegas club nights before being productized. This page fabricates nothing: no invented testimonials, no fake buyer counts. The launch counter reads real sales data.
One Linux box with systemd — a $5 VPS or a home server behind a free Cloudflare Tunnel — plus Node 20+, Postgres, Caddy, and Python 3.10+. No Docker or Kubernetes required (Events ships a docker-compose if you prefer it standalone). Everything runs as an unprivileged user.
Boilerplates give you one app with auth and payments — great, but single-tenant. HatchKit is the factory: your customers check out and get their own isolated instance — dedicated database, subdomain, process, and optionally their own Stripe account receiving their revenue. It's the difference between building a SaaS and building the thing that stamps out SaaS instances.
Out of the box the provisioner builds and serves Next.js apps. The template contract is small (env vars + npm scripts), and the systemd/build steps are two lines you can adapt to any stack that builds and listens on a port — but Next.js is the paved path.
Blast radius and simplicity. A bug, a noisy neighbor, or a deletion request affects exactly one tenant. Template copies are hardlinked, so stamping costs seconds and near-zero disk. The honest tradeoff: ~100–200MB RAM per tenant — dozens of tenants per midsize box, and by the time that's your bottleneck, you have the revenue to solve it.
Private GitHub repo access (Core, Events, or both), granted automatically within minutes of checkout — you enter your GitHub username at checkout. Lifetime updates land in the same repos.
Unlimited products you own and operate, unlimited tenants, unlimited revenue. You can't resell or republish the kit itself as a boilerplate/starter/course. Full text in the repo.
Because you receive complete source code on purchase, all sales are final once repo access is granted. Check out the live production system first — that's exactly what you're buying.