Strapi Reviews: 4.6/5 — Highly Rated

The easiness and flexibility to configure small proof-of-concepts or fullstack applications. Sometimes I just need a headless CMS for my client, sometimes I want the CMS and custom API responses. This is all possible with Strapi. Also connecting to services like RabbitMQ clusters is really easy and quick to do.

I've started using Typescript for a lot of my projects, but Strapi unfortunately doesn't support it currently. Also, I haven't been able to adjust the admin interface _exactly_ as I want it. But this is no showstopper for me.

Quickly developing backend solutions so I can quickly develop products or solutions. I was working on V2 of my API and also wanted a good CMS. After I learned about Strapi, I sticked with it for both the API and CMS part.

We tried multiple CMS systems and we can say without a doubt that Strapi is the best fit for what we wanted to do with it. It's fast, easy to install and configure.

The UI is great but the ability to customise it, even more, would be a huge advantage for our use case.

We are using the Strapi CMS to manage our school's lessons plans. It was really easy to install, setup and integrate and their documentation and support is great too.

With Strapi, making a CMS is way easier. Managing content and exposing as an API for a suitable frontend application has never been this easier. With the flexibility, it is much easier to work with a wide variety of popular Databases and Technologies.

Community edition has too many limitations.

Managing content for simple web applications. Easiness to understand and use.

The simplicity of having a ready API solution out of the box.

Need more customization options which are for power users.

Cuts down the development time of building and structuring APIs.

I like that we will be able to easily structure and build our course content and have the option to customize to our needs.

I don't like that you can't search between collection types.

It is giving us a customizable CMS that can be integrated with the other software solutions we use.

It's highly customizable, intuitive, and easy to use. There's also plenty of resources out there to help you do what you need to do.

Learning how things work can take some time.

It helps the writing team upload and modify website content.

It has lots of preconfigured customization which can be further customized to make it more useful according to your needs.

It becomes sometimes complex for beginners. It has too much available that become sometimes overwhelming in some scenarios.

Helpful in managing the backend of the jam stack website. It has lots of things premade that can be useful for development. We have a need for CMS that can be self-hosted and Starpi is a good choice for that.

Clear intuitive interface. Excellent collection of plugins. Define data structures in development mode and then enforce them in published versions. Landed itself wonderfully to dockerizing both in local development and production environment. Has GraphQL capability which accelerates development. Put Apollo Client on the other end and you are good to go. Also has a plugin to output all the TypeScript types for entities you defined in the backend. Plugins are very straightforward to install and propagate between environments.

Native API querying is quite cumbersome. Has a nice Swagger plugin for the API, but it does not work properly for data fetch which renders it useless. GraphQL is the way to go, however, in v4 data structures became significantly complex. There is no way to force relationships between entities to be required.

Content management has well-defined flows and data entry needs. StrAPI removes tedious CRUD work to upload and publish your content. It also provides plugins for various types of hosting content to expedite development. At the same time, it gives you full flexibility to either build out the user interface completely or integrate CMS elements into an existing interface. In addition, it satisfies the self-hosting requirement, by supporting major data stores like Postgres and MySQL out of the box.

- Easy to configure and use - Big support community - Periodics updates and upgrades - Lots of plans and options for your business

- The documentation do not update with each update, you have to search a lot to find a solution to new versions bugs

- It's an easy and advanced way to have our own CMS and it's free

Wonderful means of coordinating the various components of content for website builds and updates - copy writers contribute, graphic artists contribute, component-builders build, etc....

Difficult to assign roles that minimize risk for various levels of users to do something unintended (like delete a component or page.)

Allowing folks with multiple roles and levels of experience to co-manage and collaborate.

Developer-friendly CMS system that makes it easy to set up your content models and start adding content in minutes. It's pluggable, and you can find plugins for most general use cases. It exposes REST (by default) and GraphQL (with a plugin), but I found GraphQL to be more suitable, and the auto-generated schema serves over 90% of my backend requests. Customizing the backend is possible if you need custom authentication/authorization logic. It has a slick and intuitive admin UI. Integrating OAuth providers was simple, stable and quick. Backend Customization The backend can be customized using either JavaScript or TypeScript which is very useful. Admin UI Admin UI is constantly improving with every release allowing customization for Rich Text inputs, dark mode and other features based on the community feedback.

Data Modeling Database unique and required constraints are not applicable for relations' fields.

Self-hosted headless CMS for Arabic-only software review and recommendation service.

This is by far the easiest solution for a headless CMS solution and even better as an API framework to power whatever your needs are.

Content editor fields are limited in some cases e.g. date input, document selector

Our students need a well-designed and constantly updated platform to support them along the way of their studies.

It helps reduce the time spent for some jobs.

Getting started with Strapi may be somewhat tiring. I hope it would be easier in the future.

Content management is easier with Strapi, it prevents developers from drowning in repetitive tasks.

Most sites (while perhaps not all) require dynamic substance to be put, altered, checked on, and erased from their site, so I used to construct (reuse) an administrator dashboard for each utilization and deal with the data set picking and association, backend, and so on. With Strapi, I can simply make a new Strapi project, snare it with a data set facilitated by a PAAS administration, and the CMS part is finished! It's an amazingly efficient arrangement and more versatile because an entire organization is upholding it with updates and fixes thanks to their group.

Working with content "assortment" types feels somewhat not quite the same as past CMS work, but when you get the hang of it, it makes building more extravagant substances extremely quick and solid. The differentiation between "saved" and "distributed" states likewise takes a little getting acclimated to, semantically. Ultimately, we're right now sorting out some ways to make specific info fields feel more recognizable and simpler to parse through. Yet, these vibe-like feasible issues are far offset by the upsides.

Strapi is taking care of the issue of demonstrating content and giving it to applications in a simple way that saves a ton of time and exertion. What used to take a long time to plan, which is setting up the backend, demonstrating the data set with crude dialects like MySQL, etc., building courses to get to the data set, giving jobs to approval, and so on, is presently finished by Strapi, so you just focus on the main job, not the reflections that accompany each task. The Strapi tool has permitted our groups and tasks to easily and immediately get our information accessible across different applications and undertakings with practically

- Customization - Performance - Plug and play concept

Everything works pretty good. However, some upgrades are necessary to manage better the data and add more functionalities to the UI.

I hosted the entire backend of one of my personal projects. It's easy to setup and you can immediately view and manage the data.

Strapi is super easy to spin up and customizable.

Cannot automatically upgrade from v3 to v4. Merging upstream changes can sometimes take a while if you make customization.

We use strapi as our backend service. Developers can focus on defining their collections rather than writing CRUD endpoints. It also provides a layer to interact with the database.

Strapi allows for easy creation of models for content. It also allows for easy creation of roles and users for granular access control which helps to consolidate our content in 1 single platform.

We have not tested if we are able to customize structure on Strapi. But what we look forward to testing out is the flexibility of that.

It helps us to build a CMS backend for business users to easily change content on our websites without going through the develoeprs.

The Strpi platform has allowed our teams and projects to easilty and quickly get our data accessable across multiple applications and projects with little to no trouble.

Many of the plugins don't seem to be well maintained so some hacking or work needed to be done to get them working. However overall, the exprince has been very good and easy to learn.

Allowing us to make it easy for developer and non-developers to quickly and easily contribute to our websites, blogs, application and apis.

Easy setup and very simple and intuitive to use.

Our developers love Strapi and haven't found any issues. Have used it in previous projects and will continue to use it.

Helping make managing our database and content on our new site easier.

User-friendliness of system, easy to use for non-tech peopleng

would like to have some features in the basic plan

International management of content for web app

The open-source nature of the framework as well as the ability to customize the framework to the needs of the developer. Also like that it's written in NodeJS as it's a very common language.

That there is no completely free plan available (as the admin user is limited in the free version). However, they offer a free Bronze version if you are a student or work for an NGO or Open-Source Project.

Build an open-source application at my university that enables users to enhance their daily health routine and get news and improvement suggestions about their personal health every day.

I like the integrational part about Strap to fetch the data from the API into your custom frontend website.

Maybe the guide and ability to customize the frontend for Strapi could be improved.

Now I no longer need to deploy my fronted website every time I have to change the content out there. It made me more efficient.

Strapi enables us to create a backend and CMS at the same time using a web interface while also enabling us to fully customise and add extra features to our backend using code. We're able to create graphql routes for each model or content type we add, and these routes have the full CRUD functionality, this has saved us a lot of time while building.

Some of the documentation isn't as helpful and is sometimes not up to date, this is something that has caused confusion for our developers while building or making certain customisations, so it's the one area that could definitely improve. The plugin marketplace is also very limited for v3.

We're solving to create a CMS that non-technical members of our team can use, and also reduce the learning curve for new developers joining our project, Strapi enables us achieve both with it's interactive admin dashboard.

Basic API functionality comes out of the box

There's a bit of a learning curve and custom features will need to be built from scratch in-house.

I am building an internal web tool for housing custom data sets to serve over an API.

Strapi is a flexible solution for the website's backend. It also seems easy to learn for content producers.

We have had some problems with long words in titles (our native language has long compound words).

We are using Strapi for the backend database for our website. It is easy to manage the data of our website with Strapi.

- Devs are happy about easy setup and easy handling - Backend is lean and easy to use - gives enough freedom to develop what you need

- you need experienced Devs to create a good structure for big websites

Strapi is flexible to adapt to your needs. You can go a long way with the free version.

- Easy to use - Good UI - Powerful yet intuitive

- Would like more default plugins - Handling of media files could be better

Building a flexible system that allows multiple types of users to add and edit content. Also, being Headless makes it very easy to consume the data.

Super fast to set up Highly customisable Active development roadmap GraphQL component focus

It's still pretty young would love to have a hands off cloud hosting option

As a small climate change charity we have been able to build a JAMstack based on strapi to replace our old WordPress setup. Its super-fast, secure, and just works.

I really love the simplicity of the content API. Normally I would have to write my Routes and Controllers inside Node and Express, which can take ages. With Strapi I only have to set them up in the UI, which is easy and straight forward!

I Would love to have the possibility to directly add/change UI layouts in the BackEnd. It would be great to to have a clickable "List" view of all connected Relations, which is currently not possible and makes it a bit more complicated.

My main Problem/Benefit is time saving. With Strapi I can fully focus on getting the Frontend and Application Logic done, while using Strapi as a "Visual Database" management system.

Strapi is highly customizable and easy to use so we were able to use it for entering content into a game we developed that is unique and custom built - Strapi was the perfect solution for managing the content.

I would've said lack of translation was a big hole but that issue was resolved in April and we're now in the process of translating our game into multiple languages. So no complaints!

We have a digital game that was designed from the ground up, with very specific content formats that don't match any existing content management systems. They combine graphical elements (uploaded as SVGs), text, interconnected collections, etc. The game is content intensive so it required a user-friendly interface that was highly customisable. The introduction of translation functionality has enabled us to now develop a multi-language version of the game.