runsonwhat

Midplane's tech stack

What does Midplane use?

Midplane (midplane.ai) uses at least 9 tools we can see from public records, including Fly.io for hosting, Google Workspace for email and documents, PostHog for analytics and Clerk for sign-in. Last checked .

“The safety layer between AI agents and your database”

Industry
Engineering, Product and Design
Size
1–10 employees
Based in
Berlin, Germany
Tools found
9
Categories
9
Oldest proven tool
May 2026
Last checked
Oct 2026

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

Data & Observability

2 tools, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

1 tool, what the team runs on day to day

What changed at Midplane

Using since

Dates come from the first certificate of the subdomain that points at the tool.

  1. Clerk

Midplane tech stack FAQ

What tools does Midplane use?

We've found 9 tools at Midplane (midplane.ai). Edge & Hosting: Cloudflare and Fly.io. Application: Next.js and Clerk. Data & Observability: web-vitals and PostHog. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does Midplane run on?

Midplane uses Fly.io for hosting. We found Fly.io through custom domain and website code.

What email provider does Midplane use?

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

What analytics tools does Midplane use?

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

Does Midplane use Cloudflare?

Yes. We found Cloudflare at Midplane through DNS records, email records and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Midplane uses?

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