Yettel Bank's tech stack
What does Yettel Bank use?
Yettel Bank (yettelbank.rs) uses at least 18 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Cookiebot for security. Last checked .
- Industry
- Financial Services
- Size
- 1–10 employees
- Based in
- Belgrade, Serbia
- Founded
- 2014
- Company page
- Tools found
- 18
- Categories
- 10
- Layers
- 4 of 5
- Last checked
- Oct 2026
Yettel Bank'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.
Application
4 tools, what the product is built with
Data & Observability
3 tools, what they measure and store
Go-to-market
8 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Yettel Bank tech stack FAQ
What tools does Yettel Bank use?
We've found 18 tools at Yettel Bank (yettelbank.rs). Application: jQuery, GSAP and Google Maps. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Microsoft 365, Atlassian and Cookiebot. Last checked October 3, 2026.
What email provider does Yettel Bank use?
Yettel Bank uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
What analytics tools does Yettel Bank use?
Yettel Bank uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
What CMS does Yettel Bank use?
Yettel Bank uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Yettel Bank use Microsoft 365?
Yes. We found Microsoft 365 at Yettel Bank through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Yettel Bank uses?
We read public traces only: Yettel Bank'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.