Chicago Health Executives Forum's tech stack
What does Chicago Health Executives Forum use?
Chicago Health Executives Forum (chefchicago.org) uses at least 8 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Cloudflare for content delivery and GlobalSign for security. Last checked .
- Industry
- Healthcare
- Size
- 1,001–5,000 employees
- Based in
- Chicago, United States
- Founded
- 1976
- Company page
- Tools found
- 8
- Categories
- 6
- Layers
- 3 of 5
- Last checked
- Oct 2026
Chicago Health Executives Forum'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
CDN & Edge
Application
4 tools, what the product is built with
Frontend
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Chicago Health Executives Forum tech stack FAQ
What tools does Chicago Health Executives Forum use?
We've found 8 tools at Chicago Health Executives Forum (chefchicago.org). Edge & Hosting: Cloudflare and Amazon Web Services. Application: jQuery, Vimeo and YouTube. Company Ops: Microsoft 365 and GlobalSign. Last checked October 3, 2026.
What cloud does Chicago Health Executives Forum run on?
Chicago Health Executives Forum uses Amazon Web Services for hosting. We found Amazon Web Services through website code.
What email provider does Chicago Health Executives Forum use?
Chicago Health Executives Forum uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.
Does Chicago Health Executives Forum use Microsoft 365?
Yes. We found Microsoft 365 at Chicago Health Executives Forum through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Chicago Health Executives Forum uses?
We read public traces only: Chicago Health Executives Forum'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.