runsonwhat

SDI Застрахователен брокер's tech stack

What does SDI Застрахователен брокер use?

SDI Застрахователен брокер (sdi.bg) uses at least 13 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics and Let's Encrypt for security. Last checked .

Industry
Insurance
Size
201–1,000 employees
Based in
Bulgaria
Founded
2004
LinkedIn
Company page
Tools found
13
Categories
5
Layers
4 of 5
Last checked
Oct 2026

SDI Застрахователен брокер'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

4 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Security & Compliance

SDI Застрахователен брокер tech stack FAQ

What tools does SDI Застрахователен брокер use?

We've found 13 tools at SDI Застрахователен брокер (sdi.bg). Application: Google Fonts, Vimeo and YouTube. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel and Google Ads. Company Ops: Microsoft 365, Let's Encrypt and Sectigo. Last checked October 3, 2026.

What email provider does SDI Застрахователен брокер use?

SDI Застрахователен брокер uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does SDI Застрахователен брокер use?

SDI Застрахователен брокер uses Google Analytics, Google Tag Manager and Hotjar for analytics, among 4 tools in this category. We found Google Analytics through website code.

Does SDI Застрахователен брокер use Microsoft 365?

Yes. We found Microsoft 365 at SDI Застрахователен брокер through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what SDI Застрахователен брокер uses?

We read public traces only: SDI Застрахователен брокер'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.