Writing and runbooks
What we learned running our own hardware, written up properly — including the postmortems.
What actually happens when you order an in-stock server
From the moment you click order to root access on a racked machine — the actual steps, and where the time goes.
Uplink flap, 9 July — what happened
A faulty optic in a LAG member caused 4 minutes of packet loss. Timeline, root cause, and the two things we changed.
Why we own our racks instead of renting capacity
Owning the hardware and the racks costs more up front. Here is what it buys you, and where it does not help.
Hardening a fresh Ubuntu 24.04 VPS in ten minutes
SSH keys, nftables, unattended-upgrades and fail2ban — the config we run on our own boxes, copy-pasteable.
New in-stock dedicated builds and faster provisioning
Four in-stock builds added, plus faster deployment for orders placed during business hours.
Dedicated server or cloud server: how to actually decide
Fixed resources versus elastic ones, and the workloads where each choice saves you real money.
What we actually log, and for how long
Access logs, netflow and console history — what is retained, who can read it, and when it is deleted.
We have never sent a newsletter. Follow the feed and you get postmortems and maintenance windows, nothing else.