What it doesn’t do (yet)

An honest list of things you might expect that aren’t there today.

• No automatic discovery: nodes are declared by hand, from a manifest or via MCP. There’s no connection to Cloudflare, GitHub, Hetzner or others to populate the map.
• Alerts only for outages: email, webhook, Slack and Telegram fire when a node goes down or an agent stops answering, but not for expiring certificates, expired secrets or drift, which stay visible only in the app.
• No “send a test” button for the notification channels: to try them you need to take a test node down.
• No domain expiry: the TLS certificate is checked, the domain’s registration at the registrar isn’t.
• No team invites: the data model is ready, the UI isn’t.
• Vault integrations are labels: they don’t read secrets from 1Password, Doppler and the like.
• No history: the status is the last check’s, there’s no history or chart over time.
• Modules are one level deep: the aggregated status excludes modules nested in the linked map, and there’s no breadcrumb to go back (use the map switcher).
• Modules are read-only: you can’t edit inner nodes from the expanded module, only in the source map.
• Module loops: the check is client-side only.
• No group management: they can’t be renamed, recolored or deleted from the UI.

This page is updated when the product changes. If something here doesn’t match what you see in the app, that’s a documentation bug: tell us.