runsonwhat

DIVR Labs's tech stack

What does DIVR Labs use?

DIVR Labs (divrlabs.com) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Webflow for its website and Mailchimp for marketing. Last checked .

Industry
Virtual Reality
Based in
Czechia
Founded
2016
LinkedIn
Company page
Tools found
11
Categories
8
Layers
5 of 5
Last checked
Oct 2026

DIVR Labs'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

Application

1 tool, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

5 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

DIVR Labs tech stack FAQ

What tools does DIVR Labs use?

We've found 11 tools at DIVR Labs (divrlabs.com). Edge & Hosting: Cloudflare. Application: jQuery. Data & Observability: Google Analytics. Go-to-market: Google Ads, Mailchimp and Webflow. Company Ops: Microsoft 365, Google Workspace and Resend. Last checked October 4, 2026.

What email provider does DIVR Labs use?

DIVR Labs uses Microsoft 365 and Google Workspace for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does DIVR Labs use?

DIVR Labs uses Google Analytics for analytics. We found Google Analytics through website code.

What CMS does DIVR Labs use?

DIVR Labs uses Webflow for its website. We found Webflow through custom domain and website code.

What marketing software does DIVR Labs use?

DIVR Labs uses Mailchimp and Elfsight for marketing. We found Mailchimp through email records.

Does DIVR Labs use Microsoft 365?

Yes. We found Microsoft 365 at DIVR Labs through DNS verification records. Microsoft 365 is used by 322,704 companies we track.

How does runsonwhat know what DIVR Labs uses?

We read public traces only: DIVR Labs'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.