Maintenance

Running self-hosted infrastructure is not a one-time setup — it requires ongoing attention. With organising, designing, living, and archiving carried elsewhere, what's left here is narrower than it first sounds: not the whole burden of keeping infrastructure alive, just the technical discipline of keeping it running once everything else is already in place.

That discipline is fundamentally stewardship's work — keeping the flame alight. It's less about heroic fixes than steady attention: noticing before a small problem becomes an outage, and renewing the knowledge needed to respond when it doesn't.

Tech

The technical layer: keeping software up to date, monitoring for issues, managing backups, and handling the occasional failure. Most of this can be automated or delegated to tooling like Coolify, but someone needs to understand what's running and be able to respond when something breaks.

See Infrastructure for provisioning and Terraform, and System for updates, Docker, and the services running on top.

The technical side of maintenance connects closely to Planning and Ownership, which cover how work stays visible and who is responsible for what.