Why We Replaced Keep: Introducing groundcover Dispatch Center
Blog post from Groundcover
Groundcover faced challenges with Keep, an open-source notification engine, due to its complexity and inefficiencies at scale, leading to operational headaches and difficulty in debugging issues. As Keep was no longer meeting their needs, Groundcover developed their own system, the Dispatch Center, leveraging the Temporal open-source workflow engine to manage notification routing with gcQL instead of complex YAML workflows. This new system allows for transparent configuration, live previews, and simulation of alerts, offering better control and diagnostics. The Dispatch Center is managed through Terraform, allowing configurations to live in version control, and it integrates seamlessly with Groundcover's existing infrastructure. While running alongside Keep during the transition, the Dispatch Center is poised to enable future automation and AI-driven notification management, transforming the notification layer from a limiting factor into a strategic asset.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Kubernetes | 3 | 1,840 | 308 | 106 | +33% |
| AI Agents | 2 | 4,545 | 963 | 231 | +27% |
| Observability | 2 | 3,204 | 716 | 172 | +14% |
| OpenTelemetry | 1 | 622 | 137 | 51 | +51% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.