PostgresGUI's tech stack
What does PostgresGUI use?
PostgresGUI (postgresgui.com) uses at least 10 tools we can see from public records, including Amazon Web Services for hosting, Google Analytics for analytics and Amazon CloudFront for content delivery. Last checked .
- Tools found
- 10
- Categories
- 7
- Layers
- 4 of 5
- Last checked
- Oct 2026
PostgresGUI'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
Data & Observability
2 tools, what they measure and store
Go-to-market
1 tool, how they find and keep customers
Marketing
PostgresGUI tech stack FAQ
What tools does PostgresGUI use?
As of October 2026, runsonwhat has found 10 tools at PostgresGUI (postgresgui.com) in public records. Edge & Hosting: Amazon Web Services, Amazon Route 53 and Amazon CloudFront. Application: React, Tailwind CSS and Next.js. Data & Observability: Google Analytics and Google Tag Manager. Last checked October 9, 2026.
What cloud does PostgresGUI run on?
PostgresGUI uses Amazon Web Services for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Amazon Web Services through Amazon Web Services code on postgresgui.com. Amazon Web Services is used by 144,668 companies runsonwhat tracks.
What analytics tools does PostgresGUI use?
PostgresGUI uses Google Analytics for analytics, alongside Google Tag Manager, according to runsonwhat (October 2026). runsonwhat found Google Analytics through Google Analytics code on postgresgui.com. Google Analytics is used by 849,088 companies runsonwhat tracks.
Does PostgresGUI use React?
Yes. runsonwhat found React at PostgresGUI through React code on postgresgui.com. React is a Frontend tool used by 124,015 companies runsonwhat tracks.
How does runsonwhat know what PostgresGUI uses?
runsonwhat reads public records only. Of the 10 tools at PostgresGUI, 6 were found through code on postgresgui.com, 2 through DNS records, 1 through website configuration files and 1 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and postgresgui.com about 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.