runsonwhat

Sandvik AB's tech stack

What does Sandvik AB use?

Sandvik AB (home.sandvik) uses at least 8 tools we can see from public records, including Cloudflare for content delivery, SendGrid for email delivery and OneTrust for security. Last checked .

“Sandvik is a global, industrial technology group providing solutions that enhance productivity, profitability and sustainability for the mining, manufacturing, and infrastructure industries. We focus on improving our customers’ productivity and are at the forefront of digitalization. Our world-leadi”

Industry
Iron and Steel
Size
10,000+ employees
Based in
Stockholm, Sweden
Founded
1862
LinkedIn
Company page
Re-check liveVisit home.sandvik
Tools found
8
Categories
7
Layers
5 of 5
Last checked
Oct 2026

Sandvik AB'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

CDN & Edge

Application

1 tool, what the product is built with

AI

Data & Observability

1 tool, what they measure and store

Flags & Experiments

Go-to-market

2 tools, how they find and keep customers

Marketing

Ads & Pixels

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Companies like Sandvik AB also use

Tools common among companies with a similar stack that we haven't found at Sandvik AB.

Companies with a stack like Sandvik AB's

Ranked by shared tools, with rare tools counting more.

Sandvik AB tech stack FAQ

What tools does Sandvik AB use?

We've found 8 tools at Sandvik AB (home.sandvik). Edge & Hosting: Cloudflare. Data & Observability: Optimizely. Go-to-market: Meta Pixel. Company Ops: SendGrid, OneTrust and SwissSign. Last checked October 3, 2026.

Does Sandvik AB use Cloudflare?

Yes. We found Cloudflare at Sandvik AB through website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Sandvik AB uses?

We read public traces only: Sandvik AB'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.