Zanders's tech stack
What does Zanders use?
Zanders (zanders.com) uses at least 17 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
- Industry
- Paper & Forest Products
- Size
- 1–10 employees
- Based in
- Bergisch Gladbach, Germany
- Founded
- 1829
- Company page
- Tools found
- 17
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Zanders'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
2 tools, what the product is built with
Media & UI
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Ads & Pixels
Company Ops
8 tools, what the team runs on day to day
Workspace
Dev Tools
Zanders tech stack FAQ
What tools does Zanders use?
We've found 17 tools at Zanders (zanders.com). Edge & Hosting: Cloudflare. Application: Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: Microsoft 365, reCAPTCHA and Atlassian. Last checked October 4, 2026.
What email provider does Zanders use?
Zanders uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Zanders use?
Zanders uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Zanders use?
Zanders uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Zanders use Microsoft 365?
Yes. We found Microsoft 365 at Zanders through DNS verification records and email records. Microsoft 365 is used by 685,700 companies we track.
How does runsonwhat know what Zanders uses?
We read public traces only: Zanders'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.