Logo.dev's tech stack
What does Logo.dev use?
Logo.dev (logo.dev) uses at least 13 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Clearbit for sales and Vercel Analytics for analytics. Last checked .
“Logo.dev gives developers instant access to millions of verified company logos via a fast, reliable CDN and API.”
- Company page
- Tools found
- 13
- Categories
- 12
- Layers
- 5 of 5
- Last checked
- Oct 2026
Logo.dev'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
5 tools, what the product is built with
Frontend
Auth & Identity
Payments & Billing
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
3 tools, how they find and keep customers
Company Ops
2 tools, what the team runs on day to day
Workspace
Dev Tools
Companies like Logo.dev also use
Tools common among companies with a similar stack that we haven't found at Logo.dev.
Companies with a stack like Logo.dev's
Ranked by shared tools, with rare tools counting more.
Logo.dev tech stack FAQ
What tools does Logo.dev use?
As of October 2026, runsonwhat has found 13 tools at Logo.dev (logo.dev) in public records. Edge & Hosting: Cloudflare and Vercel. Application: Next.js, Stripe and MCP Registry. Data & Observability: Vercel Analytics. Go-to-market: LinkedIn Insight Tag and Clearbit. Company Ops: Google Workspace and GitHub. Last checked October 29, 2026.
What cloud does Logo.dev run on?
Logo.dev uses Vercel for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Vercel through a subdomain that points at Vercel and a DNS verification record. Vercel is used by 49,885 companies runsonwhat tracks.
What sales tools does Logo.dev use?
The sales tools runsonwhat has found at Logo.dev are Clearbit (October 2026); no CRM shows up in Logo.dev's public records. runsonwhat found Clearbit through Clearbit on logo.dev's subprocessor list. Clearbit is used by 139 companies runsonwhat tracks.
What email provider does Logo.dev use?
Logo.dev uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 406,686 companies runsonwhat tracks.
What payment provider does Logo.dev use?
Logo.dev uses Stripe for payments and billing, according to runsonwhat (October 2026). runsonwhat found Stripe through a DNS verification record for Stripe and code on logo.dev. Stripe is used by 30,633 companies runsonwhat tracks.
What analytics tools does Logo.dev use?
Logo.dev uses Vercel Analytics for analytics, according to runsonwhat (October 2026). runsonwhat found Vercel Analytics through Vercel Analytics code on logo.dev. Vercel Analytics is used by 7,913 companies runsonwhat tracks.
Does Logo.dev use Cloudflare?
Yes. runsonwhat found Cloudflare at Logo.dev through DNS records that point at Cloudflare. Cloudflare is a CDN & Edge tool used by 714,439 companies runsonwhat tracks.
Does Logo.dev use AI tools?
Yes. runsonwhat has found MCP Registry at Logo.dev; MCP Registry, for example, through a DNS verification record for MCP Registry. AI services called only from servers leave no public trace, so Logo.dev may use more AI tools than these.
Which companies have a tech stack similar to Logo.dev's?
The companies with the stacks most like Logo.dev's are Amplitude, Vercel, Token Canopy and Trunk, according to runsonwhat (October 2026). Each shares 8 to 12 tools with Logo.dev, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.
How does runsonwhat know what Logo.dev uses?
runsonwhat reads public records only. Of the 13 tools at Logo.dev, 4 were found through DNS records, 3 through its own subprocessor list, 2 through code on logo.dev, 2 through subdomains that point at the vendor, 1 through email records and 1 through website configuration files. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and logo.dev about 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.