SBB's tech stack
What does SBB use?
SBB (sbb.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 Cloudflare for content delivery. Last checked .
- Industry
- Telecommunications
- Based in
- Serbia
- Founded
- 2000
- Company page
- Tools found
- 18
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
SBB'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
4 tools, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
SBB tech stack FAQ
What tools does SBB use?
We've found 18 tools at SBB (sbb.rs). Edge & Hosting: Cloudflare. Application: jQuery, Vimeo and YouTube. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Microsoft 365, SendGrid and reCAPTCHA. Last checked October 2, 2026.
What email provider does SBB use?
SBB uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does SBB use?
SBB uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
What CMS does SBB use?
SBB uses WordPress and Rank Math for its website. We found WordPress through website code.
Does SBB use Microsoft 365?
Yes. We found Microsoft 365 at SBB through email records. Microsoft 365 is used by 245,922 companies we track.
How does runsonwhat know what SBB uses?
We read public traces only: SBB'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.