Żabka Group's tech stack
What does Żabka Group use?
Żabka Group (zabkagroup.com) uses at least 12 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
- Retail
- Size
- 10,000+ employees
- Based in
- Poznań, Poland
- Founded
- 1998
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Żabka Group'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
Data & Observability
2 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
3 tools, what the team runs on day to day
Workspace
Security & Compliance
Żabka Group tech stack FAQ
What tools does Żabka Group use?
We've found 12 tools at Żabka Group (zabkagroup.com). Edge & Hosting: Cloudflare. Application: OpenAI. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Microsoft 365, KnowBe4 and CERT Polska. Last checked October 3, 2026.
What email provider does Żabka Group use?
Żabka Group uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Żabka Group use?
Żabka Group uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Żabka Group use?
Żabka Group uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Żabka Group use Microsoft 365?
Yes. We found Microsoft 365 at Żabka Group through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Żabka Group uses?
We read public traces only: Żabka Group'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.