# Vercel — How we migrated the database behind every Vercel build

- Company: Vercel (vercel.com)
- Announced: 2026-08-11T22:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://vercel.com/blog/how-we-migrated-the-database-behind-every-vercel-build
- Record: https://forck.live/items/20673-how-we-migrated-the-database-behind-every-vercel-build
- Subject: v0 / AI SDK / AI Gateway

Vercel migrated the database behind its build warm pool from Redis to DynamoDB. The state, which tracks container readiness, authentication tokens, and billing mappings, had become too important to keep in an ephemeral cache. The migration ran live under production traffic in feature-flagged phases, with the container ID as the new sort key and tokens stored as hashes.

## Evidence

Verbatim from https://vercel.com/blog/how-we-migrated-the-database-behind-every-vercel-build:

> The problem is that the pool never stops. Containers are coming up, polling, picking up work, and expiring around the clock, which meant we couldn't pause the world, copy the data, and restart. The migration had to happen live, under production traffic, in phases, each one behind a flag with a rollback ready if we needed it.

---

Record: https://forck.live/items/20673-how-we-migrated-the-database-behind-every-vercel-build
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md