runsonwhat

Sponge's tech stack

What does Sponge use?

Sponge (paysponge.com) uses at least 8 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Discord for customer support and PostHog for analytics. Last checked .

“Financial infrastructure for the agent economy. AI agent wallets, payments, and commerce.”

Industry
B2B
Size
1–10 employees
Based in
San Francisco, United States
Founded
2026
LinkedIn
Company page
Tools found
8
Categories
8
Layers
5 of 5
Last checked
Oct 2026

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

1 tool, what the team runs on day to day

Sponge tech stack FAQ

What tools does Sponge use?

We've found 8 tools at Sponge (paysponge.com). Edge & Hosting: Cloudflare and Vercel. Application: Next.js. Data & Observability: web-vitals and PostHog. Go-to-market: Discord. Company Ops: Google Workspace. Last checked October 2, 2026.

What cloud does Sponge run on?

Sponge uses Vercel for hosting. We found Vercel through DNS verification records and website code.

What email provider does Sponge use?

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

What does Sponge use for customer support?

Sponge uses Discord for customer support. We found Discord through website code.

What analytics tools does Sponge use?

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

Does Sponge use Cloudflare?

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

How does runsonwhat know what Sponge uses?

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