runsonwhat

HungryHorse's tech stack

What does HungryHorse use?

HungryHorse (hungryhorse.co.uk) uses at least 28 tools we can see from public records, including Microsoft Azure for hosting, Google Analytics for analytics, Branch for marketing and Datadog for monitoring. Last checked .

Industry
Pub
Based in
United Kingdom
Founded
1995
Tools found
28
Categories
11
Layers
5 of 5
Last checked
Oct 2026

HungryHorse's stack, layer by layer

Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

Edge & Hosting

3 tools, where the bytes are served from

Application

2 tools, what the product is built with

Data & Observability

6 tools, what they measure and store

Company Ops

4 tools, what the team runs on day to day

HungryHorse tech stack FAQ

What tools does HungryHorse use?

We've found 28 tools at HungryHorse (hungryhorse.co.uk). Edge & Hosting: Amazon Route 53, Microsoft Azure and Akamai. Application: Font Awesome and Woosmap. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Mimecast, Cookiebot and SparkPost. Last checked October 3, 2026.

What cloud does HungryHorse run on?

HungryHorse uses Microsoft Azure for hosting. We found Microsoft Azure through website code.

What analytics tools does HungryHorse use?

HungryHorse uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

What marketing software does HungryHorse use?

HungryHorse uses Branch for marketing. We found Branch through website code.

Does HungryHorse use Google Analytics?

Yes. We found Google Analytics at HungryHorse through website code. Google Analytics is used by 89,943 companies we track.

How does runsonwhat know what HungryHorse uses?

We read public traces only: HungryHorse's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.

We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.