kierunek.ai's tech stack
What does kierunek.ai use?
kierunek.ai (kierunek.ai) uses at least 23 tools we can see from public records, including Amazon Web Services for hosting, Google Analytics for analytics, ClickFunnels for its website and web-vitals for monitoring. Last checked .
- Based in
- Poland
- Tools found
- 23
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
kierunek.ai'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
Hosting & Cloud
CDN & Edge
Application
4 tools, what the product is built with
Data & Observability
6 tools, what they measure and store
Go-to-market
9 tools, how they find and keep customers
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
kierunek.ai tech stack FAQ
What tools does kierunek.ai use?
We've found 23 tools at kierunek.ai (kierunek.ai). Edge & Hosting: Cloudflare, Amazon Web Services and OVHcloud. Application: YouTube, React and Tailwind CSS. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Google Ads, Meta Pixel and Microsoft Ads. Company Ops: Cookiebot. Last checked October 4, 2026.
What cloud does kierunek.ai run on?
kierunek.ai uses Amazon Web Services and OVHcloud for hosting. We found Amazon Web Services through website code.
What analytics tools does kierunek.ai use?
kierunek.ai uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics, among 5 tools in this category. We found Google Analytics through website code.
What CMS does kierunek.ai use?
kierunek.ai uses ClickFunnels for its website. We found ClickFunnels through DNS verification records.
Does kierunek.ai use Cloudflare?
Yes. We found Cloudflare at kierunek.ai through website code. Cloudflare is used by 304,276 companies we track.
How does runsonwhat know what kierunek.ai uses?
We read public traces only: kierunek.ai'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.