Quick Start with Varity Docs

Varity Team Core Contributors Updated June 2026

Three ways to get started. Pick the one that fits where you are today.

Migrate an existing app

You already have an app on Vercel. The migration tool moves it and deploys it.

Deploy your current repo

Already have code? Deploy directly from your project folder.

Build from scratch with AI tools

Using Claude Code or Cursor? Add the Varity MCP server and ask your AI tool to deploy.

---

Path 1: Migrate your existing app

If you already have a Next.js, React, Vue, Node.js, Python, Astro, Qwik, or Vite app on Vercel, this is the fastest path.

1. Install the CLI

   pipx install varitykit
   varitykit login

2. Migrate and deploy

   varitykit migrate --url https://github.com/username/my-app

   This clones your repository, removes any platform-specific code, and deploys your app to Varity. migrate always deploys with --hosting dynamic, so your app is live at https://my-app.varity.app/ when done. (Static-only projects deployed with varitykit app deploy live at https://varity.app/<name>/ instead.)

3. Preview before deploying (optional)

   varitykit migrate --url https://github.com/username/my-app --dry-run

   Shows exactly what will change without deploying anything.

Coming from Vercel?

The migration tool automatically removes vercel.json, @vercel/* packages, and Vercel-specific environment variable names. Everything is backed up to .vercel-migration-backup/ so you can roll back.

See the full Migration Guide for step-by-step details, rollback instructions, and troubleshooting.

---

Path 2: Deploy your current repo

If your project already runs locally, deploy it directly.

cd my-app
varitykit app deploy --repo-url https://github.com/you/my-app

Varity builds from your GitHub repository in the cloud (nothing is uploaded from your machine), so the project must be pushed to GitHub first. --repo-url is auto-detected inside a Git checkout that has a GitHub remote. Prebuilt containers deploy with --image, and certified apps with --template. Varity auto-detects the framework and hosting mode, then returns a live URL. Static sites live at https://varity.app/<app-name>/; dynamic apps live at https://<app-name>.varity.app/.

---

Path 3: Build from scratch with AI tools

If you are using Claude Code or Cursor, the Varity MCP server lets your AI tool handle the entire deploy with plain English.

1. Add the Varity MCP server

   Claude Code

   claude mcp add varity -- npx -y @varity-labs/mcp

   Cursor

   Add this to your Cursor MCP config (~/.cursor/mcp.json):

   {
     "mcpServers": {
       "varity": {
         "command": "npx",
         "args": ["-y", "@varity-labs/mcp"]
       }
     }
   }

2. Open your project and ask your AI tool to deploy

   Inside Claude Code or Cursor, with your project open:

   Deploy my app to Varity

   The MCP server detects your framework, builds your project, and deploys it automatically.

3. Your app is live

   Once the deploy finishes, your app is available at:

   https://varity.app/your-app-name/

First deploy?

The first deploy needs an API key. Create one in the developer portal under Settings > API keys (a payment method or starter credit is required), then ask your AI tool to “Log in to Varity with key <your key>”, or set VARITY_API_KEY in the MCP server’s environment.

---

Check status and view logs

After deploying, you can check on your app at any time.

With the MCP (inside Claude Code or Cursor):

Check the status of my Varity deployment
Show me the logs for my app

With the CLI:

varitykit app status

---

Supported frameworks

Framework	Type	Status
Next.js	Full-stack	Supported
React (Vite)	Static	Supported
Vue	Static	Supported
Express / Fastify / Nest / Koa / Hono	Server	Supported
FastAPI	Server	Supported
Django	Server	Supported
Flask	Server	Supported

---

Next Steps

• How Varity Works: Understand the full deployment flow
• Installation: Full setup guide for all tools
• Migration Guide: Detailed migration docs for Vercel apps

---

Need a starter project? Use your AI coding tool to scaffold app code first, then run varitykit app deploy or varity_deploy.