Development previewCP1-CP10 implemented

Website monitoring for a whole fleet

Know which site needs you.

Web Fleet watches availability, incidents, TLS, DNS, redirects, headers, pages and links across every website you care about. Performance history, manual browser Audit and privacy-first analytics are now implemented in development.

The monitoring foundation is implemented in development. There is not yet a public release or supported installer.

FLEET / OVERVIEW12 websites
HEALTHY10
DEGRADED1
DOWN1
Needs attention
docs.example.com3 newly broken links2m
shop.example.comHTTP timeout · incident open6m
client-a.comTLS expires in 12 days18m
nift.dev43 ms
trestle.cv51 ms
example.com67 ms
01Remote checksImplemented
02Fleet healthImplemented
03Website healthImplemented
04Site auditsManual · history opt-in

The public website is the system

Monitoring that understands websites.

Availability is only one signal. Web Fleet keeps the important observations together so a large portfolio can be understood without opening every site individually.

01

Availability

SSRF-safe HTTP checks, latency, failure classification, scheduler health and manual checks.

02

Incidents

Coherent failure and recovery lifecycles with in-app alert delivery instead of one alert per request.

03

TLS + DNS

Certificate validity and expiry plus A, AAAA and CNAME observations with meaningful change history.

04

HTTP surface

Redirect chains and configurable security/header expectations, recorded independently from uptime state.

05

Pages + links

Bounded, robots-aware crawling with sitemap discovery, broken links and fleet-level regressions.

06

Audit

Optional browser-rendered quality audits will track performance, accessibility, best-practice and discoverability regressions before the analytics phase.

Small install, large model

Start with one binary and SQLite.

Web Fleet is designed to remain comfortable for a self-hoster or freelancer while keeping groups, site boundaries and subsystem separation strong enough to grow into agency and enterprise deployments.

Sites can already be searched, grouped, filtered and paged. The fleet overview surfaces attention across the portfolio while every site keeps its own detailed health history.

No agent required

Point Web Fleet at a URL.

Public monitoring does not require code on the monitored website. The optional privacy-first analytics tracker can report from static hosting such as GitHub Pages to a central self-hosted Web Fleet server.

# Public installer is not released yet.
# Development currently runs from source.
go run ./cmd/webfleet

Open development

The monitoring foundation is alive.

CP1 through CP25 are implemented in development. The next phase focuses on multi-user, agency and enterprise-scale controls.