Elastic is scheduled to report second-quarter fiscal 2027 results Nov. 19, 2026, providing a new checkpoint on the enterprise software supplier’s business. Its Nov. 5 notice says results for the period ended Oct. 31 will arrive after the U.S. market closes, followed by a conference call at 5 p.m. Eastern time. Readers can follow the call on the investor-relations site; Elastic plans to keep the recording online for two months.

Preview: The prior-quarter comparison

Elastic’s Aug. 27 results describe an earlier period, not the quarter being reported tomorrow. For the three months ended July 31, the company reported revenue of $478 million, including $449 million from subscriptions. It also reported more than 1,800 customers with annual contract value above $100,000. That cohort is a measure of committed customer spending, not a count of every organization using its software. The forthcoming report will supply a newer operating snapshot; the earlier figures alone cannot establish what happened in the October quarter.

How deployment becomes a commercial model

The company’s Form 10-K for the year ended April 30, 2026 describes both cloud services and software that customers manage themselves. Search and AI, observability and security sit on the same Elasticsearch platform. The distinction matters for enterprise buyers choosing where their data and workloads run: cloud delivery and self-managed deployment are different operating arrangements, even when they share underlying software.

Contracts generally cover one to three years, Elastic says; customers normally receive their annual bill before the relevant service period. Most Elastic Cloud subscriptions are based on consumption. The filing also describes month-to-month cloud subscriptions without a commitment, billed after usage. Those terms explain why contract duration, billing timing and actual resource use are separate parts of the model. Consulting and training also generate revenue.

Agent features and the implementation boundary

Elastic’s current Agent Builder documentation offers a product-level example of the implementation work behind an AI proposition. It describes agents that use natural-language requests to query Elasticsearch data or take actions through assigned tools. Teams can configure their own agents and tools through a user interface or programming interfaces, and connect external tools and clients.

Access depends on an appropriate subscription or serverless project tier. The documentation also identifies security roles and API keys as controls for agent use, available tools and queryable data. These are documented capabilities and prerequisites, not independent proof of answer accuracy, customer adoption or a newly announced November launch. For enterprise operators, the distinction is practical: a feature description does not itself specify an organization’s permissions or deployment choices.