runsonwhat

LLM Gateway's tech stack

What does LLM Gateway use?

LLM Gateway (llmgateway.io) uses at least 9 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, PostHog for analytics and Brevo for marketing. Last checked .

“Route, manage, and analyze your LLM requests across multiple providers with a unified API interface.”

Based in
Lewes, United States
Tools found
9
Categories
8
Layers
5 of 5
Last checked
Oct 2026

LLM Gateway'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

1 tool, 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

2 tools, what the team runs on day to day

Security & Compliance

LLM Gateway tech stack FAQ

What tools does LLM Gateway use?

We've found 9 tools at LLM Gateway (llmgateway.io). Edge & Hosting: Cloudflare and Vercel. Application: Next.js. Data & Observability: PostHog and Better Stack. Go-to-market: Brevo. Company Ops: Google Workspace and Comp AI. Last checked October 2, 2026.

What cloud does LLM Gateway run on?

LLM Gateway uses Vercel for hosting. We found Vercel through custom domain.

What email provider does LLM Gateway use?

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

What analytics tools does LLM Gateway use?

LLM Gateway uses PostHog for analytics. We found PostHog through website code.

What marketing software does LLM Gateway use?

LLM Gateway uses Brevo for marketing. We found Brevo through DNS verification records.

Does LLM Gateway use Cloudflare?

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

How does runsonwhat know what LLM Gateway uses?

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