Applied Underwriters Invitational's tech stack
What does Applied Underwriters Invitational use?
Applied Underwriters Invitational (invitational.com) uses at least 5 tools we can see from public records, including Netlify for hosting and Builder.io for its website. Last checked .
“The Applied Underwriters Invitational is a premier golf charity event series supporting local charities across the United States.”
- Industry
- Insurance
- Size
- 1,001–5,000 employees
- Based in
- Omaha, United States
- Company page
- Tools found
- 5
- Categories
- 5
- Layers
- 3 of 5
- Last checked
- Oct 2026
Applied Underwriters Invitational'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
Hosting & Cloud
Application
2 tools, what the product is built with
Frontend
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Applied Underwriters Invitational tech stack FAQ
What tools does Applied Underwriters Invitational use?
We've found 5 tools at Applied Underwriters Invitational (invitational.com). Edge & Hosting: Netlify. Application: Next.js. Go-to-market: Builder.io. Last checked October 3, 2026.
What cloud does Applied Underwriters Invitational run on?
Applied Underwriters Invitational uses Netlify for hosting. We found Netlify through custom domain, DNS records and website code.
What CMS does Applied Underwriters Invitational use?
Applied Underwriters Invitational uses Builder.io for its website. We found Builder.io through website code.
Does Applied Underwriters Invitational use Next.js?
Yes. We found Next.js at Applied Underwriters Invitational through website code. Next.js is used by 12,739 companies we track.
How does runsonwhat know what Applied Underwriters Invitational uses?
We read public traces only: Applied Underwriters Invitational'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.