runsonwhat

Prom's tech stack

What does Prom use?

Prom (prom.dev) uses at least 16 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, PostHog for analytics and Sentry for monitoring. Last checked .

Re-check liveVisit prom.dev
Tools found
16
Categories
11
Layers
5 of 5
Last checked
Oct 2026

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

Frontend

AI

Media & UI

Data & Observability

3 tools, what they measure and store

Monitoring

Analytics

Go-to-market

1 tool, how they find and keep customers

Marketing

Company Ops

7 tools, what the team runs on day to day

Email Delivery

Workspace

Security & Compliance

Companies like Prom also use

Tools common among companies with a similar stack that we haven't found at Prom.

Companies with a stack like Prom's

Ranked by shared tools, with rare tools counting more.

Prom tech stack FAQ

What tools does Prom use?

We've found 16 tools at Prom (prom.dev). Edge & Hosting: Cloudflare and Vercel. Application: Google Fonts and Tailwind CSS. Data & Observability: Sentry, web-vitals and PostHog. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 2, 2026.

What cloud does Prom run on?

Prom uses Vercel for hosting. We found Vercel through custom domain.

What email provider does Prom use?

Prom uses Google Workspace for email and documents. We found Google Workspace through email records and website code.

What analytics tools does Prom use?

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

Does Prom use Cloudflare?

Yes. We found Cloudflare at Prom through DNS records and website code. Cloudflare is used by 380,284 companies we track.

How does runsonwhat know what Prom uses?

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