LRF Samköp's tech stack
What does LRF Samköp use?
LRF Samköp (lrfsamkop.se) uses at least 12 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and SendGrid for email delivery. Last checked .
- Based in
- Sweden
- Tools found
- 12
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
LRF Samköp'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
Hosting & Cloud
Application
1 tool, 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
Marketing
Ads & Pixels
Company Ops
6 tools, what the team runs on day to day
Email Delivery
Workspace
Collaboration
Security & Compliance
LRF Samköp tech stack FAQ
What tools does LRF Samköp use?
We've found 12 tools at LRF Samköp (lrfsamkop.se). Edge & Hosting: Microsoft Azure. Application: Next.js. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Microsoft 365, SendGrid and Apple Business. Last checked October 4, 2026.
What cloud does LRF Samköp run on?
LRF Samköp uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain.
What email provider does LRF Samköp use?
LRF Samköp uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records and DNS verification records.
What analytics tools does LRF Samköp use?
LRF Samköp uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does LRF Samköp use Microsoft 365?
Yes. We found Microsoft 365 at LRF Samköp through email records and DNS verification records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what LRF Samköp uses?
We read public traces only: LRF Samköp'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.