Liquid Compute's tech stack
What does Liquid Compute use?
Liquid Compute (liquidcompute.com) uses at least 10 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Auth0 for sign-in and Let's Encrypt for security. Last checked .
“Pending CFTC regulation to be the first cash and physically settled…”
- Industry
- Banking and Exchange
- Size
- 1–10 employees
- Based in
- New York City, United States
- Founded
- 2025
- Company page
- Tools found
- 10
- Categories
- 6
- Layers
- 4 of 5
- Last checked
- Oct 2026
Liquid Compute'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
Application
2 tools, what the product is built with
Frontend
Auth & Identity
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
5 tools, what the team runs on day to day
Workspace
Security & Compliance
Liquid Compute tech stack FAQ
What tools does Liquid Compute use?
We've found 10 tools at Liquid Compute (liquidcompute.com). Edge & Hosting: Vercel and Amazon Web Services. Application: Next.js and Auth0. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 2, 2026.
What cloud does Liquid Compute run on?
Liquid Compute uses Vercel and Amazon Web Services for hosting. We found Vercel through DNS records.
What email provider does Liquid Compute use?
Liquid Compute uses Google Workspace for email and documents. We found Google Workspace through email records.
Does Liquid Compute use Google Workspace?
Yes. We found Google Workspace at Liquid Compute through email records. Google Workspace is used by 126,364 companies we track.
How does runsonwhat know what Liquid Compute uses?
We read public traces only: Liquid Compute'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.