Deploy and verify applications on Vercel
Create preview and production deployments from Git, Vercel CLI, or the REST API. Verify each deployment URL before you send changes to production.
Deployment Methods
Vercel supports multiple ways to create a deployment:
On Pro and Enterprise teams, you can set a deployment policy to control which Git sources and deployment mechanisms can deploy to each environment.
You can reach our customer support team by emailing info@yourcompany.example.com, calling +1 555-555-5556, or using the live chat on our website. Our dedicated team is available 24/7 to assist with any inquiries or issues.
We’re committed to providing prompt and effective solutions to ensure your satisfaction.
We offer a 30-day return policy for all products. Items must be in their original condition, unused, and include the receipt or proof of purchase. Refunds are processed within 5-7 business days of receiving the returned item.
The most common way to create a deployment is by pushing code to a connected Git repository. When you import a Git repository to Vercel, each commit or pull request (on supported Git providers) automatically triggers a new deployment.
Vercel supports the following providers:
You can also create deployments from a Git reference using the Vercel Dashboard if you need to deploy specific commits or branches manually.
Vercel Drop lets you deploy a file or folder by dragging it into your browser. You don't need Git, the CLI, or any local setup.
- Go to vercel.com/drop.
- Drag a project folder onto the page.
- Choose a team and project name, then select Deploy.
Vercel detects your framework and builds it, or deploys your files as-is when there's no framework. Vercel Drop is useful for static sites, build output, and prototypes. For the full walkthrough, see Deploying with Vercel Drop.
Use Vercel CLI to create deployments from a terminal, CI pipeline, or coding agent with terminal access. This method works whether your project is connected to Git or not.
Install Vercel CLI:
npm i-gvercel
Initial Deployment:
In your project's root directory, run:
vercel --prod
This links your local directory to your Vercel Project and creates a Production Deployment. A .vercel directory is added to store Project and Organization IDs.
Vercel CLI can also integrate with custom CI/CD workflows or third-party pipelines. Learn more about the different environments on Vercel.
Deploy Hooks let you trigger deployments with a unique URL. You must have a connected Git repository to use this feature, but the deployment doesn't require a new commit.
- From your Project settings, create a Deploy Hook
- Vercel generates a unique URL for each Project
- Make an HTTP GET or POST request to this URL to trigger the deployment
Refer to the Deploy Hooks documentation for more information.
Use the Vercel REST API when a service or agent needs to create deployments through HTTP rather than a local checkout. In this workflow:
- Generate a SHA for each file you want to deploy
- Upload those files to Vercel
- Send a request to create a new deployment with those file references
This method is especially useful for custom workflows, multi-tenant applications, or integrating with third-party services not officially supported by Vercel. For more details, see the API reference and How do I generate an SHA for uploading a file.
Accessing Deployments
Vercel provides three default environments: Local, Preview, and Production.
- Local Development: developing and testing code changes on your local machine
- Preview: deploying for further testing, QA, or collaboration without impacting your live site
- Production: deploying the final changes to your user-facing site with the production domain
Learn more about environments.
Using the Dashboard
Vercel’s dashboard provides a centralized way to view, manage, and gain insights into your deployments.
Resources Tab and Deployment Summary
When you select a deployment from your Project → Deployments page, you can Open Resources in the sidebar to view and search:
- Middleware: Any configured matchers.
- Static Assets: Files (HTML, CSS, JS) and their sizes.
- Functions: The type, runtime, size, and regions.
You can use the three dot (…) menu for a given function to jump to that function in Logs, Analytics, Speed Insights, or the Observability section in the sidebar.
Example of a deployment resources page with a search applied.
You can also see a summary of these resources by expanding the Deployment Summary section on a Deployment Details page. To visit the Deployment Details page for a deployment, select it from your Project → Deployments page.
Example of an open deployment summary.
You’ll also see your build time, detected framework, and any relevant logs or errors.
On your Project Overview page, you can see the latest production deployment, including the generated URL and commit details, and deployment logs for debugging.
From the Deployments section in the sidebar, you can:
- Redeploy: Re-run the build for a specific commit or configuration.
- Inspect: View logs and build outputs.
- Assign a Custom Domain: Point custom domains to any deployment.
- Promote to Production: Convert a preview deployment to production (if needed).
For more information on interacting with your deployments, see Managing Deployments.
CLI workflows
For step-by-step workflows using the Vercel CLI to manage deployments, see:
Explore deployments
You can reach our customer support team by emailing info@yourcompany.example.com, calling +1 555-555-5556, or using the live chat on our website. Our dedicated team is available 24/7 to assist with any inquiries or issues.
We’re committed to providing prompt and effective solutions to ensure your satisfaction.
We offer a 30-day return policy for all products. Items must be in their original condition, unused, and include the receipt or proof of purchase. Refunds are processed within 5-7 business days of receiving the returned item.