Goodbye Sails.js — Thanks for the Ride

In 2025, we finally made the call — Sails.js is out of our stack. We’ve used it for nearly 10 years. Back in the day, it was great — built-in ORM, auto-generated APIs, solid project structure. It helped us a lot, especially around 2016. But times have changed. We tried hard to keep Sails alive. We added TypeScript, wrote custom types, wrapped controllers, hacked the models, and even considered forking it to modernize the whole thing. But the deeper we went, the more obvious it became — the foundation just isn't made for today. Outdated patterns, broken dependencies, Docker images with critical vulnerabilities... The project is barely maintained — just version bumps for security. It’s no longer a tool for modern development. Our main project today is RestoApp — an open-source platform for restaurants, food delivery, and retail. It includes everything:

May 16, 2025 - 09:48

In 2025, we finally made the call — Sails.js is out of our stack.
We’ve used it for nearly 10 years. Back in the day, it was great — built-in ORM, auto-generated APIs, solid project structure. It helped us a lot, especially around 2016.
But times have changed.

We tried hard to keep Sails alive. We added TypeScript, wrote custom types, wrapped controllers, hacked the models, and even considered forking it to modernize the whole thing. But the deeper we went, the more obvious it became — the foundation just isn't made for today. Outdated patterns, broken dependencies, Docker images with critical vulnerabilities... The project is barely maintained — just version bumps for security. It’s no longer a tool for modern development.

Our main project today is RestoApp — an open-source platform for restaurants, food delivery, and retail.
It includes everything: