Instant serverless Node.JS deployments with an API.

There are no images or videos added to the gallery.
Add to gallery



You need to become a Contributor to join the discussion - Find out how.
Guillermo RauchMaker@rauchg
Really happy to be sharing our latest product on PH! A little over a month ago we shared 𝚫now with the world ( The idea is simple: deploy any website, microservice or backend app with a single command. No knobs to adjust or twist. No instance types, process numbers, manual provisioning. It's highly optimized for Node.js and its build process and package manager (npm). Today I'm having to share with you our API. With a single JSON endpoint ( you can supply the metadata (package.json) and its code! This gives you the power of our infrastructure to not just host apps, but also run automatic build tasks, tests, or even write your own deployment tools with your own flavor. We want Now to power the JavaScript cloud. Let me know if you have any questions!
Jim Pick@jimpick · Co-founder/Engineer, Backblend
@rauchg This is really amazing stuff!
Ondrej Kubala@ondrejkubala · Full stack developer @QuickMonkeys
@rauchg This looks awesome!
This is an interesting concept, are you guys using AWS Lambda?
Guillermo RauchMaker@rauchg
@tehsuck No, and for more details I actually address this in the FAQ ( The bottom line is: the "cloud functions" approach will always require that you somehow expose them with an HTTP layer on top. If you're familiar with AWS, you can think of Now as Lambda + API Gateway, but without any of the proprietary terminology or code. What this means for you: if your `package.json` runs in your local computer and it has a `start` script that serves HTTP traffic, your application works with us. The kicker: we expose your traffic with HTTP/2 load-balancers, which means your client side applications (like mobile apps) will make highly efficient use of the network.
Andy Kay@datandyk · human
@rauchg I have been using 'now' for a little while now on small projects and I love it! Now I wan't to use it for a bigger startup-y like project and have two questions. Is 'now' mean't to be a platform that a potentially big product can be launched on? And is there a recommended cloud database provider to use along side 'now'? I was hoping to use Google's Datastore. I'm super excited about your product and I apologize if those are painfully obvious questions! Thanks for any info.
Guillermo RauchMaker@rauchg
@datandyk Absolutely. Our main focus is on scalability and geographical distribution, for which there are some amazing news and technical demonstrations coming. As far as the database provider, it very much depends on the specific needs of the application (or part of the application)!. As an example, if you need basic data manipulation and caching, Redis Labs is easy to set up, replicate, and they can collocate to many different locations.
Andy Kay@datandyk · human
@rauchg thanks so much! I plan on signing up for your premium plan soon. If you don't mind answering one more question: is there a way to make use of your 'micro' web framework on now? As in dynamically using multiple micro deploys for an internal API on now. Maybe your new mix API enables this?
Guillermo RauchMaker@rauchg
@datandyk at the moment, you can deploy each micro(1) API service independently. We'll soon blog about different ways of routing traffic to them from a single host, which will make your frontends more efficiently in terms of simultaneous HTTP connections.
Andy Kay@datandyk · human
@rauchg ok cool. Seriously amazing work. Thanks again!
Maxime Dehaye@mdcarter · Front-End Developer
@rauchg @datandyk any updates on this blog post ? =)
@rauchg Just tried 𝚫now and it is really cool! Any way for me to attach a custom domain name to my Now deployment?
Guillermo RauchMaker@rauchg
@fanghai44 we're introducing a new command for this called `alias`. Aliases accomplish two things in the context of now. One is obviously a memorable shortcut ( or But aliasing is also how zero-downtime deployments happen. Let's say you want to update the code of, which is pointing to a specific version of your site. You make changes, and you provision a new unique and different now URL. When you're done testing it or happy with where it's at (having received feedback from your team, for example), you then change the pointer of to the new version!
@rauchg fantastic. can't wait to try this out :)
Matt Coleman@mattcoleman · Designer / Dev
This is really great. Excited to see it can easily host static sites as well:
Guillermo RauchMaker@rauchg
@mattcoleman yep! The cool thing is `now-serve` is 100% independent of `now` as a codebase, and is open source ( This really shows the power of programmatic deployment / APIs!