Grow on Vercel, pay more Grow on Varity, pay the same
More traffic moves a Vercel team up paid CDN tiers. A Varity app is priced by the resources you choose, so traffic alone doesn't change its bill. Connect your repository and Varity adapts your Vercel settings.
Breakout · 150M CDN requests a month
- Vercel Pro
- $320/mo
- Varity Scale
- $28/mo max
You keep $292 a month
Vercel ProVarity Scale
Migrate
Three steps in the Developer Portal
No new tools to learn. Connect the repository, check what Varity found, and deploy.
How app deployment works- Workload
- Source
- 3Configure & deploy
Use detected frontend settings
Repository settings. We'll adapt detected build and routing hints for this deployment.
Resources
No request, bandwidth or build-minute charges
Connect
Choose your GitHub repository and branch. Varity detects the framework and your vercel.json.
Review
Check the detected settings, add environment values and pick resources. You see the monthly maximum before you deploy.
Deploy
Select Deploy and verify, then open your Varity URL. Your code and Git history stay in GitHub.
What changes on your bill
Vercel Pro adds meters on top of a platform fee. A Varity application is priced by the resources you reserve, so more traffic alone doesn't change it.
| Vercel Pro | Varity application | |
|---|---|---|
| Plan | ||
| Monthly price | $20 platform fee with one deploying seat and $20 usage credit2 | $7 to $56 a month at most by size, prorated by the minute |
| Compute | Priced by active CPU, provisioned memory and invocations1 | The CPU and memory in your plan |
| Traffic | ||
| Requests | 1M CDN requests included, then higher flat-rate CDN tiers2 | No request meter |
| Data transfer | 1 TB included, then higher flat-rate CDN tiers2 | No ingress or egress meter |
| Builds | ||
| Build time | $0.007 per minute on Basic build machines1 | No build-minute meter |
| When traffic grows | Usage beyond the included allowances and credit is charged | Same price, unless you add resources, replicas or persistent storage |
- 1. Vercel pricing documentation, read 2026-09-23
- 2. Vercel Pro plan, read 2026-09-23
- 3. Vercel Flat Rate CDN, read 2026-09-25. The growth chart above counts the Pro fee plus the CDN tier for each request volume, without function compute, builds, seats or add-ons, against Varity Scale (2 vCPU · 4 GB).
Varity adapts the build
You bring what's yours
When your repository has Vercel settings, Varity rewrites them for a standard Node.js build. Your repository itself isn't changed.
Migrating from Vercel...
- vercel.json becomes moved to .vercel-migration-backup/
- next.config.js becomes output: 'standalone', images.unoptimized: true
- @vercel/analytics becomes removed with its <Analytics /> component
- POSTGRES_URL becomes DATABASE_URL
- KV_URL becomes REDIS_URL
Custom headers, redirects and rewrites were backed up. Re-add them if needed.
What you move yourself
Environment values
Add your secrets and settings in the Portal. They're encrypted and locked to your account.
Data and its clients
Replace @vercel/postgres, @vercel/kv and @vercel/blob with pg, Redis or S3-compatible storage before you deploy; the build removes those packages. Your data stays where it is until you move it.
Headers, redirects and rewrites
Rules in vercel.json are saved in the backup folder, not applied. Add the ones you need to next.config.js.
Edge routes
Routes built for the Edge Runtime run on Node.js. Test the ones that depend on edge-only behavior.
Cutover
Test first
Switch when you're ready
Your Vercel app keeps running the whole time. Customers only reach Varity after you move the domain.
1Deploy
Deploy from your repository and get a Varity URL
- Vercel
- Serving your domain
- Varity
- Test URL
2Test
Open the Varity URL. Check sign-in, data, uploads and the pages your customers use.
- Vercel
- Serving your domain
- Varity
- Test URL
3Switch
Point your domain at Varity once everything checks out
- Vercel
- Serving until the domain moves
- Varity
- Serving your domain
4Keep a way back
Leave the Vercel deployment in place until you're sure, so you can point the domain back
- Vercel
- Standing by
- Varity
- Serving your domain
Prefer your terminal or AI editor?
Preview the Vercel-specific changes in your own checkout, review the diff on a branch, then deploy. Nothing changes until you apply it.
New to the CLI? Install varitykit with Python 3.11 or later.
pipx install varitykitUse a local checkout of your repository. Previewing needs no deploy key; deploying requires a Varity account and deploy key.
See what needs to change
Run this inside your project folder. The CLI checks for Vercel-specific configuration, packages and local environment variables.
varitykit migrate --dry-runRead-only preview. No file changes and no deployment.
Read the report alongside the compatibility notes above. A scan is a starting point; it does not verify that every feature of your app will work.
Prefer your AI editor? Preview with Varity MCP.
Use the installed Varity MCP server in Cursor, Claude Code or another desktop editor. Supply your GitHub repository URL and request a dry run; the tool checks a temporary clone without deploying.
Use varity_migrate with the GitHub repository URL I provide and dry_run: true. Show the changes and warnings. Do not apply changes or deploy.
Keep dry_run set to true for this preview. The tool’s default mode applies changes and deploys.
Set up your editorChanged your mind? Run varitykit migrate rollback in your project folder to restore the backed-up files. It doesn't undo a deployment, a domain change or a database move.
Run it on Varity next to Vercel, switch when it's proven
Connect GitHubCompare Varity and Vercel3 static sites free, no card · $5 starter credit for apps, payment method required, 14 days