runsonwhat

Dymind's tech stack

What does Dymind use?

Dymind (dymind.com) uses at least 7 tools we can see from public records, including Microsoft 365 for email and documents, Zendesk for customer support and Google Analytics for analytics. Last checked .

Industry
Medical Devices
Size
1,001–5,000 employees
Based in
Shenzhen, China
Founded
2013
LinkedIn
Company page
Re-check liveVisit dymind.com
Tools found
7
Categories
6
Layers
4 of 5
Last checked
Oct 2026

Dymind'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.

Application

2 tools, what the product is built with

Frontend

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

2 tools, how they find and keep customers

Marketing

Support & Docs

Company Ops

2 tools, what the team runs on day to day

Workspace

Collaboration

Companies like Dymind also use

Tools common among companies with a similar stack that we haven't found at Dymind.

Companies with a stack like Dymind's

Ranked by shared tools, with rare tools counting more.

Dymind tech stack FAQ

What tools does Dymind use?

We've found 7 tools at Dymind (dymind.com). Application: Vue.js and Nuxt. Data & Observability: Google Analytics. Go-to-market: Zendesk. Company Ops: Microsoft 365 and Lark. Last checked October 7, 2026.

What email provider does Dymind use?

Dymind uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What does Dymind use for customer support?

Dymind uses Zendesk for customer support. We found Zendesk through email records and website code.

What analytics tools does Dymind use?

Dymind uses Google Analytics for analytics. We found Google Analytics through website code.

Does Dymind use Google Analytics?

Yes. We found Google Analytics at Dymind through website code. Google Analytics is used by 732,684 companies we track.

How does runsonwhat know what Dymind uses?

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