Difference between MEAN.js and MEAN.io


Mean.js is a fork of Mean.io and both initiatives were started by the same person... Mean.io is now under the umbrella of the company Linnovate and looks like the guy (Amos Haviv) stopped his collaboration with MEAN.io and started Mean.js.


  • SCAFFOLDING AND BOILERPLATE GENERATIONMean.io uses a custom cli tool named 'mean'
    Mean.js uses Yeoman Generators
  • MODULARITYMean.io uses a more self-contained node packages modularity with client and server files inside the modules.
    Mean.js uses modules just in the front-end (for angular), and connects them with Express. Although they were working on vertical modules as well...
  • BUILD SYSTEMMean.io has recently moved to gulp
    Mean.js uses grunt
  • DEPLOYMENTBoth have Dockerfiles in their respective repos, and Mean.io has one-click install on Google Compute Engine, while Mean.js can also be deployed with one-click install on Digital Ocean.
  • DOCUMENTATIONMean.io has ok docs
    Mean.js has AWESOME docs
  • COMMUNITYMean.io has a bigger community since it was the original boilerplate
    Mean.js has less momentum but steady growth
  • On a personal level, I like more the philosophy and openness of MeanJS and more the traction and modules/packages approach of MeanIO. Both are nice, and you'll end probably modifying them, so you can't really go wrong picking one or the other. Just take them as starting point and as a learning exercise.

The nice things about both mean.io and mean.js code is that they come with Bootstrap integration. They also come with Facebook, Github, Linkedin etc authentication through PassportJs and an example of a model (Article) on the backend on MongoDB that sync with the frontend model with AngularJS.

AS per user experience(Chris Cinelli)

First of all, MEAN stands for MongoDB, Express, Angular and Node.js. It generically identifies the combined used of these technologies. There is no such a thing as "THE MEAN framework".

Lior Kesos at Linnovate took advantage of this confusion. He bought the domain MEAN.io and put some code at https://github.com/linnovate/mean

They luckily received a lot of publicity. In the Internet lately there are more and more articles and video about MEAN. When you Google "mean framework" mean.io is the first in the list.

Unfortunately the code at https://github.com/linnovate/mean seemed poorly engineered. In February I felt in the trap. The site mean.io had a catchy design and the Github repo had 1000+ stars. The idea of questioning the quality did not even pass through my mind. I started experimenting with it but it did not take too long to stumble in things that were not working and puzzling pieces of code. The commit history was also pretty concerning. They reengineered the code and directory structure multiple times and merging the new changes is too time consuming.

The nice things about both mean.io and mean.js code is that they come with Bootstrap integration. They also come with Facebook, Github, Linkedin etc authentication through PassportJs and an example of a model (Article) on the backend on MongoDB that sync with the frontend model with AngularJS.

According to Linnovate's website:

Linnovate is the leading Open Source company in Israel, with the most experienced team in the country, dedicated to the creation of high-end open source solutions. Linnovate is the only company in Israel which gives an A-Z services for enterprises for building and maintaining their next web project. From the website it looks like that their core skill set is Drupal (a PHP content management system) and only lately they started using Node.js and AngularJS.

Lately I was reading the Mean.js Blog and things became clearer. My understanding is that the main Javascript developer (Amos Haviv) left Linnovate to work on Mean.js leaving MEAN.io project with people that are novice Node.js developers that are slowing understanding how things are supposed to work.

TRy to use MEAN.JS