Skip to main content
Uptime Kuma ships as a module contract in StackKits v0.16.0, but the initial native v2 StackSpec does not select it. A fresh Basement or Cloud Kit therefore has no generated Uptime Kuma address and no public monitoring configuration path. Do not invent a module selection from an older schema. When a released StackSpec exposes monitoring configuration, this page will document the exact fields and setup flow. Until then, use the lifecycle verification described in Operate a StackKit to assess the stack itself. For any separately operated monitoring service, add checks only for routes you are authorized to monitor. Protected routes need an intentional health endpoint or an expected authentication response; weakening route protection to obtain HTTP 200 is not a valid monitor setup. StackKits publishes local observation and verification evidence. It does not require or imply a hosted monitoring service. See Uptime Kuma for the current release boundary.