the on-call platform that helps developers and agents resolve downtime faster, together.

e e s № b b e ° b b • e b • ! e ! • • e s ¤ ! b e e e b • p p e № • e ‡ ¶ … e ‡ ‡ ¶ ¤ e s • s s b s s e s ° ¿ p ¶ b ¿ b ‡ e e e ° s ¶ № p e e b ‡ p e e ‡ … e … ‡ ¿ ° s • b s § s ¿ e s § p ‡ ¶ p e e s ! … • p ¤ s ¤ e s e s e s e • e ° ¿ e p ! № b • ¿ p e ! № ‡ e ° ° … e • p e ° e b № s ¤ § s № … ¿ № s ¶ e ¿ § … e … s ¿ ¶ e № e e b № s b ‡ § ‡ ‡ … s e ¿ b e e § b ! b ¶ ¤ ¤ e ° e s s b ! e § b § e e № b • p ¿ § ! e b … p b № p ¶ e ! ¶ b ‡ ! e ¤ ¿ ¿ № s s b b ¶ b ‡ s e … ° ¿ ¤ p e e ¤ e p b • § § b ¿ • № № e §

key features:

· beyond human rotations: relay alerts to people and agents in parallel (or sequentially), however you want

· developer-native on-call experience: api & sdk driven, and built for the ai era

· put the agents you use on-call: cursor cloud agent, devin.ai, claude code, openai codex, aws devops agent, opencode, and growing

· cli for triage: claim alerts, manage relays and schedules from the terminal. json output for scripting

· infrastructure as code: define relays in YAML. plan and apply changes, simulate to catch misconfigs before they beep someone at 3am

· terminal-native dashboard: real-time TUI for monitoring incidents as they happen

simple pricing:

· priced per relay: $70/active relay/month. no alerts, no charge.

· enterprise: book a call with us

why beeps?

we built beeps because on-call is still stuck in the past: human-only rotations, schedules built in confusing uis, and tools that weren't designed for a world where AI agents can respond to incidents. beeps is the on-call platform for teams that want humans and agents working together.