runsonwhat

TokenSpend's tech stack

What does TokenSpend use?

TokenSpend (tokenspend.dev) uses at least 13 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 .

“TokenSpend routes every frontier model through one API, with a metered receipt at list price for every request, and ties AI coding spend to the code it shipped.”

Tools found
13
Categories
10
Layers
5 of 5
Last checked
Oct 2026

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

1 tool, where the bytes are served from

Hosting & Cloud

Application

3 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Company Ops

5 tools, what the team runs on day to day

TokenSpend tech stack FAQ

What tools does TokenSpend use?

We've found 13 tools at TokenSpend (tokenspend.dev). Edge & Hosting: Vercel. Application: GSAP and Next.js. Data & Observability: web-vitals, PostHog and Vercel Analytics. Company Ops: Google Workspace, Let's Encrypt and Sectigo. Last checked October 2, 2026.

What cloud does TokenSpend run on?

TokenSpend uses Vercel for hosting. We found Vercel through DNS records.

What email provider does TokenSpend use?

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

What analytics tools does TokenSpend use?

TokenSpend uses PostHog and Vercel Analytics for analytics. We found PostHog through website code.

Does TokenSpend use Google Workspace?

Yes. We found Google Workspace at TokenSpend through email records. Google Workspace is used by 384,321 companies we track.

How does runsonwhat know what TokenSpend uses?

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