runsonwhat

Testo's tech stack

What does Testo use?

Testo (testo.com) uses at least 16 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Oracle Eloqua for marketing and Auth0 for sign-in. Last checked .

Based in
Germany
Founded
1957
Re-check liveVisit testo.com
Tools found
16
Categories
10
Layers
4 of 5
Last checked
Oct 2026

Testo'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

DNS

Application

2 tools, what the product is built with

Auth & Identity

Media & UI

Go-to-market

3 tools, how they find and keep customers

Marketing

Ads & Pixels

Company Ops

9 tools, what the team runs on day to day

Workspace

Collaboration

Dev Tools

Security & Compliance

Companies like Testo also use

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

Companies with a stack like Testo's

Ranked by shared tools, with rare tools counting more.

Testo tech stack FAQ

What tools does Testo use?

We've found 16 tools at Testo (testo.com). Edge & Hosting: Amazon Route 53 and Vercel. Application: Cloudinary and Auth0. Go-to-market: Meta Pixel and Oracle Eloqua. Company Ops: Microsoft 365, Atlassian and Let's Encrypt. Last checked October 2, 2026.

What cloud does Testo run on?

Testo uses Vercel for hosting. We found Vercel through custom domain, DNS verification records, DNS records and website code.

What email provider does Testo use?

Testo uses Microsoft 365 and Tencent Exmail for email and documents. We found Microsoft 365 through email records and DNS verification records.

What marketing software does Testo use?

Testo uses Oracle Eloqua for marketing. We found Oracle Eloqua through custom domain.

Does Testo use Microsoft 365?

Yes. We found Microsoft 365 at Testo through email records and DNS verification records. Microsoft 365 is used by 685,697 companies we track.

How does runsonwhat know what Testo uses?

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