Kagge's tech stack
What does Kagge use?
Kagge (kagge.no) uses at least 13 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Klaviyo for marketing. Last checked .
- Industry
- Publishing
- Size
- 11–50 employees
- Based in
- Norway
- Founded
- 1996
- Tools found
- 13
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Kagge'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
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
Kagge tech stack FAQ
What tools does Kagge use?
We've found 13 tools at Kagge (kagge.no). Edge & Hosting: Amazon Route 53. Application: jQuery and Adobe Fonts. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, WordPress and Yoast SEO. Company Ops: Microsoft 365, SendGrid and Cookiebot. Last checked October 3, 2026.
What email provider does Kagge use?
Kagge uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Kagge use?
Kagge uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Kagge use?
Kagge uses WordPress and Yoast SEO for its website. We found WordPress through website code.
What marketing software does Kagge use?
Kagge uses Klaviyo for marketing. We found Klaviyo through website code.
Does Kagge use Microsoft 365?
Yes. We found Microsoft 365 at Kagge through email records. Microsoft 365 is used by 268,236 companies we track.
How does runsonwhat know what Kagge uses?
We read public traces only: Kagge'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.