Cbl Electronics's tech stack
What does Cbl Electronics use?
Cbl Electronics (cblelectronics.com) uses at least 12 tools we can see from public records, including OVHcloud for hosting, Microsoft 365 for email and documents, Matomo for analytics and iubenda for security. Last checked .
- Industry
- Defense & Space
- Size
- 51–200 employees
- Based in
- Pian Di San Martino, Italy
- Founded
- 2002
- Company page
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Cbl Electronics'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
2 tools, where the bytes are served from
Hosting & Cloud
Application
5 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Cbl Electronics tech stack FAQ
What tools does Cbl Electronics use?
We've found 12 tools at Cbl Electronics (cblelectronics.com). Edge & Hosting: OVHcloud and Aruba.it. Application: jQuery, Google Fonts and YouTube. Data & Observability: Matomo. Go-to-market: Microsoft Ads. Company Ops: Microsoft 365 and iubenda. Last checked October 8, 2026.
What cloud does Cbl Electronics run on?
Cbl Electronics uses OVHcloud and Aruba.it for hosting. We found OVHcloud through DNS records and website code.
What email provider does Cbl Electronics use?
Cbl Electronics uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does Cbl Electronics use?
Cbl Electronics uses Matomo for analytics. We found Matomo through website code.
Does Cbl Electronics use jQuery?
Yes. We found jQuery at Cbl Electronics through website code. jQuery is used by 761,022 companies we track.
How does runsonwhat know what Cbl Electronics uses?
We read public traces only: Cbl Electronics'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.