Elastic has acquired two AI incident-response startups in fourteen months. Keep Alerting handles alert correlation and automated remediation. Deductive AI handles root-cause investigation. Together they cover most of an AI site reliability engineer, assembled through two separate deals rather than one internal roadmap.
Fourteen months is the distance between Elastic's acquisition of Keep Alerting and its agreement, confirmed in Elastic's own post Wednesday, to buy Deductive AI. That gap is the number worth sitting with.
Deductive Spent Three Years Building an AI Site Reliability Engineer
Sameer Agarwal and Rakesh Kothari founded Deductive AI in 2023 after years as engineering leaders at Databricks and ThoughtSpot, where by their own account half their time went to shipping features and the other half went to debugging (Deductive AI, 2026). They built what the industry calls an AI SRE, artificial intelligence performing the work of a site reliability engineer: an agent that connects to a customer's code and telemetry, forms a hypothesis about what broke, and tests it against the evidence until it can name the reason an incident happened, the part most monitoring tools skip (Azarmi, 2026).
Three years is a short window to earn an engineering team's trust with production incidents. DoorDash and Foursquare gave Deductive that trust anyway. Sameer Agarwal, Deductive's co-founder, later credited both customers with trusting a ten-person company "with some of their most complex production challenges" (Agarwal, 2026; PitchBook, 2026). By the time Elastic came calling, Deductive had reached roughly $1 million in annual recurring revenue on a $7.5 million seed round led by CRV, a round that had valued the company near $33 million (TechCrunch, 2026; PitchBook, 2026). TechCrunch first reported the talks in mid-June, citing a deal value of up to $85 million; Elastic's own post this week confirmed the agreement without disclosing terms (TechCrunch, 2026; Azarmi, 2026).
This Is the Second Time Elastic Has Bought This Exact Capability
In May 2025, Elastic completed its acquisition of Keep Alerting, a Tel Aviv company behind an open-source platform for artificial intelligence for IT operations, or AIOps, that deduplicates and correlates alerts, then automates remediation through workflow-as-code. Ken Exner, Elastic's chief product officer, framed the deal as merging Keep's automation with what he called the speed and scale of Elasticsearch (Elastic Security Labs, 2025).
Keep decides what gets flagged and what gets fixed on its own. Deductive investigates why the incident happened in the first place. Stack the two together and Elastic now owns most of an AI SRE, built through two acquisitions inside fourteen months instead of one product roadmap drawn up in advance.
Two deals in fourteen months is a pattern.
Buying the Capability Is Faster Than Building It
Elastic says plainly what comes next in its own post: it looks forward to sharing more about its product roadmap in the coming months (Azarmi, 2026). The plan for merging Keep's remediation engine with Deductive's investigation engine had not been written down in public even as the deal closed.
For an Elastic Observability customer weighing a multi-year renewal, that detail changes the bet. The purchase is two codebases, acquired fourteen months apart, still being stitched into one product on a timeline Elastic has not yet disclosed.
Deductive's Own Customers Signed a Different Vendor Than the One They Have Now
DoorDash and Foursquare picked a company built around one problem: investigating why production broke. Elastic's own post says existing Deductive customers will keep receiving support while integration plans take shape (Azarmi, 2026). That commitment covers continuity, and leaves the question of priority for later.
A feature competes for attention differently than a company does. Investigation now competes for engineering hours against Elastic's search and security product lines too, areas Deductive never had to share attention with as an independent company.
The integration timeline for Deductive's knowledge graph into Elastic Observability has not been published anywhere, including in Elastic's own announcement. Existing Deductive customers keep support during the transition, but incident investigation is now one priority competing against several others inside a larger platform.
Ask Elastic for a published integration date for Deductive's knowledge graph into Elastic Observability before your next renewal conversation, not after. Fourteen months between two acquisitions with no public roadmap yet is the one number in this announcement that decides whether you are buying a finished AI SRE or a multi-year integration project with your own production incidents as the test case.
