runsonwhat

Vesence AB's tech stack

What does Vesence AB use?

Vesence AB (vesence.com) uses at least 8 tools we can see from public records, including Microsoft Azure for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Cloudflare for content delivery. Last checked .

“An agent-native computer in the browser, where agents work in your email, files and Office documents.”

Industry
B2B
Size
1–10 employees
Based in
San Francisco, Sweden
Founded
2024
Tools found
8
Categories
7
Layers
5 of 5
Last checked
Oct 2026

Vesence AB'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

2 tools, what the product is built with

Media & UI

Data & Observability

1 tool, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Vesence AB tech stack FAQ

What tools does Vesence AB use?

We've found 8 tools at Vesence AB (vesence.com). Edge & Hosting: Cloudflare and Microsoft Azure. Application: Vimeo and Next.js. Data & Observability: Google Analytics. Company Ops: Microsoft 365 and Apple Business. Last checked October 2, 2026.

What cloud does Vesence AB run on?

Vesence AB uses Microsoft Azure for hosting. We found Microsoft Azure through custom domain and subprocessor list.

What email provider does Vesence AB use?

Vesence AB uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through email records.

What analytics tools does Vesence AB use?

Vesence AB uses Google Analytics for analytics. We found Google Analytics through website code.

Does Vesence AB use Microsoft 365?

Yes. We found Microsoft 365 at Vesence AB through email records. Microsoft 365 is used by 260,779 companies we track.

How does runsonwhat know what Vesence AB uses?

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