Keep your app running.

A process you start by hand dies on crash, logout, or reboot — and nobody is watching. Fill in a few fields and get a hardened systemd unit that restarts your app automatically, runs it as a non-root user, sandboxes it, and the exact commands to install it.

Running vs. staying running

Shipping the app is the easy part. The hard part is everything that happens after: the crash at 3am, the reboot after a kernel update, the memory leak that wedges the process without killing it. A managed platform did all of that for you invisibly — and when you move to a box you own, it becomes yours. A systemd unit is the first and most important piece: it turns “I started it” into “it stays started.”

It's also where most self-hosting setups stop — and where the gaps are. systemd will restart a crashed process, but it won't notice a hung one, fail over to another machine, page you when it gives up, or keep a record of who changed the unit and when. Those are the next layers, and they're exactly what a control plane is for.