When comparing GitLab Pages vs ZEIT Now, the Slant community recommends GitLab Pages for most people. In the question“What are the best website hosting providers?” GitLab Pages is ranked 2nd while ZEIT Now is ranked 13th. The most important reason people chose GitLab Pages is:
Gitlab pages are quick and simple to setup, with [documentation](http://doc.gitlab.com/ee/pages/) that's short and fast to read through.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy to setup
Gitlab pages are quick and simple to setup, with documentation that's short and fast to read through.
Pro Regular updates
GitLab is being constantly worked on and has a new release every month.
Pro Free private repositories
On gitlab.com you can have free private repositories.
Pro Open Source
Unlike BitBucket or GitHub, GitLab itself is Open Source. Even EE (which is needed for pages, but is free on Gitlab.com) is "source available".
Pro Deployments via a simple command line command
Installing their CLI and calling "now" inside your project's root will automatically build your project, whether it may be a Node.js or a Docker app , or maybe a static website, it works on the platform.
Pro Custom domain support
ZEIT Now supports custom domains, if that doesn't ring your bell, they also allow you to buy a domain directly from ZEIT, and even from the CLI.
Pro From the developers of Hyper Terminal and Next.js
The renowned developers of the Hyper Terminal and Framework for React applications develops and maintains this platform.
Pro Good support
You can talk to the staff anytime via their slack real-time, or mail them. They provide good assistance and will help you on any questions or issues on the platform.
Pro In-depth documentation
The documentation is very in-depth and can help you understand on how to make your application work on the platform.
Cons
Con Docker builds can only execute at the CMD Layer
ZEIT Now executes everything using docker run, so whatever was defined in the CMD Layer, is what will ZEIT will only execute.
Con Node.js apps has no access to the instance's filesystem
Once the Node.js build has completed, the only accessible directory is /tmp, which makes any file operation impossible outside the /tmp directory.
Con Free plan makes your code public
Unless you upgrade to a paid plan, the source code can be easily viewed by others.