Strapi
StrapiReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
192 reviews
from
External reviews are not included in the AWS star rating for the product.
Flexible and customisable to our needs
What do you like best about the product?
Strapi’s flexibility and customization options are what we appreciate the most. The headless architecture allows us to structure content as needed, offering a robust API that integrates seamlessly with our other systems. Being open-source, we have full control over deployment, and the community support has been invaluable. Additionally, its user-friendly interface makes it easy for non-technical staff to manage content without much training, which boosts our productivity.
What do you dislike about the product?
While Strapi offers a lot of customization, setting it up and maintaining it on-premise can require significant development time, especially when it comes to scaling. The admin panel, though intuitive, could be more feature-rich in terms of out-of-the-box analytics and user roles. Also, we’ve encountered some challenges with plugin compatibility, which sometimes slows down our workflow.
What problems is the product solving and how is that benefiting you?
Strapi solves the challenge of managing diverse content across multiple platforms by providing a flexible, API-driven approach. We needed a solution that could centralize content creation while allowing it to be distributed to our website, mobile app, and other channels effortlessly. Strapi’s headless CMS enables us to streamline our workflows, reduce duplication of effort, and maintain consistent content across platforms. Additionally, its open-source nature allows us to customize it to fit our exact organizational needs, all while keeping costs manageable. This has improved our team’s efficiency and accelerated the development of new features.
Easy to setup and powerful CMS
What do you like best about the product?
Strapi is very easy to setup locally as a developer to begin experimenting with. The documentation quickly guides you through the steps to get started, but also is thorough when you need a bit more detail (like understanding supported query parameters with API requests). Within an hour I had our admin panel deployed to Strapi cloud and added test content, and was then pulling that content with the API minutes later. It was simple to configure API access to content as well - allowing certain collection types to be available without credentials, while restricting others. Our team began using it later on that same day I deployed it.
What do you dislike about the product?
We don't have any dislikes with Strapi at the moment.
What problems is the product solving and how is that benefiting you?
We need a simple system for our non-developers to create content that can be published on our website. Strapi provides the system to do that, making it easy to create collection types/templates that content creators have to adhere to, and that can be easily consumed downstream.
Ideal CMS for any Enterprise or Small Business
What do you like best about the product?
Strapi is overall very easy for developers and users. It has sensible and easy-to-integrate querying whether it's via fetch or GraphQL, and their default data modeling tools solve most of the use cases I've had without much customization. I use it for just about every client I work with now, provided they actually have content to publish. The customer support is also very helpful. While on a larger corporate engagement, which was my first project using Strapi, our project managers reached out to them often and they were always responsive and helpful.
What do you dislike about the product?
As a CMS, I expect to see more user-friendly rich text entry than what you get with Strapi Basic. Sure, it's easy enough to use other plugins to have a more robust rich text editor, but if Strapi were to make that more easily available, it would be the perfect solution for any business's editorial needs right out of the box.
What problems is the product solving and how is that benefiting you?
Providing clients with a way to manage their content without having to go through a developer. It gives me an easy way to get clients to sign onto full-stack development projects with the ability for them to manage their own content without a lengthy development period.
Changing CMS
What do you like best about the product?
Strappy is a CMS easy to use, install, and deploy
What do you dislike about the product?
Limited Database Migration/Seed Support: the platform has limited support for database migration and seeding, which can be a challenge when moving content types or making updates
What problems is the product solving and how is that benefiting you?
Lots of Wordpress issues regarding CMS
One of the best headless CMS available in Node.js. Highly sclable
What do you like best about the product?
The framework itself and easy of developing and deploying custom plugins.
Strapi is open source and very easy to learn. Its the fastest way to deploy api's and add security layers to it.
Best part is that it has a huge community support.
Strapi is open source and very easy to learn. Its the fastest way to deploy api's and add security layers to it.
Best part is that it has a huge community support.
What do you dislike about the product?
Deploying strapi is tricky if you are self hosting this tool.
Few things you might need to take care of like using pm2 and deploying instances of strapi on different ports to better support and decouple heavy processes that needs to run on multiple threads on a server.
Few things you might need to take care of like using pm2 and deploying instances of strapi on different ports to better support and decouple heavy processes that needs to run on multiple threads on a server.
What problems is the product solving and how is that benefiting you?
Content Management, providing a backend UI to manage content. Enabling faster API development and deployment along with ACL.
Very Good but the open source should be different
What do you like best about the product?
As a Software Engineer,
- I love the way it is API-driven and React based.
- Ease of Implementation
- Ease of Use
- Ease of Integration
- I love the way it is API-driven and React based.
- Ease of Implementation
- Ease of Use
- Ease of Integration
What do you dislike about the product?
The PRO features. I don't think this should be in the community version.
What problems is the product solving and how is that benefiting you?
I believe that scalability is key feature.
Really solid but simple
What do you like best about the product?
I have found Strapi simple yet powerful. We have another enterprise CMS that is behemoth and very easy to get tied into its proprietary features. Strapi so far has given me a simple headless CMS that allows my apps to stay largely CMS agnostic - exactly what I wanted.
Its interface is intuitive and makes content creation and management easy, even for less technical team members. I have bene impressed with the flexibility in API usage. My devs have found integration really quite fun and straightforward, largely thanks to its well-documented APIs and straightforward customization options.
Strapi - the company has proven responsive to user base. The development team appears to be well-focused on enhancing the platform by implementing features that add actually the most value. There is a solid community around this product and, as such its pretty easy to get input from other users.
We don't typically do a ton of cloud deployment, but we are running Strapi cloud pro and I could not be happier with it. Deployment and management are simple and reduce the burden on my team. Really excellent cloud implementation - definitely exceeded my expectations, but devs can spin up a local instance in a minute or 2 for their work.
Really solid product.
Its interface is intuitive and makes content creation and management easy, even for less technical team members. I have bene impressed with the flexibility in API usage. My devs have found integration really quite fun and straightforward, largely thanks to its well-documented APIs and straightforward customization options.
Strapi - the company has proven responsive to user base. The development team appears to be well-focused on enhancing the platform by implementing features that add actually the most value. There is a solid community around this product and, as such its pretty easy to get input from other users.
We don't typically do a ton of cloud deployment, but we are running Strapi cloud pro and I could not be happier with it. Deployment and management are simple and reduce the burden on my team. Really excellent cloud implementation - definitely exceeded my expectations, but devs can spin up a local instance in a minute or 2 for their work.
Really solid product.
What do you dislike about the product?
The recent (beta 5) introduction of versioning and further simplification of the API is an example of Strapi's responsiveness. Lack of these 2 features in version 4 would have been my only gripe.
What problems is the product solving and how is that benefiting you?
Headless CMS without bloat, but with loose coupling was the business need. Simple and does its job well and not a bunch of extra stuff. That's what we need from our integration solutions, allowing us to focus on loose coupling, but with a reliable feature set.
Strapi great option for headless CMS
What do you like best about the product?
I like the community approach of strapi and the richness of features they provide. I've tested a couple products in the market and this is one of the best.
What do you dislike about the product?
I think the Admin user experience could be improved.
What problems is the product solving and how is that benefiting you?
help helps with a cost effective way of building and scalling a headless CMS built on a nodejs stack
A User-Friendly CMS with Exceptional Support
What do you like best about the product?
Strapi has a very intuitive interface, which has helped both our technical and non-technical teams. The roles in the admin panel are very useful because whenever I deploy something for the non-technical members to use, they ask me, "Does this allow me to break something unintentionally?" With the roles in the Strapi panel, I can disable everything but content editing, and they can use it without any fear. Another aspect worth mentioning is their customer support. I reached out to them on LinkedIn and via email. The email support was not very good; they didn’t understand what we needed, but the LinkedIn support was exceptional. They quickly communicated and gave us exactly what we needed. We currently use Strapi weekly, and it is reliable.
What do you dislike about the product?
While Strapi's implementation and integration process is straightforward and developer-friendly, a point of consideration is the separation between development and production environments. Content created and managed in the development doensn't automatically propagate to the production environment, an you need to re-enter all the content again in the production. Another thing is their e-mail support. I think they have a "customer success manager" or something similar, a person who is not very familiar with the technological aspects of the product. They don't really understand and help with technical problems. Given that this platform is more geared towards developers than end-users, I would like to see a technical person in the support team.
What problems is the product solving and how is that benefiting you?
Strapi has solved our need for a simple and quick-to-set-up content management system, which is a big help for our team members who aren't technical. It's made managing our website a lot easier for everyone, speeding up our work.
Used Strapi for Funding Partner Proof of Concent
What do you like best about the product?
Strapi was instrumental in quick prototyping for a funding partner's application needs. The flexible schema and cloud hosting were especially helpful in getting something off the ground.
We were able to easily connect the Strapi backend, with Algolia search and a Remix frontend in a short period of time, which helped us deliver the application needed.
We were able to easily connect the Strapi backend, with Algolia search and a Remix frontend in a short period of time, which helped us deliver the application needed.
What do you dislike about the product?
The plan pricing of Strapi Cloud didn't match our needs. Strapi has recently introduced other plans to address this issue, which is nice to see.
We had some issues customizing the admin experience as much as we wanted, though that may be more about our need for a user-facing admin system.
We had some issues customizing the admin experience as much as we wanted, though that may be more about our need for a user-facing admin system.
What problems is the product solving and how is that benefiting you?
We are using Strapi as an administrative backend for a proof-of-concept product.
showing 11 - 20