runsonwhat

Isoquant's tech stack

What does Isoquant use?

Isoquant (isoquant.ai) uses at least 9 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Vercel Analytics for analytics and WorkOS for sign-in. Last checked .

“Self-optimizing inference cloud for faster, cheaper AI”

Industry
B2B
Size
1–10 employees
Based in
San Francisco, United States
LinkedIn
Company page
Tools found
9
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

3 tools, where the bytes are served from

Application

2 tools, what the product is built with

Auth & Identity

Data & Observability

1 tool, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Isoquant tech stack FAQ

What tools does Isoquant use?

We've found 9 tools at Isoquant (isoquant.ai). Edge & Hosting: GoDaddy, Vercel and Amazon Web Services. Application: Next.js and WorkOS. Data & Observability: Vercel Analytics. Company Ops: Google Workspace and Resend. Last checked October 2, 2026.

What cloud does Isoquant run on?

Isoquant uses Vercel and Amazon Web Services for hosting. We found Vercel through DNS verification records, DNS records and website code.

What email provider does Isoquant use?

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

What analytics tools does Isoquant use?

Isoquant uses Vercel Analytics for analytics. We found Vercel Analytics through website code.

Does Isoquant use Google Workspace?

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

How does runsonwhat know what Isoquant uses?

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