Individual skill
levelsio-vps-deploy
Set up a web app on a single cheap, hardened VPS the "levels.io" way — one Hetzner/DigitalOcean box running Next.js (or any Node app) on SQLite + Caddy (auto-HTTPS) + systemd, secured with Tailscale, put behind a Cloudflare domain, and set up to charge money with Stripe. The whole "idea → app that makes money on a cheap VPS" path. Offers TWO workflows the user picks between — Path A, develop on your own computer and deploy to the VPS for cheap hosting; Path B (the full levels.io way), develop ON the VPS itself with Claude Code running in tmux, connecting via Termius from laptop or phone over Tailscale, with edits going live in seconds. The domain (Cloudflare) and payments (Stripe) steps each offer full-auto (the agent creates everything with your API keys) or manual (you click the dashboard, the agent verifies) modes. Use when the user wants cheap single-server hosting, asks to provision a Hetzner/DigitalOcean VPS, wants to deploy a Next.js/Node app WITHOUT Vercel/Supabase/Kubernetes, wants to develop on a server / code from their phone / run Claude Code persistently on a VPS, wants to put a domain on their app / point Cloudflare DNS at a VPS / hide the origin behind Cloudflare, wants to charge users / add Stripe subscriptions / set up a paywall / take payments / "make money", mentions the "levels.io method" / "one big server" / "boring tech" / tmux / Tailscale / Termius, or asks how to self-host a small app for a flat ~$8/mo.
skills-imported/levelsio-vps-deploy/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 56
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- devops Derived category
- data Derived category
- engineering Derived category
- data-databases Derived category
- devops-containers Derived category
- engineering-web Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 18,672 bytesSKILL.mdcore · 18,672 bytesSKILL.mdcore · 18,672 bytesSKILL.mdcore · 18,672 bytesSKILL.mdcore · 18,672 bytesSKILL.mdcore · 18,672 bytesSKILL.mdcore · 18,672 bytesSKILL.mdcore · 18,672 bytesreferences/architecture.mddoc · 7,179 bytesreferences/develop-on-vps.mddoc · 6,517 bytesreferences/domain-cloudflare.mddoc · 4,781 bytesreferences/monetize-stripe.mddoc · 9,730 bytesreferences/provision-hetzner.mddoc · 4,801 bytesreferences/remote-claude-code-tmux.mddoc · 5,363 bytesreferences/security-tailscale.mddoc · 3,824 bytesreferences/troubleshooting.mddoc · 8,050 bytes
Read excerpt
# levelsio-vps-deploy
Run a web app on **one cheap, hardened VPS** — the levels.io way. No Kubernetes,
no microservices, no managed PaaS. One box, boring tech, vertical scaling, ship
fast.
The full arc is **idea → app that makes money on a cheap VPS**: provision + secure
the box, deploy the app, put a **domain** on it (Cloudflare), and **charge money**
(Stripe). The last two steps each let the user choose *full-auto* (hand the agent
an API key, it creates everything) or *manual* (they click the dashboard, the
agent verifies each step read-only). If they already have a domain and an
activated Stripe account, going from a running app to taking payments is minutes.
## First: pick the workflow (ask the user)