Slalom Build's tech stack
What does Slalom Build use?
Slalom Build (slalombuild.com) uses at least 16 tools we can see from public records, including Amazon Web Services for hosting, Google Analytics for analytics, Avature for hiring and HR and Cloudflare for content delivery. Last checked .
- Based in
- Seattle, United States
- Company page
- Tools found
- 16
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Slalom Build'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
3 tools, where the bytes are served from
Application
2 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
People & HR
Security & Compliance
Slalom Build tech stack FAQ
What tools does Slalom Build use?
We've found 16 tools at Slalom Build (slalombuild.com). Edge & Hosting: Cloudflare, Amazon Web Services and Amazon Route 53. Application: Vimeo and Tailwind CSS. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Google Ads, Meta Pixel and LinkedIn Insight Tag. Company Ops: Proofpoint, OneTrust and Avature. Last checked October 3, 2026.
What cloud does Slalom Build run on?
Slalom Build uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What analytics tools does Slalom Build use?
Slalom Build uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.
What does Slalom Build use for hiring and HR?
Slalom Build uses Avature for hiring and HR. We found Avature through custom domain.
Does Slalom Build use Cloudflare?
Yes. We found Cloudflare at Slalom Build through website code. Cloudflare is used by 349,130 companies we track.
How does runsonwhat know what Slalom Build uses?
We read public traces only: Slalom Build'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.