runsonwhat

BrowserOS's tech stack

What does BrowserOS use?

BrowserOS (browseros.com) uses at least 13 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 .

“The Open Source Agentic Browser”

Industry
Consumer
Size
1–10 employees
Based in
San Francisco, United States
Tools found
13
Categories
10
Layers
5 of 5
Last checked
Oct 2026

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

6 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

2 tools, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

BrowserOS tech stack FAQ

What tools does BrowserOS use?

We've found 13 tools at BrowserOS (browseros.com). Edge & Hosting: Cloudflare and Vercel. Application: Google Fonts, YouTube and Tailwind CSS. Data & Observability: web-vitals and PostHog. Go-to-market: Discord. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does BrowserOS run on?

BrowserOS uses Vercel for hosting. We found Vercel through custom domain and DNS verification records.

What email provider does BrowserOS use?

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

What does BrowserOS use for customer support?

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

What analytics tools does BrowserOS use?

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

Does BrowserOS use Cloudflare?

Yes. We found Cloudflare at BrowserOS through DNS records and website code. Cloudflare is used by 569,071 companies we track.

How does runsonwhat know what BrowserOS uses?

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