WordPress on Hetzner: Plugin Architecture for Ops

WordPress on Hetzner: Plugin Architecture for Ops TL;DR Treat ops as WordPress features : expose safe knobs in wp-admin, store config as code, and trigger idempotent server actions. Use a small plugin “control plane” to manage provisioning, backups, and performance defaults for WordPress on Hetzner. Prefer asynchronous jobs, signed callbacks, and least-privilege tokens over long-running admin requests. Build around Hetzner primitives (Cloud, Volumes, Snapshots) and WordPress primitives (Actions, Cron, REST, WP-CLI). The problem: ops entropy when you self-host If you run WordPress on Hetzner, you probably started for the right reasons: predictable pricing, good network, and infrastructure you actually control. The pain usually appears later: Provisioning becomes a mix of “copy this server image,” hand-edited Nginx configs, and one-off shell scripts. Backups exist, but nobody is sure if restores have been tested recently. Performance tuning drifts between environments (dev/staging/prod)