linuxserver.hu

Getting a server is usually a ticket, a wait, and then an afternoon of hardening it yourself. linuxserver.hu turns that into a checkout: the pipeline that a careful sysadmin would run by hand runs on its own, every time, the same way.

What happens after you pay

The video shows the actual pipeline the code runs. The stage names on screen are the real ones:

1. creating_vps. A cloud server is created through the Hetzner Cloud API in the plan and location you picked.
2. installing_os. A fresh Ubuntu 24.04 with current packages.
3. hardening. Firewall on (ufw), fail2ban active, swap created, key-based SSH.
4. installing_software. Your choice of a plain server, Plesk, or n8n, with TLS set up.
5. Credentials email. "Your new server is ready", with the IP address and the SSH keys attached in both OpenSSH and PuTTY format.

A typical run finishes in a few minutes. There is no human in the loop on our side, which is the point: the result does not depend on who is on shift.

Why we built it

Most of Hilluter's automation work ends with the same question: where does this run? For n8n in particular the honest answer is often "on your own server", for data-residency and cost reasons. We were setting up the same hardened box again and again, so we automated it and put a checkout in front of it.

It is also a working example of what we mean by resilient workflows. Payment, provisioning, hardening, software install and email are separate stages with their own recorded state and logs, so a failure shows up at a named stage instead of as a half-built server nobody noticed. The same ideas are in our write-up on back-office ops automation and on deployment and monitoring.

What you get

• A hardened Linux VPS you fully own: root access, your keys, no lock-in.
• Optional Plesk for hosting websites and mail, or n8n for workflow automation, installed and reachable over HTTPS.
• Card payment through Stripe; provisioning starts the moment the payment succeeds.
• An English and a Hungarian interface.