Know when a client’s site is down.
Know what your cluster costs.

Two open-source tools for the people who run other people’s infrastructure. One is shipping and you can run it today. The other is honestly still being built.

Warden
Shipping now

Twenty clients. One dashboard you actually open.

Group the monitors by client. Each group gets its own branded status page and its own private login, so the client checks their services themselves instead of asking you. Here is what happens between the check and the phone call you didn’t have to take.

  1. 1.0

    It checks the endpoint

    HTTP and HTTPS, from 10 seconds up. You set the method, headers, body, timeout, retries and which status codes count as healthy — per monitor, not per account.

    Protocol
    HTTP / HTTPS
    Interval
    from 10s

  2. 2.0

    It confirms before it wakes you

    One bad response is not an outage. Warden re-checks against a confirmation threshold before it calls anything down, holds a cooldown so a flapping endpoint can’t page you nine times, and confirms recovery before it says the thing is back.

    Guards
    threshold · cooldown · flap detection
    Recovery
    confirmed, not assumed

  3. 3.0

    It tells you, then it tells your client

    Alerts go to Slack or a JSON webhook. The incident lands on the client’s own status page with a timeline they can read themselves — so the email asking whether you’ve noticed never gets written.

    Alerts
    Slack · JSON webhook
    Client-facing
    status page · timeline · RSS
10s
fastest check
4
roles
∞
team seats
AGPL-3.0
licence
Book a setup call Self-host it free
Recon
In development

Kubernetes cost intelligence.

A cluster spends money in places nobody remembers deploying. Recon is meant to map the spend to the namespace and tell you what to cut. Meant to — it is being built, there is nothing to run yet, and this section will stay this short until there is.

  • Cost broken down per namespace Planned
  • Idle resources surfaced Planned
  • Right-sizing recommendations Planned
Read where Recon is

What isn’t built yet.

Published so you can decide with the real picture, and without dates, because a date we invented would be worth exactly as much as a feature we invented. If one of these is a dealbreaker, say so on the call and we’ll tell you straight whether to wait.

  • Checks from more than one place

    Planned

    Every check runs from the single host Warden lives on. One host means one opinion about whether a site is up. Remote probes are the next big piece of work.

  • On-call rotations and escalation

    Planned

    Alerts fire into Slack and webhooks today, and every enabled channel gets every event. Rotations, escalation policies and routing a client’s alerts to their own channel are on the list.

  • Recon — Kubernetes cost intelligence

    In development

    Namespace-level cost breakdown, idle resource detection and right-sizing. Being built now; nothing to install yet.

Bring your client list.

We build the groups, the status pages and the logins with you on the call, and you leave with it running.

Book a setup call