runsonwhat

Audacity's tech stack

What does Audacity use?

Audacity (audacityteam.org) uses at least 11 tools we can see from public records, including Netlify for hosting, Google Workspace for email and documents, Discord for customer support and Matomo for analytics. Last checked .

Industry
Software
Size
11–50 employees
Based in
London, United Kingdom
Founded
1999
LinkedIn
Company page
Tools found
11
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

CDN & Edge

Application

2 tools, what the product is built with

Frontend

Media & UI

Data & Observability

1 tool, what they measure and store

Analytics

Go-to-market

3 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Audacity tech stack FAQ

What tools does Audacity use?

We've found 11 tools at Audacity (audacityteam.org). Edge & Hosting: Cloudflare and Netlify. Application: YouTube and Astro. Data & Observability: Matomo. Go-to-market: Discord and GitBook. Company Ops: Google Workspace, SendGrid and Amazon SES. Last checked October 3, 2026.

What cloud does Audacity run on?

Audacity uses Netlify for hosting. We found Netlify through DNS records and website code.

What email provider does Audacity use?

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

What does Audacity use for customer support?

Audacity uses Discord and GitBook for customer support. We found Discord through website code.

What analytics tools does Audacity use?

Audacity uses Matomo for analytics. We found Matomo through website code.

Does Audacity use Cloudflare?

Yes. We found Cloudflare at Audacity through DNS records. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Audacity uses?

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