Ipiranga's tech stack
What does Ipiranga use?
Ipiranga (portal.ipiranga) uses at least 16 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Akamai mPulse for monitoring and Akamai for content delivery. Last checked .
- Industry
- Retail
- Size
- 10,000+ employees
- Based in
- Rio De Janeiro, Brazil
- Founded
- 1938
- Company page
- Tools found
- 16
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Ipiranga'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
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
6 tools, how they find and keep customers
Company Ops
3 tools, what the team runs on day to day
Workspace
Security & Compliance
Ipiranga tech stack FAQ
What tools does Ipiranga use?
We've found 16 tools at Ipiranga (portal.ipiranga). Edge & Hosting: Akamai. Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics, Google Tag Manager and Akamai mPulse. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365, reCAPTCHA and OneTrust. Last checked October 3, 2026.
What email provider does Ipiranga use?
Ipiranga uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Ipiranga use?
Ipiranga uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
Does Ipiranga use Microsoft 365?
Yes. We found Microsoft 365 at Ipiranga through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Ipiranga uses?
We read public traces only: Ipiranga'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.