Firewatch Cloud
Know who is responsible, reach them on the right channel, and escalate until somebody owns the alert.
Northstar Engineering/ Workspace
Docs▣ Payments API Jul 25, 2026, 9:41 AMWebhook source
Error rate crossed the production threshold inus-east-1. Firewatch matched the Payments API and started its production escalation policy.
Permanent incident events, newest first by default.
Share what you checked, changed, or learned…
Add noteThe alert lifecycle
Ingest the signal.
Find who is on call.
Use every configured channel.
Record explicit ownership.
Advance when time runs out.
Preserve the full timeline.
Schedules
Build timezone-aware rotations, schedule overrides, alternate coverage, weekday exclusions, and future participant changes. Month and week views make handoffs and gaps obvious.
Escalation
Choose the responders, channels, wait times, and fallback steps for each service. Firewatch requires acknowledgement and advances the policy automatically.
Managed delivery
Cloud customers get managed upgrades, backups, availability, and notification delivery. Your team keeps the transparency of an open-source core without carrying the pager for the pager.
Portable by design
Firewatch’s open-source core gives you inspectable behavior, documented APIs, exportable data, and a self-hosting path.
Ready when production is not