Story House Egmont's tech stack
What does Story House Egmont use?
Story House Egmont (storyhouseegmont.no) uses at least 8 tools we can see from public records, including Google Analytics for analytics, Cloudflare for content delivery and Cookiebot for security. Last checked .
- Based in
- Norway
- Company page
- Tools found
- 8
- Categories
- 5
- Layers
- 5 of 5
- Last checked
- Oct 2026
Story House Egmont'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
1 tool, where the bytes are served from
CDN & Edge
Application
2 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Ads & Pixels
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
Companies like Story House Egmont also use
Tools common among companies with a similar stack that we haven't found at Story House Egmont.
Companies with a stack like Story House Egmont's
Ranked by shared tools, with rare tools counting more.
Story House Egmont tech stack FAQ
What tools does Story House Egmont use?
We've found 8 tools at Story House Egmont (storyhouseegmont.no). Edge & Hosting: Cloudflare. Application: Vue.js and Nuxt. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel and Google Ads. Company Ops: Cookiebot. Last checked October 3, 2026.
What analytics tools does Story House Egmont use?
Story House Egmont uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Story House Egmont use Cloudflare?
Yes. We found Cloudflare at Story House Egmont through DNS records. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Story House Egmont uses?
We read public traces only: Story House Egmont'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.