Lohnt sich dein eigenes CodeSandbox?

Build me a personal cloud dev environment to replace CodeSandbox.
Requirements:

- Do not write an IDE. Set up code-server (VS Code in the browser) on my
  VPS via its official install script, running under systemd, bound to
  localhost.
- Access over Tailscale or an SSH tunnel only; no public exposure, built-in
  password auth switched off. That is the whole security model, keep it
  that simple.
- A sandbox CLI: sandbox new <name> --template node|python|static copies a
  folder from templates/ into ~/sandboxes/<name>, runs its install step,
  and prints the code-server URL opened to it.
- Three templates: node (Express hello world + nodemon), python (venv +
  Flask), static (index.html served with live-server).
- Previews: each sandbox's dev server gets its own port, reachable through
  the same tunnel; a tiny index page lists sandboxes and their ports.
- sandbox rm <name> archives the folder to a tarball before deleting it.
- No accounts, no telemetry; everything lives on my own server.
- Out of scope: multi-user collaboration, instant VM forking, and public
  preview URLs; managed infrastructure is the hosted product.
- README: install steps, tunnel setup, and how to add a template.