Marathon Fusion's tech stack
What does Marathon Fusion use?
Marathon Fusion (marathonfusion.com) uses at least 10 tools we can see from public records, including Google Cloud for hosting, Microsoft 365 for email and documents, Vercel Analytics for analytics and Valimail for security. Last checked .
- Industry
- Mechanical or Industrial Engineering
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Founded
- 2023
- Company page
- Tools found
- 10
- Categories
- 5
- Layers
- 4 of 5
- Last checked
- Oct 2026
Marathon Fusion'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
3 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Company Ops
4 tools, what the team runs on day to day
Security & Compliance
Marathon Fusion tech stack FAQ
What tools does Marathon Fusion use?
We've found 10 tools at Marathon Fusion (marathonfusion.com). Edge & Hosting: Google Cloud and Vercel. Application: React, Tailwind CSS and Next.js. Data & Observability: Vercel Analytics. Company Ops: Microsoft 365, Google Workspace and Valimail. Last checked October 4, 2026.
What cloud does Marathon Fusion run on?
Marathon Fusion uses Google Cloud and Vercel for hosting. We found Google Cloud through DNS records.
What email provider does Marathon Fusion use?
Marathon Fusion uses Microsoft 365, Google Workspace and iCloud Mail for email and documents. We found Microsoft 365 through email records.
What analytics tools does Marathon Fusion use?
Marathon Fusion uses Vercel Analytics for analytics. We found Vercel Analytics through website code.
Does Marathon Fusion use Microsoft 365?
Yes. We found Microsoft 365 at Marathon Fusion through email records. Microsoft 365 is used by 327,005 companies we track.
How does runsonwhat know what Marathon Fusion uses?
We read public traces only: Marathon Fusion'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.