Migrate from Vercel to your own servers
Run your Next.js app or static site on Tenkai with its environment variables, cron jobs and database, step by step.
Last verified on 2 November 2026 against Vercel's documentation. Report a mistake.
Your Next.js app, its API routes and its background work run together on a cluster of servers you own, next to the database they use. Tenkai runs your app's standalone server as a long-lived Node.js process. It charges your team one price, whatever the number of apps.
What each part becomes
| On Vercel | On Tenkai |
|---|---|
| Next.js project | Web application running its standalone server |
Project with output: 'export' |
Static site |
| Environment variables | Variables |
Cron Jobs in vercel.json |
Scheduled jobs |
| Postgres from the Marketplace, such as Neon | PostgreSQL |
| Redis from the Marketplace, such as Upstash | Redis® or Valkey |
| Vercel Blob | Hosted bucket |
| Preview deployments | Pull request previews |
| Domains | Custom domains |
Before you start
You need a cluster with a project on it, as projects and clusters explains. Your CI builds your app's image, as Vercel did, so the cluster needs no Git builds.
Move your app
- Build the image in your CI. Set
output: 'standalone'and add the Dockerfile of the Next.js guide. Then add the workflow that publishes an image to GHCR on each push, and give it theNEXT_PUBLIC_values thatnext buildreads. - Create the web application. Add a web application, choose Container image and enter your image, such as
ghcr.io/acme/app:main. - Copy the variables. Run
vercel env pull --environment=production .env.verceland paste the lines your server reads in the project's Variables with Edit as .env…. Vercel writes a placeholder for each Secret variable, so put in its real value. Leave out theVERCEL_lines and the URLs of the databases you move, because a binding gives them. - Copy your database. Stop the writes. Add a PostgreSQL, choose From database under Initial data and paste your provider's direct connection URL, such as Neon's
DATABASE_URL_UNPOOLED. - Bind the databases. Bind the PostgreSQL to the application with the name your code reads. For Redis, add a Redis® and bind it, so the app receives
REDIS_URL. The new store starts empty, so sessions and other Redis data start over. Code that uses@upstash/redisor@vercel/kvtalks HTTP to Upstash, so switch it to a client that readsREDIS_URL, such asioredis. - Move the cron jobs. Vercel calls the
pathof each cron job. Add a scheduled job with the same schedule, because both read cron in UTC. Run it from the imagecurlimages/curl, with an entrypoint such assh -c 'curl -fsS -H "Authorization: Bearer $CRON_SECRET" https://app.example.com/api/sync', and give it the sameCRON_SECRET. - Deploy and point your domain. Deploy the web application, then the scheduled jobs, and check the default address. Add each deploy hook to your workflow, as deploy from GitHub Actions explains. Then add your domain, replace Vercel's records with the one Tenkai shows and remove
cronsfromvercel.json.
Static exports and files
A project built with output: 'export' becomes a static site. Your CI sends its out folder through the site's deploy hook.
Files in Vercel Blob move to a hosted bucket. Download them with the list() of the Blob SDK and upload them under the same paths with an S3 client. The bucket has no public URL, so your app serves each file or gives a signed URL, as hosted buckets explain.
To run more than one replica, follow Next.js's self-hosting guide so they share one cache.
Sources
We read these pages on 2 November 2026.
- Vercel, vercel env and Secret environment variables
- Vercel, Cron Jobs and Managing Cron Jobs
- Vercel, Postgres, Redis and Storage
- Vercel, Adding a domain
- Next.js, Self-hosting and Static exports
Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd.
Something wrong in this guide?
Vercel and Tenkai both change, so a step can go out of date. If a command fails or a step does not match what you see, tell us at [email protected]. Once you have an account, you can also choose “Report a bug” in your user menu, as the account guide explains. We fix the guide and reply to you.