Skip to main content
Uptime Kuma ships as a v0.16.0 module contract, but the initial native v2 StackSpec does not select it. Do not infer an active monitor set from the archive alone. Add monitors only for services you operate. For protected routes, use an intentional health endpoint or expect the configured authentication response; do not weaken route protection merely to make a monitor return HTTP 200. There is no supported Uptime Kuma configuration example for the initial v0.16.0 StackSpec. The StackKits lifecycle remains the source of stack verification even when you operate a separate monitor.