Guides written by the people who run the servers.
No content-marketing filler and no tutorials that stop before the hard part. Every command here has been run on the platform it describes.
Getting started
From payment to a working server.
First steps after deployment
The ten minutes of work that turn a fresh VPS into one you can safely leave running: updates, a non-root user, keys-only SSH, a firewall and a backup plan.
Choosing a location
How to pick a jurisdiction from your actual threat model rather than from marketing, and why buying the most distant country is usually the wrong answer.
Security
Hardening, keys, firewalls and access.
SSH hardening
An sshd configuration that resists everything short of a targeted attacker: Ed25519 keys, modern ciphers only, fail2ban, TOTP and hardware tokens.
SSH over Tor
Reach your server through a v3 onion service so it never sees the address you administer from, then firewall public SSH off the internet entirely.
Networking
IPv6, rDNS, firewalls and DDoS.
Firewall configuration
Deny inbound by default and open only the ports you serve, in ufw, firewalld or nftables directly — plus how not to lock yourself out doing it.
IPv6 configuration
Every server ships with an IPv6 /64. How to configure it in netplan and systemd-networkd, bind the whole range, set PTR records and not break ICMPv6.
Reverse DNS and mail deliverability
PTR, SPF, DKIM and DMARC are the four records that decide whether your mail arrives. How to set each one, verify it, and warm a new IP without being filtered.
How DDoS protection works here
What the included filtering stops, what needs the layer-7 tier, and what to do while an attack is running. We do not null-route the customer being attacked.
Operations
Backups, snapshots, resizing and migration.
Off-site backups with Restic
Encrypted, deduplicated backups to a storage VPS in a different jurisdiction, in about twenty minutes — including the restore test almost everybody skips.
Snapshots and restore points
What snapshots protect against, what they do not, and why crash-consistent is not the same as application-consistent when the disk holds a live database.
Resizing and migrating servers
Growing vCPU, memory and disk, moving a server between jurisdictions, and the downtime to expect from each — plus why disk cannot be shrunk afterwards.
API & automation
REST API, Terraform and cloud-init.
REST API reference
Server lifecycle, power, snapshots, firewall rules and reverse DNS over REST — the same interface the control panel itself uses, with signed webhooks.
Terraform provider
Declare servers, SSH keys and firewall rules as code, and spread a fleet across jurisdictions in a two-line change instead of eight trips through a panel.
cloud-init recipes
Ship a server that is already hardened at first boot, so the window between “server exists” and “server is secured” never happens. Recipes you can paste.
Something the docs did not cover?
Support answers technical questions 24/7, with a 12-minute first-reply target.
7-day money-back guarantee · No KYC · Cancel any time from the panel