diva-e's tech stack
What does diva-e use?
diva-e (divae.com) uses at least 12 tools we can see from public records, including Netlify for hosting, HubSpot for sales, Google Analytics for analytics and Storyblok for its website. Last checked .
- Industry
- IT Services
- Size
- 201–1,000 employees
- Based in
- München, Germany
- Founded
- 2015
- Company page
- Tools found
- 12
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
diva-e'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
Hosting & Cloud
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Search
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
5 tools, how they find and keep customers
Website & CMS
Sales & CRM
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
diva-e tech stack FAQ
What tools does diva-e use?
We've found 12 tools at diva-e (divae.com). Edge & Hosting: Cloudflare and Netlify. Application: Vue.js, Nuxt and Algolia. Data & Observability: Google Analytics. Go-to-market: Google Ads, Meta Pixel and HubSpot. Company Ops: Usercentrics. Last checked October 6, 2026.
What cloud does diva-e run on?
diva-e uses Netlify for hosting. We found Netlify through website code.
What CRM does diva-e use?
diva-e uses HubSpot for sales and CRM. We found HubSpot through website code.
What analytics tools does diva-e use?
diva-e uses Google Analytics for analytics. We found Google Analytics through website code.
What CMS does diva-e use?
diva-e uses Storyblok for its website. We found Storyblok through website code.
Does diva-e use Cloudflare?
Yes. We found Cloudflare at diva-e through DNS records. Cloudflare is used by 567,378 companies we track.
How does runsonwhat know what diva-e uses?
We read public traces only: diva-e'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.