Zeit Now Tutorial

Dream of running a solo Internet business? check out SOLO LAB

Find out how to use the Now platform created by Zeit

Zeit is now called Vercel, and this tutorial might be outdated

One of the most simple ways to deploy a Node.js application is through the Now platform created by Zeit.

Now 2 was recently launched. This tutorials focuses on that. There are many differences from Now 1, highlighted in this post.

Now makes the deployment and distribution step of an app very, very simple and fast. You can think of it as the “cloud”, as you don’t really know where your app will be deployed, but you know that you will have a URL where you can reach it.

You can use Now to deploy Node.js apps, Static Websites, and much more.

Now does not only support Node.js (also Go, PHP, Python and other languages), but in this tutorial I’ll just consider this technology.

Now is free to start using, with generous free plan that includes free SSL, 100GB of hosting, 1000 serverless functions invocations per day, 1000 builds per month, 100GB of bandwidth per month, and the use of the global CDN. The pricing page helps get an idea of the costs if you need more.


The best way is to install Now Desktop, which you can download from https://github.com/zeit/now-desktop. It’s an Electron application which also installs the Now CLI, a tool we’ll later use.

Through that, you can deploy applications using a simple drag and drop interface, really handy!

Tip: you can also just install the command line if you prefer, from https://zeit.co/download

After starting, enter your email and Now will go on with the authentication, sending you a verification email.

Once you are signed in, you can follow the quick tutorial:

After you scroll through the few screens, the app is moved to the menu bar, and you when you click it, shows the activity feed:

As you can see in this image, I installed Now a few months back with that email account, but didn’t do much on it.

After signing in with the desktop application, the command line application called now is automatically signed in as well.

Jump into the terminal, and run now.

Tip: if you don’t need/want the desktop client, you can also just install the now CLI using the command npm install -g now. Then, you’ll proceed to login using now login.

Deploying an application on Now

For “application” we can just think about a simple HTML file, or a complex application with many build steps.

Whatever your app is, you can run


in a folder, and that folder will be uploaded to the cloud.

With just one caveat: the folder must contains a now.json file with (at least) this content:

  "version": 2

to make sure the projects runs on Now 2.

Once you run the now program, the app is deployed to a random URL under the now.sh domain. In this case, it’s https://test-8h57iozp1.now.sh and I just deployed an index.html file with <p>test</p> in its content:

After the deploy, the Now Desktop app lists this activity

If you now change that index.html file content and run again now, you’ll get a different URL for your app.

This might be unexpected, right? Before it was test-8h57iozp1.now.sh, now it’s test-m2vcwrsc8.now.sh. And both URLs can be accessed. Why?

The expected behavior should be that the old URL is updated with the new content, but it’s not.

Now has this concept of immutability that has many advantages, including the option of testing multiple releases at the same time, multiple developers working on different parts of an app, rollbacks, and more.

In production, or when you want to share your app, you need a fixed URL. It can’t change every time you update it, right? To do this, you create an alias:

now alias test-m2vcwrsc8.now.sh test-flavio

After you run this command, test-flavio.now.sh will point to that deploy.

Every time you want to update the deploy this alias points to, you run the command again. In this way you can freely test drive new releases, and when you are ok with making it the official one, you update the alias.

Same thing to rollback to a previous deploy, you just alias to the old deploy unique URL.

To remove a deployment, run now rm <URL>:

now rm test-m2vcwrsc8.now.sh

Configure a lambda function

We can execute a Node.js application on demand when visiting a particular URL.

For example add a test.js file with this content:

module.exports = (req, res) => {

In order to make it executable, we must add a build step to now.json:

  "version": 2,
  "builds": [{ "src": "test.js", "use": "@now/node" }]

Head to https://test-a0onzajf4.now.sh/test.js to see the result (“Hi!“)

The curious thing is that now the index.html file does not load any more like before. This is because the default build step is overwritten, so we need to add one to fix this:

Add the line { "src": "index.html", "use": "@now/static" } to our build:

  "version": 2,
  "builds": [
      "src": "test.js",
      "use": "@now/node"
      "src": "index.html",
      "use": "@now/static"

Where to go from here

There’s lots more to find out about Now, but this tutorial will hopefully get you started in the right direction.

Some useful resources for you are