runsonwhat

Namespace Labs's tech stack

What does Namespace Labs use?

Namespace Labs (namespace.so) uses at least 19 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 .

“Namespace accelerates the development workflow of fast-moving software engineering teams.”

Based in
San Francisco, United States
Founded
2021
LinkedIn
Company page
Re-check liveVisit namespace.so
Tools found
19
Categories
13
Layers
5 of 5
Last checked
Oct 2026

Namespace Labs'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

7 tools, what the product is built with

Frontend

Auth & Identity

AI

Media & UI

Data & Observability

3 tools, what they measure and store

Monitoring

Analytics

Go-to-market

4 tools, how they find and keep customers

Marketing

Ads & Pixels

Support & Docs

Company Ops

3 tools, what the team runs on day to day

Workspace

Security & Compliance

Companies like Namespace Labs also use

Tools common among companies with a similar stack that we haven't found at Namespace Labs.

Companies with a stack like Namespace Labs's

Ranked by shared tools, with rare tools counting more.

Namespace Labs tech stack FAQ

What tools does Namespace Labs use?

As of October 2026, runsonwhat has found 19 tools at Namespace Labs (namespace.so) in public records. Edge & Hosting: Cloudflare and Vercel. Application: YouTube, React and Tailwind CSS. Data & Observability: Sentry, web-vitals and PostHog. Go-to-market: LinkedIn Insight Tag, LinkedIn and Discord. Company Ops: Google Workspace, DMARC Digests and Vanta. Last checked October 7, 2026.

What cloud does Namespace Labs run on?

Namespace Labs 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 46,079 companies runsonwhat tracks.

What email provider does Namespace Labs use?

Namespace Labs uses Google Workspace for email and office software, according to runsonwhat (October 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace and code on namespace.so. Google Workspace is used by 395,445 companies runsonwhat tracks.

What does Namespace Labs use for customer support?

Namespace Labs uses Discord for customer support and documentation, according to runsonwhat (October 2026). runsonwhat found Discord through Discord code on namespace.so. Discord is used by 4,362 companies runsonwhat tracks.

What analytics tools does Namespace Labs use?

Namespace Labs uses PostHog for analytics, according to runsonwhat (October 2026). runsonwhat found PostHog through PostHog code on namespace.so. PostHog is used by 9,213 companies runsonwhat tracks.

What marketing software does Namespace Labs use?

Namespace Labs uses LinkedIn for marketing, according to runsonwhat (October 2026). runsonwhat found LinkedIn through a DNS verification record for LinkedIn. LinkedIn is used by 14,612 companies runsonwhat tracks.

Does Namespace Labs use Cloudflare?

Yes. runsonwhat found Cloudflare at Namespace Labs through DNS records that point at Cloudflare and email records. Cloudflare is a CDN & Edge tool used by 689,728 companies runsonwhat tracks.

Which companies have a tech stack similar to Namespace Labs's?

The companies with the stacks most like Namespace Labs' are Sully, Veris AI, Decagon and Wildcard, according to runsonwhat (October 2026). Each shares 8 to 9 tools with Namespace Labs, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.

How does runsonwhat know what Namespace Labs uses?

runsonwhat reads public records only. Of the 19 tools at Namespace Labs, 10 were found through code on namespace.so, 3 through DNS records, 3 through subdomains that point at the vendor, 2 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 namespace.so 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.