runsonwhat

ContextVault's tech stack

What does ContextVault use?

ContextVault (contextvault.dev) uses at least 11 tools we can see from public records, including Vercel for hosting, Microsoft 365 for email and documents, Google Analytics for analytics and Clerk for sign-in. Last checked .

Tools found
11
Categories
8
Oldest proven tool
May 2026
Last checked
Oct 2026

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

4 tools, what the product is built with

Data & Observability

4 tools, what they measure and store

Company Ops

1 tool, what the team runs on day to day

What changed at ContextVault

Using since

Dates come from the first certificate of the subdomain that points at the tool.

  1. Clerk

ContextVault tech stack FAQ

What tools does ContextVault use?

We've found 11 tools at ContextVault (contextvault.dev). Edge & Hosting: Cloudflare and Vercel. Application: Google Fonts, Adobe Fonts and Next.js. Data & Observability: Google Analytics, Google Tag Manager and Sentry. Company Ops: Microsoft 365. Last checked October 2, 2026.

What cloud does ContextVault run on?

ContextVault uses Vercel for hosting. We found Vercel through custom domain, DNS verification records, DNS records and website code.

What email provider does ContextVault use?

ContextVault uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does ContextVault use?

ContextVault uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

Does ContextVault use Microsoft 365?

Yes. We found Microsoft 365 at ContextVault through DNS verification records. Microsoft 365 is used by 674,699 companies we track.

How does runsonwhat know what ContextVault uses?

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