Vercel KV Limits
Learn about Vercel KV's technical limitations.Vercel KV provides durable, serverless Redis storage. It supports nearly all Redis commands, and is compatible with most Redis clients. This page outlines the limitations of Vercel KV.
Vercel KV was built in partnership with Upstash, which means many of Upstash's features are available with KV. However, there are some differences worth knowing about, including currently unsupported features.
The following is a list of Upstash features that Vercel KV does not currently support:
- Managing or creating a Vercel KV store from Upstash's web console
- Backup/Restore – Use
redis-cliinstead - Disabling TLS
- Detailed runtime metrics
- Upstash's Pro and Enterprise addons
We also do not support redis-cli version 5, due to its lack of TLS support.
The following is a general list of limitations with Vercel KV:
- It is not possible to transfer your database between accounts or across plans. This includes transferring from Hobby to Pro or Pro to Enterprise.
- Provisioning a KV store from the Vercel CLI is not currently supported (coming soon)
- Provisioning a KV store from the Vercel Terraform Provider is not currently supported
- Changing the primary region of a Vercel KV store is not currently supported. Instead, you must create a new store and migrate your data
- The
node-redisandioredismodules are not supported in Edge Functions. Instead, prefer using the SDK - There is a limit of 3,000 requests per day for users on the Hobby plan. When this limit is reached, requests to the database will be rate limited
- The Hobby plan has a maximum database size of 256 MB. The database will be rate limited when the maximum requests have been reached. When the maximum storage is reached, writes will fail
- There is currently a limit of 5 KV databases that can be created per Pro account
The below table outlines the technical limitations of Vercel KV depending on your plan:
Limit | Hobby | Pro |
|---|---|---|
Max commands per second | 1000 | 1000 |
Max request size | 1 MB | 1 MB |
Max record size | 100 MB | 100 MB |
Max data size | - | 10 GB |
Max number of concurrent connections | 100 | 1000 |
Max number of daily requests | 3000 | - |
Max database size | 256 MB | - |
Max daily bandwidth | 50 GB | 50 GB |
When using a read only token to connect to your KV store, you will not have access to any write commands. You will also not have access to the KEYS command.
Vercel KV creates a single Redis store as your primary region. Writes are routed to the primary region, then replicated to other read regions you define.
Support for replication to other regions is an additional charge. You can have up to four additional read replicas. Learn more about usage and pricing for Vercel KV.
The following regions are available for Vercel KV. You can select a single primary region, and up to four additional read replicas.
Region Code | Region Name | Location |
|---|---|---|
dub1 | eu-west-1 | Dublin, Ireland |
fra1 | eu-central-1 | Frankfurt, Germany |
gru1 | sa-east-1 | São Paulo, Brazil |
iad1 | us-east-1 | Washington, D.C., USA |
pdx1 | us-west-2 | Portland, USA |
sfo1 | us-west-1 | San Francisco, USA |
sin1 | ap-southeast-1 | Singapore |
syd1 | ap-southeast-2 | Sydney, Australia |
Vercel KV is a first-party integration with Upstash. Supported regions for Vercel KV correspond to Upstash's available regions. We recommend selecting the same regions for your store as your Edge and Serverless Functions.
See what Redis commands we support in our Redis Compatibility docs.
During public beta, Vercel KV is not SOC 2 Type 2. We are working with Upstash on achieving compliance. Outside of Vercel KV and Postgres in public beta, all other Vercel products are SOC 2 Type 2 compliant.
When you create a Vercel KV store, a Redis store is provisioned with support for TLS v1.2 and v1.3 enabled. There is no way to disable TLS for your KV store.