Valet's tech stack
What does Valet use?
Valet (valet.dev) uses at least 6 tools we can see from public records, including Fly.io for hosting, Google Workspace for email and documents, Google Tag Manager for analytics and Termly for security. Last checked .
“Valet is the missing SDLC for your team's vibe-coded apps. Build using your favorite agent. Valet handles everything after: SSO, secrets, data access, an owner, and a fix when it breaks.”
- Industry
- Internet
- Size
- 1–10 employees
- Based in
- San Francisco, United States
- Founded
- 2026
- Company page
- Tools found
- 6
- Categories
- 6
- Layers
- 5 of 5
- Last checked
- Oct 2026
Valet'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
1 tool, what the product is built with
Media & UI
Data & Observability
1 tool, what they measure and store
Analytics
Go-to-market
1 tool, how they find and keep customers
Marketing
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Valet tech stack FAQ
What tools does Valet use?
We've found 6 tools at Valet (valet.dev). Edge & Hosting: Fly.io. Application: Google Fonts. Data & Observability: Google Tag Manager. Company Ops: Google Workspace and Termly. Last checked October 2, 2026.
What cloud does Valet run on?
Valet uses Fly.io for hosting. We found Fly.io through custom domain and website code.
What email provider does Valet use?
Valet uses Google Workspace for email and documents. We found Google Workspace through email records.
What analytics tools does Valet use?
Valet uses Google Tag Manager for analytics. We found Google Tag Manager through website code.
Does Valet use Google Fonts?
Yes. We found Google Fonts at Valet through website code. Google Fonts is used by 505,894 companies we track.
How does runsonwhat know what Valet uses?
We read public traces only: Valet'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.