runsonwhat

LiveText's tech stack

What does LiveText use?

LiveText (livetext.com) uses at least 8 tools we can see from public records, including Amazon Web Services for hosting, Microsoft 365 for email and documents, Zendesk for customer support and Pardot for marketing. Last checked .

Industry
E-learning
Size
11–50 employees
Based in
La Grange, United States
Founded
1997
LinkedIn
Company page
Tools found
8
Categories
7
Layers
4 of 5
Last checked
Oct 2026

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

Go-to-market

2 tools, how they find and keep customers

Marketing

Support & Docs

Company Ops

3 tools, what the team runs on day to day

LiveText tech stack FAQ

What tools does LiveText use?

We've found 8 tools at LiveText (livetext.com). Edge & Hosting: Amazon Route 53 and Amazon Web Services. Application: jQuery. Go-to-market: Zendesk and Pardot. Company Ops: Microsoft 365, Google Workspace and Amazon Trust Services. Last checked October 3, 2026.

What cloud does LiveText run on?

LiveText uses Amazon Web Services for hosting. We found Amazon Web Services through custom domain.

What email provider does LiveText use?

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

What does LiveText use for customer support?

LiveText uses Zendesk for customer support. We found Zendesk through email records.

What marketing software does LiveText use?

LiveText uses Pardot for marketing. We found Pardot through DNS verification records and email records.

Does LiveText use Microsoft 365?

Yes. We found Microsoft 365 at LiveText through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what LiveText uses?

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