Insights
Engineering notes, infrastructure deep dives and practical guides from the Exotecho team.
The claim Teams adopt infrastructure-as-code for the reproducibility and then store the one file that makes it reproducible — the state file — on a laptop, in a Git repository, or...
Read article
The claim A small business does not need a backup appliance, a vendor contract, or a six-figure disaster-recovery product to protect its data properly. A single open-source tool wr...
Read article
The claim A monitor that fetches your homepage and checks for a 200 status confirms the least useful thing about your business: that a web server is running. The failures that cost...
Read article
The claim Every public SSH port on the internet receives thousands of password guesses a day within hours of coming online. The standard responses — moving the port, installing fai...
Read article
The claim Every long-running process on a production Linux host should be a systemd unit. Not pm2, not a screen session someone detached from in the spring, not nohup & in a deploy...
Read article
The claim Most staging environments differ from production in ways that guarantee they cannot catch the failures people expect them to catch: a smaller database, different configur...
Read article
The claim Businesses spend real money on redundant servers, replicated databases and multi-region backups, then protect the domain name that points at all of it with a shared passw...
Read article
The claim Caching a dynamic page for one second sounds pointless. It is the single highest-leverage configuration change available to a small site, because it converts an unbounded...
Read article
The claim If more than four conditions in your system are permitted to page a human at three in the morning, none of them will be taken seriously by March. Alert fatigue is not a d...
Read article
