Target validation comes first.
Monitor creation uses LaunchLock target validation and SSRF protections instead of blindly polling user input.
Monitoring
Keep launch surfaces watched after the first scan.
Guarded uptime monitors and public status data keep the same safety model as scans: validate the target, track history, and expose honest status.
Open monitoringMonitor loop
Target
Checks
Incidents
Status
Report signals
ChecksHTTP monitor history
StatusPublic component rollups
AlertsBackend dispatch path
Checks
HTTP monitor history
Status
Public component rollups
Alerts
Backend dispatch path
Incidents stay attached to history.
Thresholded incidents, uptime windows, and timeline data are designed to support post-launch review.
Alert routing is staged carefully.
Customer-owned destinations need auth, project ownership, and encrypted storage before self-serve rollout.