# Vercel — How v0 authenticates to Snowflake without exposing the user's OAuth token

- Company: Vercel (vercel.com)
- Announced: 2026-08-20T04:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://vercel.com/blog/how-v0-authenticates-to-snowflake-without-exposing-the-users-oauth-token
- Record: https://forck.live/items/20668-how-v0-authenticates-to-snowflake-without-exposing-the-user-s-oauth-token
- Subject: v0 / AI SDK / AI Gateway

Vercel describes how its v0 Snowflake integration authenticates to Snowflake without exposing the user's OAuth token to generated code. A request proxy outside the sandbox resolves the real credential at request time, while a fixed placeholder string inside the sandbox preserves compatibility with Snowflake clients.

## Evidence

Verbatim from https://vercel.com/blog/how-v0-authenticates-to-snowflake-without-exposing-the-users-oauth-token:

> We solved this with a Snowflake request proxy for v0 sandboxes, built on the Vercel Sandbox firewall. The sandbox can run normal Snowflake clients, but the real credential is resolved at request time in a server proxy outside the sandbox runtime.

---

Record: https://forck.live/items/20668-how-v0-authenticates-to-snowflake-without-exposing-the-user-s-oauth-token
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md