---
title: "Edge Redirects with Upstash"
description: "Redirect from a list of redirects both hardcoded and coming from Upstash (Redis), that get evaluated at the edge."
url: "https://vercel.com/templates/next.js/edge-redirects-upstash"
links:
  repository: "https://github.com/vercel/examples/tree/main/edge-middleware/redirects-upstash"
  demo: "https://edge-functions-redirects-upstash.vercel.app"
  deploy: "https://vercel.com/new/clone?demo-title=Edge+Redirects+with+Upstash&demo-description=Redirect+from+a+list+of+redirects+both+hardcoded+and+coming+from+Upstash+%28Redis%29%2C+that+get+evaluated+at+the+edge.&demo-url=https%3A%2F%2Fedge-functions-redirects-upstash.vercel.app&project-name=redirects-upstash&repository-name=redirects-upstash&repository-url=https%3A%2F%2Fgithub.com%2Fvercel%2Fexamples%2Ftree%2Fmain%2Fedge-middleware%2Fredirects-upstash&env=UPSTASH_REST_API_DOMAIN%2CUPSTASH_REST_API_TOKEN%2CUPSTASH_EDGE_API_DOMAIN%2CUPSTASH_EDGE_API_TOKEN&demo-image=%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2F1okd1PXB7PcCLPpZEMIfqY%2Fc269766ddd869c7d604f934b7b1861d9%2Fedge-functions-redirects-upstash.vercel.app_.png"
---

# Edge Redirects with Upstash

Redirect from a list of redirects both hardcoded and coming from Upstash (Redis), that get evaluated at the edge.

# Edge Redirects with Upstash

This demo features a list of redirects, both hardcoded and coming from Redis ([Upstash](https://upstash.com/)), that get evaluated at the edge.

The demo has a total of 10,000 redirects, 1,000 of which are hardcoded on a JSON file, and 9,000 added to Redis.

Redirects in a JSON file are faster to evaluate, but they can only be edited at build time, with Redis we can have editable redirects with a low latency cost.

## Demo

https://edge-functions-redirects-upstash.vercel.app

## How to Use

You can choose from one of the following two methods to use this repository:

### One-Click Deploy

Deploy the example using [Vercel](https://vercel.com?utm_source=github&utm_medium=readme):

[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https://github.com/vercel/examples/tree/main/edge-middleware/redirects-upstash&env=UPSTASH_REST_API_DOMAIN,UPSTASH_REST_API_TOKEN,&project-name=redirects-upstash&repository-name=redirects-upstash)

### Clone and Deploy

Execute [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app) with [npm](https://docs.npmjs.com/cli/init) or [Yarn](https://yarnpkg.com/lang/en/docs/cli/create/) to bootstrap the example:

```bash
pnpm create next-app --example https://github.com/vercel/examples/tree/main/edge-middleware/redirects-upstash redirects-upstash
```

You'll need to have an account with [Upstash](https://upstash.com/). Once that's done, copy the `.env.example` file in this directory to `.env.local` (which will be ignored by Git):

```bash
cp .env.example .env.local
```

Then open `.env.local` and set the environment variables to match the REST API and Edge API of your database. It should look like this:

```bash
# Upstash REST API
UPSTASH_REST_API_DOMAIN = "us1-shiny-firefly-12345.upstash.io"
UPSTASH_REST_API_TOKEN = "your-api-token"
```

We populate the redirects in Upstash in [scripts/upstash.js](https://github.com/vercel/examples/tree/main/edge-middleware/redirects-upstash/scripts/upstash.js) using their REST API, if you prefer not to do that then set `POPULATE_REDIS` to `false` in `.env`. JSON redirects are also created there.

Next, run Next.js in development mode:

```bash
pnpm dev
```

Deploy it to the cloud with [Vercel](https://vercel.com/new?utm_source=github&utm_medium=readme&utm_campaign=edge-middleware-eap) ([Documentation](https://nextjs.org/docs/deployment)).

## Related Templates

### [i18n in Edge Middleware](https://vercel.com/templates/next.js/edge-functions-i18n)

This template shows how to redirect users based on i18n configuration.

---

## Additional documentation

The [Vercel Knowledge Base](https://vercel.com/kb) contains guides and answers to common questions about Vercel, including deployment, framework configuration, domains, caching, and troubleshooting.