I don't get it. There is the "meteor bundle" command, which as far as I can tell does the exact same thing. "meteor bundle" turns your Meteor app into a regular Node.js app. It does not bundle Node.js itself and it does not bundle MongoDB.

The author mentioned that Demeteorizer allows a Meteor app to be able to run on any Node.js hosting provider. "meteor bundle" does that too. In last week's announcement about the Phusion Passenger app server + Meteor support, I documented how one can use Meteor bundles with Passenger. If you look at the instructions[1] you'll see that the instructions for deploying a Meteor bundle are the same as deploying a Node.js app.

So how is Demeteorizer different from "meteor bundle"?

[1] http://tinyurl.com/mj9ex3y

As pointed out by another user, I was annoyed as you reading the article, but the script can be used outside of their PaaS and the source is on Github [0], even though the author did not link to the repo. Typically, I have noticed the prevalence of Github and free repo hosting means people link less and less, and expect you to auto-magically find their code via Google search, or by just clicking one of the social buttons (even though the nerdier you are, the more you hate them and refuse to use them).

[0]https://github.com/onmodulus/demeteorizer

I think the author was only talking about how to make Meteor scale on any hosting service by making it into a raw node.js app, something that more people have experience scaling. The NPM package demeteorizer, which was written by the modulus team, can actually be used to turn any meteor app to a core node.js package, which can then be hosted as you would any other node.js apps and can use any node.js hosting service (nodejitsu, heroku, appfog, modulus.io) or roll your own on bare metal (dedicated/aws).