BeaconAPP2:04
Error rate 18% on checkout
checkout-api · 312 failed payments in 3 minutes
engDeploys, incidents and code review
One room per release, one per incident, review requests in the reviewer's DMs. The person on call hears about what's on fire. Everyone else hears about it once it's out.
Declare it and Hum opens the room, pages the on-call, starts the huddle and keeps the timeline. Try it: the checkout is down.
eng-alerts
BeaconAPP2:04
Error rate 18% on checkout
checkout-api · 312 failed payments in 3 minutes
inc-412
01Alerts land in a channel forty people have muted.
Beacon pages the on-call in a DM and opens #inc-412 with the owners of the service.
02Review requests drown under deploy bots.
Reviews go to the reviewer's DMs. Deploys go to #deploys. Merges go to the release.
03The postmortem starts with “who remembers 2 a.m.?”
The incident room writes its own timeline, and the huddle notes are already in it.
04The Monday sync exists because nobody can read the backlog.
Each engineer reads a 30-second catch-up of their channels, with links to the source.
A starting set you can copy in one click when you create a workspace. Pick one to see who's in it and what posts there.
CHANNELS
#launch
This week's release: decisions in the channel, arguments in threads.
Members
ATMS18 people
Apps that post here
ForgeShipyard
Theo Laurent
RC2 is on staging. Pricing toggle fixed, test added.
“We used to start every Monday with a 40-minute sync. Now we read the catch-up over coffee and save the call for the one thing that needs it.”
For most teams, yes: Beacon pages the on-call through Hum and gets through quiet hours. Keep a phone call fallback for SEV-1 if your policy needs one.
Bring the team, connect your tools, and let Hum keep everyone in the loop. Free for teams up to 10.