Highrises.com's tech stack
What does Highrises.com use?
Highrises.com (highrises.com) uses at least 25 tools we can see from public records, including Google Workspace for email and documents, AppsFlyer for analytics, New Relic for monitoring and Amazon CloudFront for content delivery. Last checked .
- Based in
- United States
- Founded
- 2005
- Tools found
- 25
- Categories
- 12
- Layers
- 5 of 5
- Last checked
- Oct 2026
Highrises.com'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
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
4 tools, what they measure and store
Monitoring
Analytics
Data Pipeline
Go-to-market
11 tools, how they find and keep customers
Company Ops
5 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
Highrises.com tech stack FAQ
What tools does Highrises.com use?
We've found 25 tools at Highrises.com (highrises.com). Edge & Hosting: Amazon Route 53 and Amazon CloudFront. Application: Google Fonts, Next.js and Adobe Fonts. Data & Observability: New Relic, Adobe Experience Platform Tags and AppsFlyer. Go-to-market: Google Ad Manager, Criteo and Microsoft Xandr. Company Ops: Google Workspace, SendGrid and Proofpoint. Last checked October 4, 2026.
What email provider does Highrises.com use?
Highrises.com uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Highrises.com use?
Highrises.com uses AppsFlyer and Amplitude for analytics. We found AppsFlyer through website code.
Does Highrises.com use Google Workspace?
Yes. We found Google Workspace at Highrises.com through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Highrises.com uses?
We read public traces only: Highrises.com'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.