We chose to self-host this website rather than relying on a managed platform or website builder.
Not because those tools are inherently bad, but because ownership matters. By running our own infrastructure, we understand every layer involved: DNS, TLS, the web server, and the content itself. There are no opaque defaults, hidden dependencies, or vendor-imposed constraints.
This approach mirrors how we build software systems for clients. We prefer simple, explainable architectures that can be reasoned about, monitored, and evolved over time. Convenience has value, but not at the expense of clarity or control.
Self-hosting also keeps the surface area small. There is no build pipeline, no framework churn, and no unnecessary complexity. The site is fast, secure, and does exactly what it needs to do.
Most importantly, this setup is reproducible. The same approach can be applied to internal tools, documentation sites, or client-facing systems where reliability and understanding matter more than novelty.
In a world of abstraction, choosing to own the basics is a deliberate engineering decision.