The news that Xervo (formerly known as Modulus) is shutting down was announced today. We are thankful to the Xervo leadership team for choosing us as the provider for their customers to transition their production deployments to.

In this blog post we'll walk you through our migration plan to now. You'll learn in a few simple steps how to continue your online operations and resume deploying changes to your services and websites without any interruptions.

Welcome to now! Let's get started.


Migration Support

Before we continue, we know that migrating to a new service on short notice is a difficult and sometimes frustrating experience.

To avoid any hiccups in this process, we have a set up a channel #xervo in our Public Slack Community where you can find members of the team and other people from the community to answer any migration-related questions.


A Brief History of Now

We conceived now to be the simplest, fastest and most scalable deployment solution for websites and APIs.

All it takes to deploy is one command in a directory that contains a package.json,Dockerfile or just HTML files (for static hosting):

now

Your now deployments are immutable: every time you run now, you get a new unique URL (ending in .now.sh) for the source code and dependencies at that point in time.

When it's time to go to production, you run a now alias command as follows:

now alias my-deployment-url-2jf4h2jfh2.now.sh my-domain.com

For this to work, the only requirement is that you point my-domain.com to our nameservers.

We then take care of provisioning SSL certificates, load balancing, setting up DNS records, serving your content over HTTP/2 and much more.

With those two commands we have covered the basis of deploying for development, staging and production. All with the same model! To learn more about this philosophy, we recommend you read our Introduction Guide.

Make sure to visit our Documentation Center to learn in-depth about topics such as Secrets and Environment Variables and Microservice Composition.


Migrating Everything

If you were running Node.js projects or Docker containers in Xervo, you'll feel right at home pretty much instantly!

In the description above, we assumed that you deploy from scratch and then update your DNS settings to point to us. This could result in a small amount of downtime to your users while DNS propagate.

In many cases, however, you will want to transition with no downtime whatsoever. To that end, we have written up a Zero-Downtime Migration Guide to assist you in the process.

now specializes in a microservice-oriented, highly scalable and stateless model of computation. We don't persist any data on your behalf. There's no notion of volumes or databases.

If you were running your projects in Xervo using their database support, we recommend you transition to cloud providers such as DocumentDB or MongoDB Atlas.


The Now Way

Now was conceived to optimize iteration speed, minimizing barriers between product engineers and production.

We recommend checking out our guide to deploying microservices to learn how to use a function-oriented approach to defining your APIs, thanks to the open-source micro framework.

To get involved and learn more about our products and services, check out our Chat Community, Open-Source Projects and follow us on Twitter to stay on top of our news.