My experience has been pretty good. I like how fast it is, how it enforces immutable deploys and how user friendly the CLI is.

The only thing I stumbled upon is that deploys start to sleep after ~1 hour of inactivity. This is, of course, a great way to save unnecessary applications from running. However, it means that when you 'wake' a deploy up by sending a new request, it can take up to 30 seconds to get a response.

For production sites that's simply unacceptable.

One way to solve this problem is by running a cronjob on a different server that performs an HTTP request every hour, to keep the deploy running. Which isn't really elegant in my opinion.

TL;DR; It's great for quick prototyping, but I wouldn't use it in production.

I'm a bit late to the party but our experience with Now:

Great concept for microservices, definitely something you should strive for.

But.. the hosting itself... constant outages, problems and issues at least once a month.

A few times there were like half-day long outages.

Once I've tried deploying apps and completely random websites started popping up on the deployment URLs. Imagine you deploy an update to your client's website and there's a porn site instead suddenly.. shivers.

Trying to get help from their support team usually starts okay but you will be lucky if they ever actually get back to you or admit they have a problem.

All in all - great for experimenting, maybe take an inspiration from the way they do things, but definitely don't use with important live apps.

Never heard of it, from looking at the site doesn't look like ANYTHING I would EVER do in the environments in which I use JavaScript in the first place as it's all goofy stuff that has NO business on websites if you care in the slightest about meeting accessibility minimums.

Though admittedly, flipping the bird at usability and accessibility seems to be what's hot and trendy right now.