Elastic reports 46% of $1.74bn FY2026 revenue from outside the United States and discloses nothing finer. This scores 30 EMEA markets on opportunity Elastic can actually sell into, then sets that against where Elastic is currently staffed.
Breadth is not the problem, depth is. Elastic reaches more EMEA countries than most of its peers. But it staffs each one more thinly, and its international hiring skews to engineering (55%) rather than field (36%), where the peer median is the other way round.
The Netherlands is the sharpest single case. Highest hosted-database adoption in Europe at 78% of large enterprises, roughly 2,155 addressable firms, and one Elastic field role. Five of nine peers are present with 25 roles between them, Datadog alone carrying fifteen.
Italy is uncovered outright, about 2,343 addressable enterprises and zero Elastic field roles against twelve across three peers. Germany is the largest opportunity but already contested, and its hosted-database adoption is only 30%, near the bottom of western Europe and below the 30-market median of 40%, so it is an early market rather than a ripe one.
The order above depends on how four factors are weighted, and reasonable people weight them differently. So the weights are movable rather than asserted, and the ranking recalculates as you move them.
This treats Elastic's own open field roles as the measure of coverage. Elastic's FY2026 10-K says that is incomplete, in its own words: partners extend its reach "in geographic areas and verticals where we do not have a formal sales presence", and users can adopt Elastic Cloud through a free trial or a cloud marketplace "without any sales interaction".
So a market with zero Elastic field roles is not necessarily uncovered. It may be deliberately partner-led or self-serve. One channel partner alone accounted for 11% of total revenue in FY2026. Read the gaps below as where Elastic places its own field capacity, which is a real signal, and not as proof that demand is being missed.
Second, a field role in Barcelona or Dublin may cover many markets rather than the one it sits in. That inflates coverage for hub countries and understates it everywhere else. The Limits page lists the rest.
The role that owns Elastic International exists to answer one question in different clothes: where does the next unit of investment go, and how do you defend that to an executive?
Elastic discloses that customers outside the United States are 46% of $1.74bn in FY2026 revenue. That is the entire public geographic disclosure. No country split, no per-market growth, no coverage map. Internally the team has all of it; from outside there is nothing.
So the interesting question is whether the decision can be reconstructed anyway. Two public sources make it nearly possible:
Adoption of the specific services Elastic sells is measured. Eurostat surveys European enterprises on cloud usage and splits the answers by service type, one of which is hosted database services. That is close to a direct proxy for the Elasticsearch buying motion, reported country by country and by company size.
Field investment is advertised. A strategy deck is a claim, but an open requisition is a budget somebody already approved. Every company publishes them.
Put the two together and you get where demand is, against where capacity is going. That is not the whole job, but it is the shape of it.
A generic market-attractiveness scorecard would be worthless, because it is not derived from anything. Elastic earns in a particular way, and that dictates what makes a market valuable. Every factor below traces to a line in the business model.
| How Elastic earns | What that implies | Measured by |
|---|---|---|
| Elasticsearch is adopted bottom-up by developers, then converted | Landing needs developer and ICT depth, not GDP | Large ICT-sector enterprises |
| Elastic Cloud is consumption-priced and grew 22% in FY2026 | Value follows enterprise cloud maturity | Hosted database and dev-platform adoption |
| Net expansion around 112%, and 1,720 customers sit above $100k ACV | The ceiling is the count of firms large enough to scale consumption, not logo count | Enterprises with 250+ employees |
| Elastic Security is a separate solution with its own buyers | Security demand can point somewhere different from search demand | Security-as-a-service adoption |
| Field coverage is expensive and country-specific | Return depends on presence already in market | Elastic's open field roles per country |
The useful accident is that Eurostat splits cloud adoption by service type. One of those types is hosted database services, the closest public proxy that exists for what Elasticsearch is bought to do. It carries the most weight.
Worked example, the Netherlands. 2,773 enterprises with 250 or more employees, of which 77.7% buy hosted database services, giving 2,155 addressable. With 147 large ICT enterprises, 59% dev-platform adoption and 79% security adoption, the balanced weighting scores it 82.6, third in EMEA. Spreading Elastic's 21 EMEA field roles by opportunity would put 1.1 there. Elastic posts 1. Nine peers post 25 between them.
The ranking is a function of a strategic prior, so the weights are yours to move rather than mine to assert. Drag a slider or pick a preset and the order recalculates.
Worth trying: Security led. Germany falls from first to ninth and the Netherlands takes the top spot. Germany's advantage is size, 4,482 addressable enterprises against the Netherlands' 2,155, but its security-as-a-service adoption is 51%, ranking nineteenth of thirty and below the median of 58%. The Netherlands ranks first at 79%. Weight security heavily and size stops carrying Germany. Which product Elastic leads with changes where it should lead with it.
| Market | Opportunity | Addressable | Hosted DB | Elastic | Peers | vs expected | State |
|---|
Addressable is large enterprises multiplied by the share already buying hosted database services. vs expected spreads Elastic's field roles in proportion to opportunity, then compares. Spain reads over-covered because Barcelona is a regional hub, not because Spain is over-served.
One company is an anecdote. These are the nine direct and adjacent competitors with a readable public board, grouped by which Elastic solution they compete with.
| Company | Reqs | Intl % | Field % | Intl eng | Intl field | EMEA field | Countries |
|---|
Splunk, Dynatrace, CrowdStrike, Chronosphere and Coveo have no readable public board. Splunk and Dynatrace are Elastic's closest observability rivals, so their absence is the biggest hole in this comparison and is stated rather than glossed.
The score is built only from Eurostat adoption and enterprise counts. It never looks at what any competitor does. So competitor field placement is an independent test of it.
That answers the obvious objection to any weighted model, which is why those weights. If nine firms independently allocate field capacity in nearly the same order this score produces, the weights are not arbitrary. It is an out-of-sample check, not a restatement.
How much of that is just market size? Most of it. A naive count of large enterprises, with no weighting and no adoption data at all, already predicts peer placement at 0.869. Addressable enterprises alone reaches 0.912. The full four-factor score reaches 0.958. So the model beats a size proxy, but modestly. The honest claim is that weighting adds something on top of size, not that the ranking would collapse without it. Anyone who suspected the correlation was mostly a big-country effect was largely right.
It also separates two situations the score alone cannot tell apart. A high-scoring market several peers already staff is validated demand, and being absent from it is a competitive gap. A high-scoring market nobody staffs is either genuinely overlooked or has a reason the score cannot see, and deserves a check before it becomes a plan.
| Market | Opportunity | Elastic | Peers in | Peer roles | Read |
|---|
Ireland shows five peers and 34 roles because Dublin is where Datadog and MongoDB put their EMEA hub. Read it as evidence about hub location, not Irish market demand.
Eurostat does not cover the UK, Switzerland, Israel or the Gulf, and the UK alone holds 10 of Elastic's 36 EMEA field roles. Those markets get a separate, cruder table.
| Market | GDP $bn | ICT exports | Elastic | Peers |
|---|
Only the field-presence columns are comparable to tier 1, because they come from the same method. GDP is a size proxy from the World Bank and says nothing about whether these firms buy hosted database services. Tier 1 uses no World Bank data at all. Israel is the row worth a second look: the highest ICT-export intensity in either tier at 64%, eight peer field roles, and none from Elastic.
The hub effect is the real weakness. Eight of Elastic's EMEA field roles sit in Barcelona and 34 of the peers' sit in Ireland. Both are regional hubs, so a role there may cover many markets. Coverage is overstated for hub countries and understated everywhere else.
A requisition is an intention, not a hire. Boards carry stale and evergreen postings, and a hiring plan is not coverage.
No country-level revenue exists publicly, so current performance is proxied by field presence and never measured. A market could be well served and quietly growing without a single open role.
Vintage varies. Cloud adoption is 2023 for most countries with 2024 where published, enterprise counts are 2023, World Bank figures are 2024.