runsonwhat

LiveOne's tech stack

What does LiveOne use?

LiveOne (slacker.com) uses at least 20 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, Zendesk for customer support and Google Analytics for analytics. Last checked .

Tools found
20
Categories
8
Layers
4 of 5
Last checked
Oct 2026

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

CDN & Edge

Data & Observability

2 tools, what they measure and store

Company Ops

1 tool, what the team runs on day to day

LiveOne tech stack FAQ

What tools does LiveOne use?

We've found 20 tools at LiveOne (slacker.com). Edge & Hosting: Amazon Web Services and Akamai. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Meta Pixel and Google Ads. Company Ops: Google Workspace. Last checked October 6, 2026.

What cloud does LiveOne run on?

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

What email provider does LiveOne use?

LiveOne uses Google Workspace for email and documents. We found Google Workspace through email records.

What does LiveOne use for customer support?

LiveOne uses Zendesk for customer support. We found Zendesk through custom domain and email records.

What analytics tools does LiveOne use?

LiveOne uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does LiveOne use?

LiveOne uses WordPress for its website. We found WordPress through website code.

Does LiveOne use Google Workspace?

Yes. We found Google Workspace at LiveOne through email records. Google Workspace is used by 378,849 companies we track.

How does runsonwhat know what LiveOne uses?

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