runsonwhat

Sonarly's tech stack

What does Sonarly use?

Sonarly (sonarly.dev) uses at least 12 tools we can see from public records, including Google Workspace for email and documents, Zoho for sales, Discord for customer support and PostHog for analytics. Last checked .

Tools found
12
Categories
10
Layers
5 of 5
Last checked
Oct 2026

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

Application

4 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

3 tools, how they find and keep customers

Sales & CRM

Support & Docs

Company Ops

1 tool, what the team runs on day to day

Sonarly tech stack FAQ

What tools does Sonarly use?

We've found 12 tools at Sonarly (sonarly.dev). Edge & Hosting: Cloudflare. Application: Google Fonts, YouTube and Stripe. Data & Observability: Sentry, PostHog and Bugsnag. Go-to-market: Zoho and Discord. Company Ops: Google Workspace. Last checked October 2, 2026.

What CRM does Sonarly use?

Sonarly uses Zoho for sales and CRM. We found Zoho through email records.

What email provider does Sonarly use?

Sonarly uses Google Workspace for email and documents. We found Google Workspace through DNS verification records.

What does Sonarly use for customer support?

Sonarly uses Discord for customer support. We found Discord through website code.

What payment provider does Sonarly use?

Sonarly uses Stripe for payments. We found Stripe through website code.

What analytics tools does Sonarly use?

Sonarly uses PostHog for analytics. We found PostHog through website code.

Does Sonarly use Cloudflare?

Yes. We found Cloudflare at Sonarly through DNS records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Sonarly uses?

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