When comparing Strapi vs Squidex, the Slant community recommends Strapi for most people. In the question“What are the best open source headless CMS's?” Strapi is ranked 1st while Squidex is ranked 17th. The most important reason people chose Strapi is:
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.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Auto-generate REST APIs
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.
Pro Users, groups and permissions
Manage user settings, login, registration, groups and permissions on the fly. Strapi delivers all those essential features out-of-the-box.
Pro Out-of-the-box administration panel
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.
Pro Open source
Pro Versioning
Pro Powerful rule engine for integrations
Pro REST and GraphQL
Pro Slick UI
Pro Generous free package
2 locales, 2 collaborators, many API calls
Cons
Con Limited to SImple Content
Limited to simple displaying of contents but will struggle with complex business rules ie ones that require cascading drop-downs, complex nested documents, etc..
Con Un-debuggable Script Editors
You can't debug any of its in-built script editors
Con References
It will allow you to delete references which are used by documents and when you come to open those documents, it will then perform its 'shake' logic to remove it (make it balnk') and will also disappear from history / versioning