Rapid News Brief
Elastic said Nov. 19 it agreed to acquire HoneyHive, adding AI agent evaluation to its planned observability expansion as the software company reported another quarter of subscription growth.
Agreement, not a completed integration
Elastic intends to incorporate HoneyHive's technology into Elastic Observability and continue supporting existing customers. Its announcement did not disclose a purchase price or closing date.
The company said it would share a consolidated product roadmap in the coming months. The agreement is not an announcement that an integrated product is already available.
Data and permissions
HoneyHive's v2 product description separates a control plane for administration from data planes containing raw inputs, outputs and evaluation workloads. The control plane handles items such as project structure, evaluator definitions, identity and audit records.
HoneyHive describes shared managed infrastructure, dedicated managed infrastructure, a hybrid arrangement and a fully self-hosted stack. In a hybrid deployment, a customer runs one or more data planes in its own environment while HoneyHive manages the control plane.
The product description also assigns permissions at organization, workspace and project levels. These are vendor-described controls, not independent security findings.
A subscription-led business
For its second quarter of fiscal 2027 ended Oct. 31, 2026, Elastic reported $496 million in revenue, up 17% from a year earlier. Subscription revenue was $465 million, also up 17%. GAAP operating income was $22 million, representing a 4.4% margin.
Elastic said more than 1,830 customers had annual contract values above $100,000, compared with more than 1,600 a year before. Its net expansion rate was approximately 111%. These are companywide measures, not HoneyHive's sales or the deal's value.
Cash, cash equivalents and marketable securities totaled $1.423 billion at Oct. 31, 2026. The release did not identify a purchase price for the HoneyHive agreement.
For enterprise IT teams, those distinctions matter when deciding where operational records and evaluation workloads should run and which administrators should have access.
