Reno's tech stack
What does Reno use?
Reno (reno.de) uses at least 12 tools we can see from public records, including Vercel for hosting, Google Analytics for analytics, Storyblok for its website and Klaviyo for marketing. Last checked .
- Industry
- Retail
- Founded
- 1977
- Tools found
- 12
- Categories
- 8
- Layers
- 5 of 5
- Last checked
- Oct 2026
Reno'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
1 tool, what the product is built with
Frontend
Data & Observability
3 tools, what they measure and store
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Reno tech stack FAQ
What tools does Reno use?
We've found 12 tools at Reno (reno.de). Edge & Hosting: Vercel. Application: Next.js. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and Klaviyo. Company Ops: SendGrid and Cookiebot. Last checked October 2, 2026.
What cloud does Reno run on?
Reno uses Vercel for hosting. We found Vercel through DNS verification records and DNS records.
What analytics tools does Reno use?
Reno uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.
What CMS does Reno use?
Reno uses Storyblok for its website. We found Storyblok through website code.
What marketing software does Reno use?
Reno uses Klaviyo for marketing. We found Klaviyo through DNS verification records and website code.
Does Reno use Google Analytics?
Yes. We found Google Analytics at Reno through website code. Google Analytics is used by 89,943 companies we track.
How does runsonwhat know what Reno uses?
We read public traces only: Reno'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.