Vercel Private Blob is now generally available
Vercel just shipped Private Blob GA. For AI builders storing agent memory, user uploads, and sensitive files—this matters: OIDC auth, signed URLs, zero static tokens.
Why it matters
AI applications increasingly need secure file storage for agent memory, user uploads, and sensitive data. Vercel's Private Blob GA with OIDC and signed URLs lowers the operational burden for builders shipping production AI features without managing credentials.
The key facts
12 to knowVercel Private Blob now generally available across all plans
OIDC authentication with short-lived, auto-rotating tokens (no static credentials)
Signed URLs support with configurable expiration (up to 7 days)
Use cases: agent memory storage, user-uploaded files, invoices, sensitive documents
CLI support for OIDC authentication
Supports PUT, GET, HEAD, DELETE operations on private objects
Private Blob now GA across all Vercel plans
OIDC authentication with auto-rotating, short-lived tokens (no static credentials)
Signed URLs support scoped access (PUT, GET, HEAD, DELETE) with configurable expiration up to 7 days
Use case explicitly called out: agent memory and sensitive file storage
CLI now supports OIDC for terminal-based access
Migration path from static tokens to OIDC with dashboard revocation
Go to the source
Vercel Blogvercel.com
Publisher excerpt: Vercel Private Blob is now generally available for all plans. Store sensitive files like user-uploaded photos, invoices, and agent memory, and control exactly who can read them. Private stores, Signed URLs, and OIDC authentication all graduate from beta with this release. Vercel Private Blob uses…