Stack Overflight's tech stack
What does Stack Overflight use?
Stack Overflight (stackoverflight.com) uses at least 8 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Vercel Analytics for analytics and Amazon CloudFront for content delivery. Last checked .
- Industry
- Airlines/aviation
- Size
- 11–50 employees
- Based in
- Barcelona, Spain
- Founded
- 2021
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
Stack Overflight'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
Frontend
Backend & Database
Data & Observability
1 tool, what they measure and store
Analytics
Company Ops
2 tools, what the team runs on day to day
Stack Overflight tech stack FAQ
What tools does Stack Overflight use?
We've found 8 tools at Stack Overflight (stackoverflight.com). Edge & Hosting: Amazon CloudFront, Vercel and Namecheap. Application: Next.js and Firebase. Data & Observability: Vercel Analytics. Company Ops: Microsoft 365 and Google Workspace. Last checked October 6, 2026.
What cloud does Stack Overflight run on?
Stack Overflight uses Vercel for hosting. We found Vercel through custom domain, DNS verification records and website code.
What email provider does Stack Overflight use?
Stack Overflight uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through email records.
What analytics tools does Stack Overflight use?
Stack Overflight uses Vercel Analytics for analytics. We found Vercel Analytics through website code.
Does Stack Overflight use Microsoft 365?
Yes. We found Microsoft 365 at Stack Overflight through email records. Microsoft 365 is used by 685,733 companies we track.
How does runsonwhat know what Stack Overflight uses?
We read public traces only: Stack Overflight'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.