Framo's tech stack
What does Framo use?
Framo (framo.com) uses at least 21 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Umbraco for its website and Cloudflare for content delivery. Last checked .
- Industry
- Mechanical or Industrial Engineering
- Size
- 1,001–5,000 employees
- Based in
- Florvåg, Norway
- Founded
- 1938
- Company page
- Tools found
- 21
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Framo'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
CDN & Edge
DNS
Application
4 tools, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Company Ops
9 tools, what the team runs on day to day
Email Delivery
Workspace
Framo tech stack FAQ
What tools does Framo use?
We've found 21 tools at Framo (framo.com). Edge & Hosting: Cloudflare and CSC. Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads, Meta Pixel and TikTok Pixel. Company Ops: Microsoft 365, reCAPTCHA and SendGrid. Last checked October 7, 2026.
What email provider does Framo use?
Framo uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records, email records and website code.
What analytics tools does Framo use?
Framo uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Framo use?
Framo uses Umbraco for its website. We found Umbraco through website code.
Does Framo use jQuery?
Yes. We found jQuery at Framo through website code. jQuery is used by 762,082 companies we track.
How does runsonwhat know what Framo uses?
We read public traces only: Framo'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.