Sails.js vs Strapi

Sails.js is built with a focus on building real time communication apps such as chat or multiplayer games, so naturally it has Socket.io extremely well supported.

This could be a huge plus, if you prefer to build your apps using the Model View Controller architecture. Using Sails.js you'll find the task of separating the business logic from the user interface and keeping the interactions between them in a separate layer, extremely easy.

Exposes public JSON API for free. No additional routing to be defined. Makes it pretty easy to access data from anywhere.

Sails.js uses Waterline ORM at its backend which means you can store your data in any datastore that you like; all you have to do is make a change to the Waterline adapter, this will allow you to store your data in MySQL/Redis or any other kind of database.

Clear documentation and easy to understand. The file structure gives you a way to understand where you can start to develop when you encounter a new Sails project

Strapi comes with blueprints that let you create, read, update and delete your data. You also can paginate, sort and filter your results in a matter of seconds with simple but yet specific parameters.

Manage user settings, login, registration, groups and permissions on the fly. Strapi delivers all those essential features out-of-the-box.

Easy way to manage your application. This panel allows you to add/edit/delete entries for your APIs, manage your users, groups and permissions. In the future, it will be such as WordPress-like administration panel dedicated to your application.