Breezing's tech stack
What does Breezing use?
Breezing (breezing.com) uses at least 13 tools we can see from public records, including Fly.io for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and WordPress for its website. Last checked .
- Based in
- United States
- Founded
- 2011
- Company page
- Tools found
- 13
- Categories
- 10
- Layers
- 5 of 5
- Last checked
- Oct 2026
Breezing'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
4 tools, 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
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Breezing tech stack FAQ
What tools does Breezing use?
We've found 13 tools at Breezing (breezing.com). Edge & Hosting: GoDaddy, Fastly and Fly.io. Application: jQuery, Google Fonts and Vimeo. Data & Observability: Google Analytics. Go-to-market: WordPress and Yoast SEO. Company Ops: Microsoft 365 and reCAPTCHA. Last checked October 3, 2026.
What cloud does Breezing run on?
Breezing uses Fly.io for hosting. We found Fly.io through website code.
What email provider does Breezing use?
Breezing uses Microsoft 365 for email and documents. We found Microsoft 365 through email records and website code.
What analytics tools does Breezing use?
Breezing uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does Breezing use?
Breezing uses WordPress and Yoast SEO for its website. We found WordPress through website code.
Does Breezing use Microsoft 365?
Yes. We found Microsoft 365 at Breezing through email records and website code. Microsoft 365 is used by 685,125 companies we track.
How does runsonwhat know what Breezing uses?
We read public traces only: Breezing'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.