Kieser's tech stack
What does Kieser use?
Kieser (kieser.com) uses at least 16 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Sentry for monitoring. Last checked .
- Size
- 1,001–5,000 employees
- Founded
- 1967
- Company page
- Tools found
- 16
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Kieser'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
2 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
1 tool, what the product is built with
Frontend
Data & Observability
5 tools, what they measure and store
Monitoring
Flags & Experiments
Go-to-market
4 tools, how they find and keep customers
Company Ops
4 tools, what the team runs on day to day
Kieser tech stack FAQ
What tools does Kieser use?
We've found 16 tools at Kieser (kieser.com). Edge & Hosting: Amazon Web Services and Amazon CloudFront. Application: Vue.js. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Google Ads, Meta Pixel and Microsoft Ads. Company Ops: Microsoft 365, Atlassian and Sophos. Last checked October 2, 2026.
What cloud does Kieser run on?
Kieser uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does Kieser use?
Kieser uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.
What analytics tools does Kieser use?
Kieser uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.
Does Kieser use Microsoft 365?
Yes. We found Microsoft 365 at Kieser through DNS verification records, email records and website code. Microsoft 365 is used by 424,408 companies we track.
How does runsonwhat know what Kieser uses?
We read public traces only: Kieser'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.