keephq.dev (legally registered as Keep Alerting Inc.) is an open-source AIOps and alert management platform founded to help engineering teams manage alerts at scale. Backed by Y Combinator and Runa Capital, Keep has grown to approximately 100 team members, earned 9,200+ GitHub stars, and was recently acquired by Elastic.
Alert fatigue is a real problem. SRE teams at fast-growing companies can receive thousands of alerts per day—many of them redundant, mislabeled, or simply irrelevant. Most organizations patch the problem with spreadsheets, Slack threads, and manual runbooks. Keep was built to replace all of that.
keephq.dev is the open-source AIOps platform quietly changing how engineering teams handle incident response and alert management. With 110+ integrations, a YAML-based workflow engine, and enterprise-grade AI correlation, Keep has attracted users from global giants like IKEA, Siemens, Rakuten, and Monday.com—alongside a developer community of 700+ and counting.
This guide covers everything you need to know about keephq.dev: when it was founded, who built it, how it’s funded, what the platform actually does, and what the recent Elastic acquisition means for users. Whether you’re evaluating Keep as an AIOps solution or simply researching the company, this is the most complete resource available.
How and When Was keephq.dev Founded?
Keep Alerting Inc. was founded to tackle a problem that every scaling engineering organization eventually hits: too many alerts, not enough context. The company emerged from the Y Combinator accelerator program, which has historically been one of the strongest early signals of startup quality—past YC alumni include Airbnb, Stripe, and Dropbox.
While a precise founding date has not been officially published by the company, Keep’s early GitHub activity and YC participation place its origins in the early 2020s. The platform gained significant traction as the open-source AIOps category began drawing more attention from DevOps and SRE practitioners looking for alternatives to expensive, closed-source incumbent tools.
Keep is registered legally as Keep Alerting Inc., operating publicly under the brand name KeepHQ and through the domain keephq.dev.
Who Founded Keep (keephq.dev)?
Keep was co-founded by a team of engineers with backgrounds in infrastructure, operations tooling, and developer experience. The founding team’s contact email—founders@keephq.dev—is publicly listed in Keep’s privacy policy, which reflects the startup’s lean, founder-led culture.
The founders brought a clear thesis to the market: alert management should be open, extensible, and deeply integrated into the tools engineers already use—not locked behind enterprise contracts or proprietary APIs. That philosophy is evident in every layer of the Keep platform, from its open-source GitHub repository to its bidirectional provider architecture.
How Many Employees Does keephq.dev Have?
As of the most recent publicly available data, keephq.dev has approximately 100 team members, referred to internally as “Keepers.” This headcount reflects a lean, high-output team typical of venture-backed developer infrastructure startups.
The Keepers community extends beyond full-time staff. Keep’s open-source contributor base is active on GitHub, where the repository has earned 9,200+ stars—a meaningful benchmark of community trust and engagement in the developer tools space. The broader user and contributor community numbers over 700 members, accessible via Keep’s dedicated Slack workspace.
For a company operating at this scale, the ratio of community engagement to headcount suggests a product-led growth model where the open-source platform drives organic adoption before enterprise sales conversations begin.
How Much Funding Has keephq.dev Raised?
Keep Alerting Inc. has raised funding from two notable investors:
- Y Combinator — one of the world’s most prestigious startup accelerators, providing both capital and network access
- Runa Capital — a venture capital firm with a strong focus on open-source and developer-first infrastructure companies
The exact total funding amount has not been disclosed publicly. However, backing from Y Combinator alone is widely recognized as a significant vote of confidence, given the program’s rigorous acceptance criteria and track record with infrastructure startups. Runa Capital’s focus on open-source businesses further validates Keep’s core go-to-market strategy.
Given the subsequent acquisition by Elastic (discussed below), it’s likely that Keep’s funding runway was sufficient to build the product to a point of strategic value—rather than raising large rounds to scale sales independently.
What Does keephq.dev Do? (Product & Platform Overview)
keephq.dev is an open-source AIOps and alert management platform that gives engineering teams a centralized, intelligent system for managing alerts across complex environments. The platform is built around four core steps: integrate, collect and query, automate, and apply AI.
Keep consolidates alerts from every monitoring tool, incident response system, ticketing platform, and CMDB in an organization’s stack. Instead of toggling between Datadog, PagerDuty, Grafana, and Jira tabs simultaneously, engineers get a single pane of glass—with the ability to query, filter, and act on alerts from one interface.
The platform is available in three deployment tiers:
- Self-Hosted (OSS): Free, open-source toolbox for teams that want full control over their infrastructure
- Cloud: Fully managed deployment with a free trial available at platform.keephq.dev
- Enterprise: Cloud and on-premises options with unique AI-driven alert correlation and summarization features
This tiered model makes Keep accessible to individual contributors and small startups, while scaling all the way up to global enterprises.
Key Features of the Keep AIOps Platform
Bidirectional Integrations Across 110+ Providers
Keep connects with over 110 providers across monitoring, IRM, ticketing, source control, change management, and CMDB categories. What makes Keep’s integration system distinctive is its bidirectional architecture—alerts and signals stay in sync between Keep and the connected tools, rather than flowing one way.
Supported integrations include AppDynamics, Datadog, PagerDuty, Jira, Grafana, Prometheus, GitHub, Slack, and Discord, among many others. Teams can also build custom provider integrations to fit proprietary or niche tooling.
Single Pane of Glass for Alert Management
Keep’s alert console uses a Common Express Language that gives teams advanced querying, slicing, and data analysis capabilities across all connected sources. Rule-based grouping reduces noise and improves data clarity—two of the core pain points in high-volume alert environments.
This unified view means that SREs and on-call engineers no longer need to context-switch between tools during an active incident. All relevant alert data surfaces in one place, fully queryable.
YAML-Based Workflow Engine
Keep’s workflow engine is modeled after GitHub Actions but adds a UI layer for teams that prefer a visual interface over raw YAML. Engineers can use the workflow engine to query MySQL databases, enrich alerts with query results, update Jira tickets automatically, and execute Python scripts—all within a single workflow definition.
The result is a flexible, code-friendly automation layer that fits naturally into existing DevOps workflows without requiring a separate orchestration tool.
AI-Powered Alert Correlation (Enterprise)
For enterprise teams managing thousands of daily alerts, Keep’s most powerful feature is its AI-driven alert correlation engine. Available exclusively on the Enterprise tier, this capability uses past incident data and a continuously updated knowledge base to group related alerts into high-level incidents automatically.
The system improves over time through a continuous feedback loop, meaning the more an organization uses Keep, the more accurate its correlation becomes. This directly reduces mean time to detect (MTTD) and mean time to resolve (MTTR)—the two metrics that matter most during incidents.
Alert Quality Health Checks
Keep also provides a no-signup alert quality check tool at platform.keephq.dev/health. Teams can run provider health checks against Datadog, CloudWatch, Grafana, PagerDuty, and GCP Monitoring to immediately surface quality metrics about their existing alerting setup.
Who Uses keephq.dev? (Customers & Use Cases)
Keep’s customer base spans startups and global enterprises. Publicly referenced organizations using the platform include IKEA, Siemens, Rakuten, Monday.com, Retool, Airtel, Wolters Kluwer, Autodoc, HiBob, and Radius AI.
This diversity reflects Keep’s tiered deployment model. A Series A startup can self-host the open-source version and contribute back to the repository, while an enterprise like Siemens can run the platform on-premises with full AI correlation features enabled.
Primary use cases include:
- Alert consolidation: Replacing fragmented multi-tool monitoring with a single operational view
- Incident response automation: Triggering runbooks, creating tickets, and notifying on-call teams automatically
- Alert enrichment: Adding contextual data to raw alerts so engineers have everything they need before opening a ticket
- Noise reduction: Using rule-based grouping and AI correlation to filter out low-signal alerts
Keep’s Acquisition by Elastic
In 2025, Keep announced that Keep is joining forces with Elastic—the company behind Elasticsearch, the Elastic Stack (ELK), and Elastic Observability. The announcement was made on the Elastic blog and confirmed on keephq.dev’s homepage.
This acquisition represents a significant strategic development. Elastic has long been a foundational layer in observability stacks worldwide, and integrating Keep’s AIOps and alert management capabilities into the Elastic ecosystem gives Elastic a much stronger incident response story.
For existing Keep users, the acquisition signals increased investment in the platform’s development rather than a wind-down. Elastic’s scale and resources are likely to accelerate Keep’s roadmap, particularly on the enterprise and cloud tiers. For engineers already using the Elastic Stack, Keep’s acquisition introduces a natural path to adding automated alert management and AI-driven incident correlation without switching platforms.
How to Contact keephq.dev Customer Service
Keep does not publish a customer service phone number. Support and contact options are as follows:
- Founders/general inquiries:founders@keephq.dev
- Privacy-related queries:privacy@keephq.dev
- Community support: Keep’s Slack workspace (accessible via keephq.dev)
- Technical documentation and issues: GitHub at github.com/keephq/keep
- Enterprise and demo bookings: keephq.dev/meet-keep
For teams evaluating the platform, booking a demo via the Meet Keep page is the most direct route to a product conversation with the Keep team.
keephq.dev vs. Alternatives: How Does Keep Compare?
How does keephq.dev compare to PagerDuty?
PagerDuty is a closed-source, SaaS-only incident management platform focused primarily on on-call scheduling and escalation policies. Keep differs in three key ways: it is open-source, supports self-hosted deployment, and places a heavier emphasis on alert correlation and workflow automation rather than just notification routing.
Choose Keep if your team wants code-level control over alert logic, an extensible integration layer, and open-source transparency. Choose PagerDuty if your primary need is polished on-call management with minimal configuration.
How does keephq.dev compare to Grafana OnCall?
Grafana OnCall is open-source and focused on on-call alerting within the Grafana ecosystem. Keep is monitoring-tool agnostic, supporting 110+ providers across a broader range of categories. Keep also adds a dedicated AI correlation layer at the enterprise tier that Grafana OnCall does not currently match.
How does keephq.dev compare to OpsGenie?
OpsGenie (now part of Atlassian) integrates tightly with the Atlassian suite—Jira, Confluence, and Bitbucket. Keep also integrates with Jira but operates independently of any single vendor ecosystem. For teams outside the Atlassian stack, Keep offers more flexibility and a lower total cost of ownership via the open-source tier.
Keep Building on a Stronger Foundation
Keep Alerting Inc. has built something genuinely useful: an open, extensible, and increasingly intelligent platform for the alert management problem that quietly drains productivity from engineering teams every day. The combination of Y Combinator credibility, Runa Capital backing, a 9,200+ star GitHub repository, and acquisition by Elastic puts keephq.dev in a strong position as AIOps adoption accelerates.
For startups and enterprises exploring AI tools for IT operations, Keep is one of the most credible open-source options available. The self-hosted tier removes the barrier to entry entirely, while the Enterprise tier delivers the kind of AI-driven correlation that high-volume environments genuinely need.
The Elastic acquisition doesn’t close the story for Keep—it opens the next chapter. Teams evaluating the platform today are likely getting in ahead of a significantly more capable and well-resourced product.
Start with the free cloud trial at platform.keephq.dev, or explore the open-source repository on GitHub to see how Keep fits into your existing stack.
Frequently Asked Questions About keephq.dev
What is keephq.dev?
keephq.dev is the web domain for Keep, an open-source AIOps and alert management platform legally registered as Keep Alerting Inc. Keep helps engineering teams consolidate, query, automate, and AI-correlate alerts from 110+ monitoring and incident management tools.
When was keephq.dev founded?
Keep Alerting Inc. was founded in the early 2020s and participated in the Y Combinator accelerator program. An exact founding date has not been officially disclosed by the company.
Who are the founders of keephq.dev?
Keep was founded by a team of engineers with backgrounds in infrastructure and developer tooling. The founding team can be contacted directly at founders@keephq.dev, as listed in Keep’s privacy policy.
How many employees does keephq.dev have?
keephq.dev has approximately 100 full-time team members, referred to internally as “Keepers.” The platform also has an open-source contributor community of 700+ members on GitHub and Slack.
How much funding has keephq.dev raised?
Keep Alerting Inc. has received funding from Y Combinator and Runa Capital. The total funding amount has not been publicly disclosed.
Is keephq.dev free to use?
Yes. Keep offers a free, self-hosted open-source version available on GitHub. A free cloud trial is also available at platform.keephq.dev. Enterprise pricing requires a demo booking via keephq.dev/meet-keep.
What is the difference between Keep OSS, Cloud, and Enterprise?
Keep OSS is a self-hosted, community-supported open-source deployment. Keep Cloud is a fully managed version with a free trial. Keep Enterprise adds AI-driven alert correlation, on-premises deployment options, and dedicated support—designed for organizations managing thousands of daily alerts.
Is keephq.dev being acquired?
Yes. Keep announced it is joining forces with Elastic, the company behind Elasticsearch and the Elastic Stack. The announcement was published on the Elastic blog and confirmed on keephq.dev’s homepage.
What is keephq.dev’s customer service contact?
Keep does not offer a phone support line. Contact options include founders@keephq.dev for general inquiries, privacy@keephq.dev for data-related requests, and the community Slack workspace for peer support. Enterprise customers can book a direct conversation at keephq.dev/meet-keep.
