Potraviny Žabka's tech stack
What does Potraviny Žabka use?
Potraviny Žabka (izabka.cz) uses at least 8 tools we can see from public records, including Oracle Cloud for hosting, Google Analytics for analytics, WordPress for its website and reCAPTCHA for security. Last checked .
- Industry
- Retail
- Size
- 11–50 employees
- Based in
- Czechia
- Founded
- 2016
- Company page
- Tools found
- 8
- Categories
- 5
- Layers
- 5 of 5
- Last checked
- Oct 2026
Potraviny Žabka'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
Hosting & Cloud
Application
1 tool, what the product is built with
Frontend
Data & Observability
2 tools, what they measure and store
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Company Ops
2 tools, what the team runs on day to day
Security & Compliance
Potraviny Žabka tech stack FAQ
What tools does Potraviny Žabka use?
We've found 8 tools at Potraviny Žabka (izabka.cz). Edge & Hosting: Oracle Cloud. Application: jQuery. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress and Yoast SEO. Company Ops: reCAPTCHA and CookieYes. Last checked October 4, 2026.
What cloud does Potraviny Žabka run on?
Potraviny Žabka uses Oracle Cloud for hosting. We found Oracle Cloud through email records.
What analytics tools does Potraviny Žabka use?
Potraviny Žabka uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Potraviny Žabka use?
Potraviny Žabka uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Potraviny Žabka use Google Analytics?
Yes. We found Google Analytics at Potraviny Žabka through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Potraviny Žabka uses?
We read public traces only: Potraviny Žabka'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.