Cloudera's tech stack
What does Cloudera use?
Cloudera (hortonworks.com) uses at least 16 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Segment for analytics and Fastly for content delivery. Last checked .
- Industry
- Software
- Based in
- United States
- Founded
- 2011
- Company page
- Tools found
- 16
- Categories
- 14
- Layers
- 5 of 5
- Last checked
- Oct 2026
Cloudera'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
Application
2 tools, what the product is built with
Search
Media & UI
Data & Observability
2 tools, what they measure and store
Analytics
Data Pipeline
Go-to-market
2 tools, how they find and keep customers
Marketing
Ads & Pixels
Company Ops
7 tools, what the team runs on day to day
Email Delivery
Dev Tools
Security & Compliance
Cloudera tech stack FAQ
What tools does Cloudera use?
We've found 16 tools at Cloudera (hortonworks.com). Edge & Hosting: Amazon Web Services, Fastly and NS1. Application: Brightcove and Coveo. Data & Observability: Adobe Experience Platform Tags and Segment. Go-to-market: Meta Pixel. Company Ops: Microsoft 365, Google Workspace and Atlassian. Last checked October 3, 2026.
What cloud does Cloudera run on?
Cloudera uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.
What email provider does Cloudera use?
Cloudera uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.
What analytics tools does Cloudera use?
Cloudera uses Segment for analytics. We found Segment through website code.
Does Cloudera use Microsoft 365?
Yes. We found Microsoft 365 at Cloudera through DNS verification records. Microsoft 365 is used by 333,179 companies we track.
How does runsonwhat know what Cloudera uses?
We read public traces only: Cloudera'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.