Workers at Work's tech stack
What does Workers at Work use?
Workers at Work (workersatwork.com) uses at least 8 tools we can see from public records, including Microsoft Azure for hosting, Google Workspace for email and documents, Google Analytics for analytics and SendGrid for email delivery. Last checked .
- Industry
- Staffing and Recruiting
- Size
- 51–200 employees
- Based in
- Marseille, France
- Founded
- 2022
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Workers at Work'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
DNS
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
2 tools, what the team runs on day to day
Email Delivery
Workspace
Workers at Work tech stack FAQ
What tools does Workers at Work use?
We've found 8 tools at Workers at Work (workersatwork.com). Edge & Hosting: Microsoft Azure and Gandi. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Google Ads. Company Ops: Google Workspace and SendGrid. Last checked October 6, 2026.
What cloud does Workers at Work run on?
Workers at Work uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain.
What email provider does Workers at Work use?
Workers at Work uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Workers at Work use?
Workers at Work uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Workers at Work use Google Analytics?
Yes. We found Google Analytics at Workers at Work through website code. Google Analytics is used by 543,414 companies we track.
How does runsonwhat know what Workers at Work uses?
We read public traces only: Workers at Work'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.