Introducing the Deploy Button

Authors

Share your custom templates as one-click deployments.

As the author of an open source project or framework, one of your key focuses is making it as easy as possible for users to get started with your creation.

With the help of today's feature release, you can now reduce this entire process down to the click of a single button: The Vercel Deploy Button.

What's new

To offer your users an easy way to deploy your code to production (and keep updating it afterward), you can now create your own Deploy Button.

After clicking "Deploy", you will be asked to confirm the destination and project name, under which a Next.js template from the Next.js examples list will be forked and deployed.

The interface for selecting the destination of your deployment.
The interface for selecting the destination of your deployment.

Creating Git repositories

You might also want to create a GitHub or GitLab repository. To accomplish this, you only need to select the "Create Git repository" option on the Deploy button flow.

The interface for creating a Git repository for your new project.
The interface for creating a Git repository for your new project.

We will automatically create the Git repository for you, once you click deploy, and push the source files of your freshly created deployment.

Get your own

Using the button for your own project is as easy as copying our default markdown snippet and replacing the URL of the Git repository:

[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/project?template=https://github.com/zeit/now-examples/tree/master/nextjs)

A button that deploys the `nextjs` directory of the zeit/now-examples repository.

For an example written in HTML, make sure to check out the feature's documentation.

Conclusion

Our Deploy Button lets your users easily deploy your code to Vercel.

It is ideal for scenarios where customers have not interacted with our platform before, but works just as well if they already have an account.

With this release, we hope to empower open source maintainers and enable faster deployment workflows for the people enjoying their creations.

Let us know what you think about this change!