Documentation
Product overview
Web Fleet is a self-hosted control room for understanding websites. It observes the public web surface and combines health, history and optional traffic analytics.
Questions Web Fleet is designed to answer
- Which websites need attention right now?
- Did availability or response time regress?
- Is a TLS certificate approaching expiry?
- Did DNS change unexpectedly?
- Did a change introduce broken links or redirects?
- Which pages are being visited and where is traffic coming from?
- Can a freelancer or agency see the health of every client site without checking them individually?
What Web Fleet is not
Web Fleet is not intended to become a hosting platform, CDN, DNS provider or host telemetry agent. Those responsibilities create very different operational and security models.
HTTP, pages, links, TLS, DNS, headers, traffic and website changes.
CPU, memory, disks, processes and machine/service telemetry.
Same product at different scale
The development dashboard already supports groups, search, group filtering and direct page-number navigation for larger inventories. Organizations and scoped multi-user access remain later enterprise checkpoints.
Organization
└── Group / client / team
└── Site
├── Domains
├── Monitors
├── Analytics
├── Incidents
└── Deployment history
Health model
The fleet dashboard uses a small set of meaningful health states instead of treating every observation as an incident. The current availability model is:
| State | Meaning |
|---|---|
| Healthy | No current observation requires attention. |
| Warning | A first non-status failure occurred and needs another observation before Web Fleet calls the site down. |
| Degraded | The site responded, but an HTTP status fell outside the configured expected range. |
| Down | Availability checks establish a current outage. |