Strapi Reviews & Product Details

Fully customizable, written entirely in JavaScript, vibrant community, tonnes of support. Additionally, I've observed Strapi grow, develop and ship new features at the speed of light! Which is not only encouraging and assuring but also inspiring!

Honestly, it's hard to think of anything that I dislike. Strapi has proven to enable the projects I work on to ship complex data structures and solve problems related to getting an early idea off the ground in record times! From the free and open-source projects, this is hands down the best one I've come across. They just rolled out Version 4 beta, which on top of all the awesome flexibility and functionality, also looks gorgeous! If you haven't yet, go check them out, you will most probably not regret it!

Shipping new features within a matter of hours, not weeks. Building my startup and helping clients to develop and ship features with little to no friction.

The administration UI makes DB architecture very straightforward, while at the same time Strapi exposes enough under the hood to remain highly extensible.

Any "magic wand" solutions always suffer the same problem; less transparency about the underlying low-level processes that are happening. Fortunately this has not been a huge drawback for me with Strapi.

I am currently using it as a way to enable customers to edit their own content, replacing older CMS solutions like Wordpress.

Combined with Dio HTTP cache in Flutter, Strapi has enabled us to build up an easy-to-manage app menu and content system, allowing us to make live changes in a beautiful UI without code changes and app releases.

Some documentation and answers to common questions are outdated for older versions, can cause some confusion.

The ready-made dashboard has saved us time and money. The HTTP API to insert data via scripts allows us to pull data from Podbean, Vimeo, Instagram etc in a draft state, allowing us to log in and publish new content.

The thing I like the best about Strapi is that it's open-source; this allows for complete flexibility in what you want the CMS to do. Content is easily accessible through REST API or GraphQL, which is fantastic!

The free version only comes with three roles which you can't customize. This is understandable because there needs to be an incentive to support the developers, and restricting features is the only way.

Quick solution to create an api and present a panel for people with no technical skills.

Fast API setup. Can build a production-ready cms real fast

Changing the admin page requires a lot of work

Having to set up a working graphql API in a short time with authentication. With Strapi, i can complete this task in a short time, and no need to worry about the reliability

The fact that all the APIs are created on the go, all methods on the APIs are all set. That is like a gold key to me

The time it takes to refresh after creating a collection, sometimes I have to restart the server on development

In time project delivery. Strapi gives hope to junior devs who'd love to experience what goes on in the backend.

The best part about Strapi is that I'm able to spin up a CMS in less than a minute. Yes, it really is that fast. Just a single quickstart command in the terminal and you're ready to build out your content structure for use in any project. When I explain Strapi to other developers, I usually tell them to think Wordpress Pages + Posts + Media + Custom Post Types + Advanced Custom Fields + Users, all rolleded into 1, easily accessible via API, without the parts that you don't need and with a better user experience. Strapi makes development so much quicker. No longer do I have to think about setting up, managing and interacting with databases. Instead, everything I would need a database for is now handled by Strapi. API endpoints for all of my data are generated automatically, making it easily consumable from any front end app. I love that Strapi is free and open-source, making it very easy to customise Strapi 'till your hearts content. The Strapi core team also work hard to push new updates and functionality while listening to and engaging with the community. It's the best of both worlds.

I might have once said that the UI could be a little less bland, but with Strapi version 4 just around the corner and the upcoming re-design they showed off, I'm just excited for the update. The only real issues I have with using Strapi aren't directly related to Strapu itself. The only slight problem I have is hosting Node apps in general due to the more complex requirements than what I'd been accustomed to. For example, there aren't a thousand companies offering easy to use 1-click installs like in the Wordpress world or easy push-to-git solutions you get in the javascript front end world. This, of course, makes hosting Strapi a little less intuitive for beginners. That being said, I know that the Strapi team is currently working on an in-house hosting solution, so I look forward to that.

Currently, I'm using Strapi in portfolio-type websites to manage page content and blogs, etc. I'm also using Strapi for business websites where I have to manage users and authentication. So far, I can't imagine there being many, if any, projects that Strapi wouldn't be great for.

It is 100% codeless. Creating custom content types and roles, giving permissions, creating APIs are very easy with the Strapi. Everything can be done using the admin panel. They have nice documentation as well.

The richtext editor has a limited number of functionalities. Better if can add more functionalities.

I am creating a blog publishing site and needed an admin panel for all the authors to add content.

- it recently supports Internationalization - the UI is beautiful - role management is very detailed and clear

- That there is no cloud service yet but it's now coming from what I saw!

- the non-dev team will be able to edit and add content, which will free their time to code real stuff - better interface overall, and scalable website.

Strapi allows me to build React apps with functionality that would require a backend about 10x faster than I would typically take me if I had to code a backend from scratch. It also provides so many extra features and is constantly being updated and improved.

If you upgrade Strapi versions and have customized the admin portal by overriding files, you can run into problems quickly but it's still doable!

The main benefit is quickly integrating a backend & database to my websites.

Strapi is one of the easiest, fastest headless CMS that I worked with; it is so easy to implement and start with excellent, fully described documentation that facilitates everything for everyone from senior to beginner,

The email functionalities are a bit buggy, but I guess that these bugs will be fixed shortly.

I'm using Strapi.io for my graduation project, which is a Smart Attendance Management System that uses a combination of MongoDB and Strapi to build the backend. It helped me a lot with providing my team with an easy-to-use backend UI that they can deal with and make changes on it,

The ability to generate a REST API very quickly through the Admin UI. Also, the option to easily extend policies, services and middleware programmatically. Strapi hits the sweet spot in terms of catering to both the end-user and developer.

I like to use Typescript in backend projects. Unfortunately, there is no support for Typescript currently. Also, I cannot hide selected collections easily in the admin UI based on user role/permissions. There are workarounds to accomplish this, though.

Building the backend to a booking system. Faster time to delivery.

One-click deploy to Heroku, Ease in configuration

Nothing as such. Its slightly slow to load on first time, otherwise quite good. There's very good customer support, so all problems are fixed immediately.

We've basically opened up our website for every kind of content writer. Previously all content had to go through the Webmaster, and not many have coding background. However, now all members can contribute with ease.

I like the fact that I can use it as a regular application. I can put CI/CD and deploy it on staging and production quickly, just like a typical application. Most importantly, Strapi has the slightest learning curve for us. This is important because we don't have enough capacity to train our developers. Strapi also quickly scaffolds all content models for us. This helps us to move fast without wasting time on building plugins for every minute feature.

It's good in every way currently and suits our needs best. There are minor issues, check https://github.com/strapi/strapi/issues for more details, but the team is excellent. I am hopeful that they fix them all. One feature I think would be useful is a way to export specific content using some filters from staging to production. Because content is core of any website. On large websites we cannot test content changes that effect UI, even though there are preview options available. I also miss block editor like wordpress.

We are building an extensive website with multiple forms and a lot of content, and we also have various author roles with access to multiple types of content. Most importantly we have a huge books database, which we want to manage and serve using Strapi. We also want to create events, collect donations and maintain a blog using strapi. Because strapi gives us huge control, its easier for us.

Strapi is the best fit for what our organization wants to do with it. We like the flexibility!

Nothing for now, we totally recommend Strapi.

We are creating an educative platform in French and English