Weframe's tech stack
What does Weframe use?
Weframe (weframe.com) uses at least 10 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Google Analytics for analytics and Cookiebot for security. Last checked .
- Industry
- IT Services
- Size
- 51–200 employees
- Based in
- München, Germany
- Founded
- 2016
- Company page
- Tools found
- 10
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Weframe'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
Application
1 tool, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
4 tools, what the team runs on day to day
Security & Compliance
Weframe tech stack FAQ
What tools does Weframe use?
We've found 10 tools at Weframe (weframe.com). Edge & Hosting: Amazon Web Services and Amazon Route 53. Application: GSAP. Data & Observability: Google Analytics. Go-to-market: Meta Pixel. Company Ops: Google Workspace, Apple Business and Cookiebot. Last checked October 6, 2026.
What cloud does Weframe run on?
Weframe uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.
What email provider does Weframe use?
Weframe uses Google Workspace and Apple Business for email and documents. We found Google Workspace through email records.
What analytics tools does Weframe use?
Weframe uses Google Analytics for analytics. We found Google Analytics through website code.
Does Weframe use Google Analytics?
Yes. We found Google Analytics at Weframe through website code. Google Analytics is used by 579,808 companies we track.
How does runsonwhat know what Weframe uses?
We read public traces only: Weframe'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.