runsonwhat

Testlify's tech stack

What does Testlify use?

Testlify (testlify.com) uses at least 19 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Help Scout for customer support and LinkedIn for marketing. Last checked .

Industry
Internet
Size
11–50 employees
Based in
Bensalem, United States
Founded
2022
LinkedIn
Company page
Tools found
19
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

Application

1 tool, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

4 tools, how they find and keep customers

Testlify tech stack FAQ

What tools does Testlify use?

We've found 19 tools at Testlify (testlify.com). Edge & Hosting: Amazon Web Services and Vercel. Application: Anthropic. Data & Observability: incident.io. Go-to-market: LinkedIn, Help Scout and ReadMe. Company Ops: Microsoft 365, Google Workspace and Atlassian. Last checked October 6, 2026.

What cloud does Testlify run on?

Testlify uses Amazon Web Services and Vercel for hosting. We found Amazon Web Services through custom domain.

What email provider does Testlify use?

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

What does Testlify use for customer support?

Testlify uses Help Scout and ReadMe for customer support. We found Help Scout through custom domain.

What marketing software does Testlify use?

Testlify uses LinkedIn for marketing. We found LinkedIn through DNS verification records.

Does Testlify use Microsoft 365?

Yes. We found Microsoft 365 at Testlify through DNS verification records. Microsoft 365 is used by 685,116 companies we track.

How does runsonwhat know what Testlify uses?

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