hi all, joey parsons here, founder & ceo of beeps (https://beeps.dev). we’ve been frustrated with the state of on-call and are on a mission to fix it, starting with solving on-call problems for nextjs developers.

we spent a bit of time with engineers in this space and identified two problems we’ve built solutions for: getting straight to the facts: beeps helps you get to context quickly when problems arise. we automatically listen for alerts from your observability systems like sentry, axiom, datadog and others and when things go wrong, we’ll track down all the context you usually get from opening tabs in your browser. things like your most recent deploys, the diffs of recent code changes, and checking to see if any of the external services (apis) are down. knowing if it’s you, or them: we automatically detect the service providers you use to build your app and will let you know if they’re having issues. developers typically will think it’s their code – and we help you eliminate the external provider as a potential cause quickly.

on-call has been a pain for almost every engineer i’ve ever talked to. i’m sure you all have thoughts on what we’ve built and where we should go next.

give it a shot and let us know what you think.