How Varity Deployments Work

Varity Team Core Contributors Updated June 2026

Varity takes a supported app input, prepares it for production hosting, returns a public URL, and gives you tools to manage the deployment afterward. This page is the lifecycle overview.

For the exact framework matrix, use Supported Frameworks. For the current beta boundary, use What You Can Deploy Today.

The Mental Model

Stage	What happens	Where to read next
Input	You provide source, a GitHub repo, dashboard settings, MCP request, or Docker image	Deploy Your App
Build	Varity builds supported source projects or pulls a runnable image	Supported Frameworks
Configure	Varity applies hosting, variables, services, and URL defaults	Deployment Defaults
Launch	Your app becomes available on its Varity URL	App URLs and Names
Operate	You use logs, status, environment updates, redeploy, and support	Troubleshooting Deploys

Deploy Lifecycle

Choose an input

Use a supported source project, GitHub repo, dashboard deploy, MCP request, or Docker or OCI HTTP service image.
Authenticate

Sign in through the CLI, Developer Portal, or MCP server. See Installation for setup details.
Deploy

Use the path that matches your workflow:
Terminal window
```
varitykit app deploy
```
Or ask your AI editor:
```
Deploy this app to Varity
```
Receive the live URL

Static apps use a varity.app/<name>/ path. Dynamic apps use a <name>.varity.app subdomain.
Operate the app

Check status and logs, update environment variables, redeploy under the same app name, or get support if the workload needs manual review.

What Varity Reads

Project files

Package manifests, Python requirements, Go modules, framework config, build output, and Docker image settings.

Deploy settings

App name, hosting mode, port, environment variables, image reference, and registry credentials when supplied.

Service hints

Database, cache, object storage, and model runtime dependencies that map to supported services.

Tool context

CLI flags, dashboard fields, or MCP tool arguments passed by your AI coding tool.

What Varity Returns

Every successful deploy returns the information you need to keep moving:

The public app URL
Deployment status
Logs and troubleshooting context
The fixed monthly price for that workload
Commands or MCP tools for redeploying and updating environment variables

Use CLI Reference and MCP Server for the exact command and tool names.

URL Shapes

App type	URL shape
Static site	`https://varity.app/<your-app>/`
Dynamic app	`https://<your-app>.varity.app/`

Varity chooses the default based on the app type. You can force the mode with --hosting static or --hosting dynamic when needed.

Current Product Boundary

Varity currently supports Node, Python, Go, static projects, and Docker or OCI HTTP service images. External custom domains, cron jobs, preview deployments, one click rollback, and dedicated GPUs for user containers are not shipped yet.