I’m Ali a solo founder and ex-SRE. After working at Dynatrace and Gartner, I left my job to build RobinRelay, a Slack-native assistant for noisy alerts and incident memory.
The Problem: SRE and DevOps teams get flooded with alerts in Slack. People investigate in threads or the main alert channel… and then the context disappears.
So when the same alert happens again (next week, another team, different cluster), everyone starts from scratch.
What I’ve Built: RobinRelay watches your alert channels and automatically replies when a recurring alert is detected. It brings back:
Past thread replies: Root cause + fix summaries Cross-channel memory (Team A solves it, Team B sees it next time) We’ve also added Slack-native dashboards like:
- Alert heatmaps to show noisy days - Insights directly inside the Slack App Home tab — no need to leave Slack
RobinRelay runs in one company across 3 live Datadog alert channels and delivers context in under a minute.
About Integrations: No rigid setups. RobinRelay listens directly to Slack channels and automatically parses any alert format using LLMs, including custom bots. That means unlimited integration possibilities without any API keys, webhook configs, or vendor lock-in.
Seamless Setup: Install the app Choose the alert channel RobinRelay starts reading historical alerts + discussions to surface useful memory and insights — no manual migration needed. Demo (1:40) YouTube: https://www.youtube.com/watch?v=RSY7-AZJqU8
Or join the public demo workspace to see it live: https://join.slack.com/t/robinrelay/shared_invite/zt-39kf33n...
Looking For Feedback from teams who:
Handle alerts in Slack Run on-call rotations Care about reducing alert fatigue and rework I’m happy to answer questions or ship improvements based on feedback!