For us, as a non-profit organization with limited funds, Strapi offers one of the best solutions on the market when it comes to headless CMS: - It’s easy to install and configure - It can be deployed to a PaaS (e.g., Heroku) such that we don’t have to deal with the runtime environment, OS and so on - We keep complete control over UI, extensions, data, and models - Maximum flexibility through extensions, i.e., use the HTML editor of your choice - It is open source - Excellent documentation—most questions have been asked and answered before - GraphQL API (it’s an extension)
Unfortunately, this highest flexibility comes at a cost: We have to install, deploy, and test it ourselves, but Strapi is about to launch the Strapi Cloud bringing this flexibility to a SaaS. So don’t take this dislike too serious.
We are developing new projects on a modern tech stack, e.g. with NextJS. Thus, we heavily rely on a predictable and potent API. With Strapi, we can decide whether to consume REST or GraphQL—both work well. Editors get a fantastic user experience with components in models, the media manager, and the navigation extension for drawing the site’s/menu structure.
Best for CMS API. Looks great for the future.
Frontend UI or plugins so it will reduce the development cost
Distribution of the content and api
Our team of developers are doing their best to make us feel comfortable using the back end of our game app. They were able to create a wizard for us ! I love that you, although the interface is intuitive, you can get help if needed. Thanks to Strapi you can keep things simple and functional for optimal results. My experience with this ongoing project has been really pleasant and user-friendly for every level of tech savyness ;)
Still learning but haven't had any bad experience so far, will update if we do with time.
Enables all the stakeholders (other non-for profits in different cities of BC, Canada) to be responsible for their part of the game and be able to upload and update their own content freely with no cost.
Strapi is easy to get up and running quickly, even for the most junior developer. Its total cost of ownership is down to earth, especially as nearly all SaaS alternatives are overpriced. It has a solid API and has no artificial predefined limits.
No sdks and new features develop slowly.
Needed a blazing fast content management system at a scale that WordPress chokes and SaaS Headless CMS providers demand an exuberant amount of money.
Easy to setup The simplicity and effectiveness in content building (mostly) open source Nice documentation Active community
Somes spécifics features need to be customized and are not well documented there is no completely free plan available (as the admin user is limited in the free version).
I am creating a platform for Non profit organisation, and Strapi allows us to develop a front end easily and at low cost.
Strapi is an awesome product for quickly setting up CMS and API for your products. We started working with Strapi in Dec 2020. Since then, we have used Strapi in three of our projects. Basic things like Rate Limiting, Authentication, Roles and Permissions are pre-built into Strapi. If you know Strapi, you can set up your fully functional E-Commerce store in a day.
There are some technical issues that I am confident would be fixed in the next major release. One that comes to my mind is that context is not available in lifecycle hooks. Another thing I would want the Strapi team to consider is to make Strapi on Serverless environments. Also reducing the size of node modules can help a lot.
Setting up CMS for non-technical users was one of the biggest issues for our firm. It would cost our clients a lot of money, training sessions and time. After using Strapi, the cost is less, fewer frustrations and happy clients.
Very easy to adopt, wonderful client service and good pricing.
Not the easiest to customize, according to our dev team, but gave us a lot of the major stuff we needed out of the box
Quick time to production. It would've taken us much longer without it
I really enjoy how easy Strapi is. You can build complex APIs including relation, automatic slug, field assertions and so on. You can also define multiple roles and give different read / write / update / delete conditions for each of these roles. You can also give more complex permissions with just a click like "a user can update a resource only if he created it".
Roles management for community edition is quite restrictive. It may not be an issue with other editions but I couldn't try it at this time. Anyway, pricing are quite expensive for small companies.
At the time I write these lines, I've only used Strapi for local development. But it really helped me to develop faster. I used to develop my APIs from scratch.