Conductor's tech stack
What does Conductor use?
Conductor (conductor.build) uses at least 11 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 .
“Conductor is a Mac app for running Claude Code, Codex, and Cursor agents in parallel across isolated workspaces.”
- Industry
- Engineering, Product and Design
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Tools found
- 11
- Categories
- 11
- Layers
- 5 of 5
- Last checked
- Oct 2026
Conductor'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
3 tools, what the product is built with
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
2 tools, how they find and keep customers
Marketing
Support & Docs
Company Ops
3 tools, what the team runs on day to day
Conductor tech stack FAQ
What tools does Conductor use?
We've found 11 tools at Conductor (conductor.build). Edge & Hosting: Cloudflare and Vercel. Application: Next.js and WorkOS. Data & Observability: PostHog. Go-to-market: Discord. Company Ops: Google Workspace, Resend and Vanta. Last checked October 2, 2026.
What cloud does Conductor run on?
Conductor uses Vercel for hosting. We found Vercel through DNS verification records and website code.
What email provider does Conductor use?
Conductor uses Google Workspace for email and documents. We found Google Workspace through email records.
What does Conductor use for customer support?
Conductor uses Discord for customer support. We found Discord through website code.
What analytics tools does Conductor use?
Conductor uses PostHog for analytics. We found PostHog through website code.
Does Conductor use Cloudflare?
Yes. We found Cloudflare at Conductor through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Conductor uses?
We read public traces only: Conductor'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.