runsonwhat

Pluto's tech stack

What does Pluto use?

Pluto (talentpluto.com) uses at least 15 tools we can see from public records, including Amazon Web Services for hosting, Google Workspace for email and documents, PostHog for analytics and Framer for its website. Last checked .

Industry
Recruiting and Talent
Size
1–10 employees
Based in
San Francisco, United States
Tools found
15
Categories
11
Layers
5 of 5
Last checked
Oct 2026

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

3 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

5 tools, what the team runs on day to day

Pluto tech stack FAQ

What tools does Pluto use?

We've found 15 tools at Pluto (talentpluto.com). Edge & Hosting: Cloudflare, Amazon Web Services and Vercel. Application: Google Fonts, React and Three.js. Data & Observability: web-vitals and PostHog. Go-to-market: Framer. Company Ops: Google Workspace, Apple Business and Amazon SES. Last checked October 2, 2026.

What cloud does Pluto run on?

Pluto uses Amazon Web Services and Vercel for hosting. We found Amazon Web Services through website code.

What email provider does Pluto use?

Pluto uses Google Workspace and Apple Business for email and documents. We found Google Workspace through email records and website code.

What analytics tools does Pluto use?

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

What CMS does Pluto use?

Pluto uses Framer for its website. We found Framer through website code.

Does Pluto use Cloudflare?

Yes. We found Cloudflare at Pluto through DNS records, email records and website code. Cloudflare is used by 375,363 companies we track.

How does runsonwhat know what Pluto uses?

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