Strapi Reviews: 4.6/5 — Highly Rated

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 offers a flexible platform that is built for builders. It offers functionalities that can be used in content-based projects, regardless of their size. It gives developers the ability to design their own content structure and even content type, define their workflow, and the interface to create and manage their data. It also offers a very robust API and set of tools that lets developers use that data in any form they need. All of that, with the speed and the option to choose your own database and tools, and the fact that it's all open-source,makes Strapi a very valuable tool for anyone who wants to do a content-based project.

I wish there was a hosted service which would let us use Strapi for smaller projects, without going through the hassle of setting up our own servers.

Without a tool like Strapi, content can easily get our of hand, from designing the structure to the workflow and access. Classic Content Management Systems are usually not as flexible and are slow. Headless Content Management Systems are usually not as flexible, and / or use proprietary technology, which make you dependent on them. Strapi brings structure and east content management, and it's open-source.

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

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.

Making an API service so easily and without much programming

Honestly there is nothing to say about this.

Reduce the time needed for development

I love that any admin can use the system to manage content

Nothing. Strapi works like a charm, totally recomment.

We are building a nonprofit campaign platform, where admins can manage content for public use.

I really love the fast prototyping and API creation. Im using the Jamstack architecture and works fine.

Missing dashboard customatization and adaptability

Im creating an ecommerce and educative platform

We love that Strapi is Omnipresent! our students can choose any Frontend Frameworks, Any RESTful or GraphQL, we can integrate it with everything! We have always seen strapi pomo interest to integrate it into our academic training curriculum but due to costs they were impossible for our students. Now that they arrive at our institution with the new Strapi Enterprise Bronze Edition plan for students, non-profit organizations and open source projects we can think about changing our academic curriculum and integrating Strapi into our courses and that our students are the beneficiaries of this great contribution from Strapi! Thank you!

We could say that allow to customize even more UI.

Our students in their training of the AWS Platform are adapting new stacks in their study curricula and now we can integrate JAMStack, Headless CMS with Strapi and we deploy in AWS we are complete to develop the new web of the future with them.

How easy it is to get started. You literally have a single CLI command, go through the process of setting up the connection to the database, and you're ready to work. From there, the UI/UX is great. During the development, it's important that prototying is FAST, which it is. The customization of views and data types is just the cherry on top. Support for GraphQL comes in form of a plugin that you install with a single click. That's it. Now you have GraphQL. In a single click. The documentation is automatically generates for your API is concise and to the point.

I'm waiting for out-of-the-box TypeScript support. It's planned, so I'm not worried. Sometimes, the UI shows an error when updating the component, even though the operation was successful. You just refresh the page and it works.

When you need to tinker around with the source, the official documentation has all the information written in a legible and concise way. At our company, we have created everything from custom views, modified the branding, colors, etc. To put it in perspective: we had a detailed plan on how our API should look like, and we knew what the CMS system needs to have. From start until we were able to deploy to testing phase, it took less than an hour. We created all the custom views and branding modifications, deployed to production in a single day.

I love the customisability of Strapi. I wrote a plugin for it by following a tutorial. it was easy enough!

I would've loved to have the ability to customise the UI a bit more

It enables me to write common APIs super fast so I can spend more time on UI

Almost 0 effort to set up and get started developing, UI is extensible if you need, and lots of easy ways to deploy

It could be easier to customize the UI, you've got to do quite a bit of coding to change things

I use strapi to organize and publish articles to my blog / portfolio

Simple Model creation with rules and GraphQL API

The user access (roles, right) for admin page and API is not easy to understand. I d'ont' kown if it should be the same managment (API = Admin would be more simple)

CRUD Backend is done in 1 day max now, before STRAPI it was 20 days

Simple setup and easy creation of a Rest API, with support for graphql and easy customization of the admin dashboard.

Internationalization functions are missing although they have it with the status In Progress (Design) in the Roadmap

It solves the management of the content of a project in an easy way, with a customization of all its parts. With features like self-hosted, agnostic database, plugins to fit projects needs, open-source and free.

1. Automatic GraphQL schema generation based on models created by the content-types builder 2. Lifecycle hooks

I cannot complain about Strapi because it's beyond my expectations and it's not easy to find any flaw in Strapi. However, I found Strapi doesn't support the subscription operation out of the box which is one of the key reasons I have chosen GraphQL. But I found a workaround and it works well seamlessly. So there's nothing I dislike.

I believe all of the business logic should be implemented at server side and the client application should focus UX/UI only. But it's easier said than done. When we realize that there's something wrong with our project and wish to refactor the source codes both on client- and server-side, we don't have much time left. However, with Strapi you can rewrite the APIs at anytime in a couple of days. That's actually what happened in my company. We've decided to re-do our work that had taken a year so far because we were assured that it would be much faster to deliver our product rather than to be stuck with spaghetti codes of previous work.

Strapi is in my opinion the best headless CMS currently because of its fast api development process and its flexibility.

At first I disliked a part of the policies when it come to customize it for custom controller's actions. I took some time to make it work how I wanted.

Strapi help me to fastly build some APIs to save time and money. It's an headless CMS but I use it for more than that, I use it for general APIs too.

Strapi came at the right time when I was looking for a way to build a custom and light-weight API driven Content Management System for my Project. I got started with few hours of watching tutorials and reading the documentation. It was a real life-saver. I've developed my CMS now and Frontend & Mobile Devs are already consuming the endpoints for production ready stage.

I could barely find a fault at the moment. What I would probably say is that switching between dev and production environments could be more seamless or maybe I just haven't gotten a hang of it.

One major cool thing about Strapi is also that its open source and self-hosted backed with growing community.

Strapi offers a rich set of features and defaults to develop first-class applications quickly. Strapi grapqhql API, components, unique types and json type fields set this product apart from its competitors.

The docker image for production overpasses 1GB

Saving development time building front-end applications

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.

Honestly just how easy it is to quickly start up your API and just start adding data. Going from basically nothing to a fully functional backend headless CMS in 5 to 10 minutes with not a single line of code is great!

Obviously new features take time, and the Strapi team is small. My main dislike actually has little to do with the team or product but the lack of outside contributors helping to make the project better.

I am using Strapi in a free and open source environment in a product that doesn't bring in any income, thus Strapi being free and open source was a huge benefit for us. Our API will be used by many other parties that need a solid standard query framework to pull our data, REST/GraphQL they both work great.

Strapi is very easy to get started . It is one of the best CMS . The documentation is very clear and easy to undersatnd. It is open source so continuously growing.

The deployment is kind of tricky for strapi. There should be much support in strapi.

We are using strapi for headless CMS. It helps us managing and adding data.

The best thing about Strapi is that it is quite user friendly and anyone with a moderate education making changes to the backend of a website can do it without the need for a developer.

There's not much to dislike about Strapi just that it can have more functionalities.

Strapi solved the problem of having a Headless CMS with a great interface for us to easily modify the content on the website that we developed.

Strapi is built on a solid open source community and is both forward looking (via things like GraphQL) and well-established standards (such as REST). The latest version is also beautiful and easy to use.

Strapi Cloud has been slow to release. When we initially ran into installation problems and looked into a hosted version, we were disappointed that it was not yet available.

Strapi makes it easy to define and use many-to-many data relationships. One of the main problems Strapi has solved for us is providing an easy way for non-technical writers to leverage a complex data model.

It gives a very robust and flexible ready-to-use API within minutes. In my previous organization, we had a project with a very tight deadline, and Strapi came to the rescue, all we had to do was configure a database schema on their dashboard, and boom, we were ready with very flexible CRUD, filtering, and pagination APIs for the backend. Also, the overall dev experience with Strapi was good!

Most of the things were above average, if you check the docker image it is one major version behind which might become an issue if you want to deploy the latest version with containers.

Strapi can be helpful for cases where a CMS fits, to make static/corporate websites, blogs, basic software with less scalability needs, etc. It can be used by developers and also the management team due to the clean dashboard provided.

Strapi helps us with the back-end solution. We want to develop a service with user authentication and a database. One possibility was to implement it from scratch, but then we got to the Strapi, which met all our needs. It provides an easy UI for creating DB and also for creating new users, roles, and also managing access rights. It is much simpler and safer for us to use Strapi than to implement this. It was super easy to install and very intuitive to start using. Also, DB schemas are clear, with no extra fields used by CMS itself.

Right now, we don't see a big downside to Strapi. We will see how hard it will be if we need to bend the code to our purposes. Till now, everything seems easy.

We want to build the service with back-end and front-end. It is much easier a safer to use Strapi than to implement the back-end by ourself.

Strapi has clear guidelines and is simple to use. It is very intuitive to design solutions, and as a headless CMS, it provides more functionality than any other CMS I have used.

The documentation that pertains to customisation can be made better. An Enhanced Rich content editor, as well as Support for a Greater Degree of Customization in Regards to WebHooks can further improve the experience.

I have a web application that I am managing the content of with the help of Strapi. We are relieved to be able to handle all of our content in a one location rather than across several different systems. The amount of time needed to construct solutions has decreased dramatically.

It just works! It's lightweight, extremely easy to set up, fast and highly customisable. We have built our application using Strapi together with NextJS and Postgres.

That granular permission control is not available in the free version of Strapi. This has been a slight hurdle when going to production for us.

We can finally decouple our data storage and management from our frontend. Wordpress is no longer needed. Instead, we have a beautiful NextJS/TailwindCSS application for our frontend.

Clean interface and power content type builder. Supports SQLite which makes it cheap to deploy to cloud

Lacks support for Microsoft SQL. Nothing else.

Saves a lot of time rather than implementing CRUD interfaces to all content pages of our website.

How quickly I was able to get up and running with secured REST endpoints

Nothing... so far. I build B2B SaaS products so I may grow to loathe the tax on Strapi's tier that offers SSO, as it's an essential feature to sell to the enterprise.

Strapi simplifies the effort to build a robust backend with its GUI tools to build out entities & generated code. Instead of spending weeks building the foundation to an application, I can bootstrap with Strapi and immediatly focus on the actual data entities and workflows.