Fate's tech stack
What does Fate use?
Fate (fate.com.ar) uses at least 8 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Metricool for marketing and Trend Micro for security. Last checked .
- Industry
- Manufacture of Rubber Tyres and Tubes; Retreading and Rebuilding of Rubber Tyres
- Size
- 1,001–5,000 employees
- Based in
- San Fernando, Argentina
- Founded
- 1940
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
Fate'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
Application
1 tool, what the product is built with
Frontend
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 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
Fate tech stack FAQ
What tools does Fate use?
We've found 8 tools at Fate (fate.com.ar). Edge & Hosting: Amazon Route 53. Application: jQuery. Data & Observability: Google Analytics. Go-to-market: Meta Pixel, Google Ads and Metricool. Company Ops: Microsoft 365 and Trend Micro. Last checked October 3, 2026.
What email provider does Fate use?
Fate uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Fate use?
Fate uses Google Analytics for analytics. We found Google Analytics through website code.
What marketing software does Fate use?
Fate uses Metricool for marketing. We found Metricool through website code.
Does Fate use Microsoft 365?
Yes. We found Microsoft 365 at Fate through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Fate uses?
We read public traces only: Fate'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.