Deploy to a server you own.

Push to main, and your app ships to your own box — no platform, no lock-in, just SSH to infrastructure you control. Pick how you run it and get a GitHub Actions workflow, the secrets to set, and the one-time deploy-key setup.

Your repo, your server, no middle layer

Platform deploys are convenient until the platform's pricing, limits, or outages become your problem. Deploying straight from GitHub Actions to a box you own keeps the convenience — push to a branch, it ships — without handing the keys to anyone. It's just SSH and a few commands, which means it works the same on any host and moves with you if you ever change providers.

The workflow is the easy 90%. The other 10% — making sure the deploy actually succeeded, that a bad release can roll back, that you have a record of what shipped and who triggered it, and that the service comes back if it crashes after deploy — is the operational layer a platform used to hide. That's the part a control plane gives back to you, on your own infrastructure.