runsonwhat

Radius's tech stack

What does Radius use?

Radius (radiusbrowser.com) uses at least 12 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Discord for customer support and PostHog for analytics. Last checked .

“Code and browse in the same place”

Industry
Engineering, Product and Design
Size
1–10 employees
Based in
San Francisco, United States
Tools found
12
Categories
9
Layers
5 of 5
Last checked
Oct 2026

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

Hosting & Cloud

Application

2 tools, what the product is built with

Auth & Identity

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

Radius tech stack FAQ

What tools does Radius use?

We've found 12 tools at Radius (radiusbrowser.com). Edge & Hosting: Vercel. Application: Next.js and WorkOS. Data & Observability: PostHog and Vercel Analytics. Go-to-market: Discord. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 2, 2026.

What cloud does Radius run on?

Radius uses Vercel for hosting. We found Vercel through DNS records.

What email provider does Radius use?

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

What does Radius use for customer support?

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

What analytics tools does Radius use?

Radius uses PostHog and Vercel Analytics for analytics. We found PostHog through website code.

Does Radius use Google Workspace?

Yes. We found Google Workspace at Radius through email records. Google Workspace is used by 126,364 companies we track.

How does runsonwhat know what Radius uses?

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