runsonwhat

Teester's tech stack

What does Teester use?

Teester (teester.com) uses at least 9 tools we can see from public records, including Microsoft 365 for email and documents, Zendesk for customer support, Cloudflare for content delivery and Mailjet for email delivery. Last checked .

Industry
Internet
Size
201–1,000 employees
Based in
Nantes, France
Founded
2016
LinkedIn
Company page
Re-check liveVisit teester.com
Tools found
9
Categories
7
Layers
3 of 5
Last checked
Oct 2026

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

CDN & Edge

Go-to-market

4 tools, how they find and keep customers

Marketing

Ads & Pixels

Support & Docs

Company Ops

4 tools, what the team runs on day to day

Email Delivery

Workspace

Dev Tools

Companies like Teester also use

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

Companies with a stack like Teester's

Ranked by shared tools, with rare tools counting more.

Teester tech stack FAQ

What tools does Teester use?

We've found 9 tools at Teester (teester.com). Edge & Hosting: Cloudflare. Go-to-market: Meta Pixel, Zendesk and GitBook. Company Ops: Microsoft 365, Google Workspace and Atlassian. Last checked October 6, 2026.

What email provider does Teester use?

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

What does Teester use for customer support?

Teester uses Zendesk and GitBook for customer support. We found Zendesk through email records.

Does Teester use Microsoft 365?

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

How does runsonwhat know what Teester uses?

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