RetroShift's tech stack
What does RetroShift use?
RetroShift (retroshift.dev) uses at least 12 tools we can see from public records, including Google Workspace for email and documents, Cal.com for sales, Discord for customer support and Google Analytics for analytics. Last checked .
- Tools found
- 12
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
RetroShift'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
CDN & Edge
DNS
Application
2 tools, what the product is built with
Backend & Database
Media & UI
Data & Observability
2 tools, what they measure and store
Monitoring
Analytics
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Workspace
RetroShift tech stack FAQ
What tools does RetroShift use?
We've found 12 tools at RetroShift (retroshift.dev). Edge & Hosting: Cloudflare, Amazon CloudFront and Namecheap. Application: Google Fonts and Supabase. Data & Observability: Google Analytics and web-vitals. Go-to-market: Discord and Cal.com. Company Ops: Google Workspace and Resend. Last checked October 2, 2026.
What CRM does RetroShift use?
RetroShift uses Cal.com for sales and CRM. We found Cal.com through website code.
What email provider does RetroShift use?
RetroShift uses Google Workspace for email and documents. We found Google Workspace through email records.
What does RetroShift use for customer support?
RetroShift uses Discord for customer support. We found Discord through website code.
What analytics tools does RetroShift use?
RetroShift uses Google Analytics for analytics. We found Google Analytics through website code.
Does RetroShift use Cloudflare?
Yes. We found Cloudflare at RetroShift through website code. Cloudflare is used by 564,981 companies we track.
How does runsonwhat know what RetroShift uses?
We read public traces only: RetroShift'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.