runsonwhat

Operator.io's tech stack

What does Operator.io use?

Operator.io (operator.io) uses at least 13 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Google Analytics for analytics and Clerk for sign-in. Last checked .

“Operator.io is OpenClaw that just works”

Industry
B2B
Size
1–10 employees
Based in
New York City, United States
LinkedIn
Company page
Tools found
13
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Operator.io'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

4 tools, what the product is built with

Data & Observability

2 tools, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Ads & Pixels

Company Ops

3 tools, what the team runs on day to day

Operator.io tech stack FAQ

What tools does Operator.io use?

We've found 13 tools at Operator.io (operator.io). Edge & Hosting: Cloudflare, Vercel and Microsoft Azure. Application: Next.js, Tailwind CSS and Clerk. Data & Observability: Google Analytics and PostHog. Go-to-market: Google Ads. Company Ops: Google Workspace, SendGrid and Resend. Last checked October 2, 2026.

What cloud does Operator.io run on?

Operator.io uses Vercel and Microsoft Azure for hosting. We found Vercel through DNS verification records, DNS records and website code.

What email provider does Operator.io use?

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

What analytics tools does Operator.io use?

Operator.io uses Google Analytics and PostHog for analytics. We found Google Analytics through website code.

Does Operator.io use Cloudflare?

Yes. We found Cloudflare at Operator.io through DNS records. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Operator.io uses?

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