runsonwhat

Midrender's tech stack

What does Midrender use?

Midrender (midrender.com) uses at least 11 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, PostHog for analytics and web-vitals for monitoring. Last checked .

“Turn product features into launch videos”

Industry
Engineering, Product and Design
Size
1–10 employees
Based in
San Francisco, United States
Tools found
11
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

Hosting & Cloud

CDN & Edge

Application

3 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

Company Ops

2 tools, what the team runs on day to day

Email Delivery

Midrender tech stack FAQ

What tools does Midrender use?

We've found 11 tools at Midrender (midrender.com). Edge & Hosting: Cloudflare, Vercel and Render. Application: React, Tailwind CSS and Next.js. Data & Observability: web-vitals and PostHog. Company Ops: Google Workspace and Resend. Last checked October 2, 2026.

What cloud does Midrender run on?

Midrender uses Vercel and Render for hosting. We found Vercel through DNS verification records, DNS records and website code.

What email provider does Midrender use?

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

What analytics tools does Midrender use?

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

Does Midrender use Cloudflare?

Yes. We found Cloudflare at Midrender through DNS records and website code. Cloudflare is used by 498,249 companies we track.

How does runsonwhat know what Midrender uses?

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