OpenUI's tech stack
What does OpenUI use?
OpenUI (openui.com) uses at least 14 tools we can see from public records, including Amazon Web Services for hosting, Reo.dev for sales, Discord for customer support and Google Analytics for analytics. Last checked .
- Company page
- Tools found
- 14
- Categories
- 10
- Layers
- 4 of 5
- Last checked
- Oct 2026
OpenUI'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
Hosting & Cloud
Application
5 tools, what the product is built with
Data & Observability
3 tools, what they measure and store
Monitoring
Go-to-market
3 tools, how they find and keep customers
Companies like OpenUI also use
Tools common among companies with a similar stack that we haven't found at OpenUI.
Companies with a stack like OpenUI's
Ranked by shared tools, with rare tools counting more.
OpenUI tech stack FAQ
What tools does OpenUI use?
We've found 14 tools at OpenUI (openui.com). Edge & Hosting: Amazon Web Services, Amazon Route 53 and Vercel. Application: Google Fonts, React and Tailwind CSS. Data & Observability: Google Analytics, web-vitals and PostHog. Go-to-market: Discord and Reo.dev. Last checked October 2, 2026.
What cloud does OpenUI run on?
OpenUI uses Amazon Web Services and Vercel for hosting. We found Amazon Web Services through website code.
What CRM does OpenUI use?
OpenUI uses Reo.dev for sales and CRM. We found Reo.dev through website code.
What does OpenUI use for customer support?
OpenUI uses Discord for customer support. We found Discord through website code.
What analytics tools does OpenUI use?
OpenUI uses Google Analytics and PostHog for analytics. We found Google Analytics through website code.
Does OpenUI use Google Analytics?
Yes. We found Google Analytics at OpenUI through website code. Google Analytics is used by 359,957 companies we track.
How does runsonwhat know what OpenUI uses?
We read public traces only: OpenUI'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.