Strapi has become useful to Sefaria beyond its function as a traditional CMS, especially for making our small-donor fundraising more efficient. It powers the targeted sidebar ads, banners, and modals in our web app so that non-engineering staff can configure campaigns directly in Strapi without code changes or deployments.

Because we're using Strapi headlessly, we can also use it to serve content to our mobile app. We've built custom API endpoints with a data structure customized for the mobile app's fundraising notifications. In both cases, staff use the same editor to manage content, while the web and mobile apps consume it independently. This lets fundraising and marketing make content changes without needing engineering support each time. Review collected by and hosted on G2.com.

There is nothing specific or noteworthy that comes to mind Review collected by and hosted on G2.com.

What I value most about Strapi is its flexibility when working on real-world projects. Being able to create custom content types and structure data exactly as we need it has made a huge difference in efficiency.

One of the things I value most is the option to use Strapi Hosting for free, especially in the early stages or for small projects. It allows you to develop and test without worrying about initial costs, which is a huge advantage over other CMS options. It's simply fantastic.

The admin panel is also very easy to use, even for team members without technical expertise. This has been a huge help, as content updates don't always depend on a developer, which streamlines our daily work.

I also appreciate how easily Strapi connects to modern frontend frameworks. By providing ready-to-use APIs, it integrates seamlessly into a headless architecture and simplifies content management across different parts of the project.

In terms of performance, it has been reliable for our use case, especially when combined with a modern frontend and a suitable hosting setup. It manages content delivery efficiently and scales well with project growth.

From a cost perspective, it offers excellent value, especially considering the level of control and customization it provides compared to traditional CMS platforms. It helps reduce reliance on more complex or expensive solutions.

The onboarding process is fairly straightforward for developers, and while some advanced configurations require some learning, the documentation and community resources are helpful enough to overcome most challenges. Review collected by and hosted on G2.com.

I wouldn't call them disadvantages, but Strapi does have some drawbacks. Some advanced settings can be a bit confusing at first. When working with custom logic, plugins, or permissions, you sometimes need to consult the documentation or resort to trial and error to achieve the desired result. Review collected by and hosted on G2.com.

Very simple to use from a content manager point of view. Review collected by and hosted on G2.com.

There isn't anything I dislike about Strapi when using as a content manager. It is expensive, even with a NFP discount, to subscribe to the Growth Plan with SSO, which is what we need - not sure how long we'll be able to afford it. Review collected by and hosted on G2.com.

Strapi stands out for its flexibility and ease of use as a headless CMS. Creating and managing content types is straightforward, and the APIs (REST and GraphQL) make it very easy to consume content from multiple websites and applications.

I also really appreciate that Strapi is self-hosted, which gives full control over data, infrastructure, and deployment. The admin interface is clean and intuitive, allowing non-technical users to manage content efficiently, while developers can easily customize APIs, permissions, and business logic when needed. Review collected by and hosted on G2.com.

The main downside is that more advanced customizations, especially in the admin panel or when extending core functionality, can have a learning curve. Major version upgrades may require additional effort, particularly if you rely on plugins or custom code. Review collected by and hosted on G2.com.

Strapi has been especially valuable for our work at Scouts de Colombia because it gives us a flexible and centralized way to manage all the content for both the main website (built with Astro) and the online store (built with Next.js). Its API-first approach lets us structure information exactly as we need it—documents, events, training content, product data, and internal resources—while maintaining full control over permissions and workflows.

The admin panel stands out because it’s intuitive for non-technical collaborators. Content creators and team members can update information without requiring a developer, which speeds up our publishing workflow and reduces bottlenecks. The integration with Vercel has also been smooth, and Strapi’s native support for media handling, roles, and custom fields makes it easy to scale our system as the organization grows.

Finally, Strapi gives us the freedom to create custom types and relations to reflect our real organizational structure. This has allowed us to build a CMS that supports both public-facing content and private internal processes, adapting naturally to the needs of a national volunteer organization. Review collected by and hosted on G2.com.

Some aspects of Strapi become challenging when working on a complex, multi-site project like ours. The main limitation is the absence of native features for rate-limiting, analytics of API usage, or built-in monitoring. Because our website receives traffic from multiple fronts—public visitors, store interactions, and internal tools—we’ve had to create additional layers in Vercel to protect forms, track errors, and manage request limits.

Another friction point is media storage. While the built-in media library works well, using remote image optimization (for example, Vercel's optimizer) requires custom setups since Strapi Cloud doesn’t offer a straightforward configuration for external loaders. This adds extra steps for performance optimization.

Finally, upgrading Strapi versions can sometimes introduce breaking changes. The migration guides exist, but handling them in a production environment with multiple environments and plugins demands careful planning. Review collected by and hosted on G2.com.

What I like best about Strapi is how flexible it is as a headless CMS. It’s quite easy to create and manage content types without needing heavy dev work each time. The admin interface is simple enough so even non-technical people in the team can publish or update content by themself. For exemple, we can quickly create landing pages for campaigns or update messages for new user acquisition tests without waiting for a full release cycle. I also appreciate that Strapi connects well with other tools and APIs, so we can push content to website, app or other platforms in the same time. Review collected by and hosted on G2.com.

What I like less about Strapi is that some configurations are not very obvious at first, especially when you start mixing plugins or custom permissions. Sometimes small changes require going a bit too deep in technical settings, which is not ideal for marketing teams. Performance can also be an issue when there is a lot of content entries or when media library becomes very big. Documentation helps, but sometimes it feels a bit fragmented, and you need to search several places to find the exact answer. Also, upgrades between versions can be a bit painful and break things that were working before. Review collected by and hosted on G2.com.

I like using Strapi because it allows me to publish and update our project information and pictures without needing to do manual updates directly to the code. This is especially beneficial since we use a static website, and it helps us save money by avoiding the costs associated with server payments, such as those we would incur with platforms like WordPress. I appreciate the templates in Strapi, which significantly speed up the process of defining our project's structure, eliminating the need to delve into coding. This feature is particularly advantageous because it simplifies the setup process, allowing for a more efficient workflow. Review collected by and hosted on G2.com.

I find the deployment process using GitHub and requiring a manual install initially to be cumbersome. This approach introduces extra steps, which can be quite daunting for non-technical users, effectively acting as a barrier. Review collected by and hosted on G2.com.

Strapi makes it incredibly easy to build, customize, and scale content-driven applications. I love its flexibility, intuitive admin panel, and the fact that it’s built with modern technologies like Node.js. The plugin ecosystem, robust API generation, and role-based access controls save a lot of development time. It’s also open-source and has a very supportive community, which makes learning and troubleshooting easier. Review collected by and hosted on G2.com.

While Strapi is excellent overall, some advanced features require plugins or self-implementation, which may add extra work. The documentation, though comprehensive, can sometimes lag behind new releases. However, these are minor compared to the value it provides. Review collected by and hosted on G2.com.

For simple website changes, it is pretty easy. Review collected by and hosted on G2.com.

There is still quite a bit of coding required on the back end, so if you aren't a coder, you probably need to work with one for some things in Strapi. Review collected by and hosted on G2.com.

I like that Strapi uses JavaScript, because as a web developer, I am already familiar with this language, which makes its use very convenient. The simplicity of Strapi is a great asset, as it allows me to quickly and easily create the various back office entries without necessarily needing to code. Moreover, it is really easy to configure initially, a single command in the terminal is enough to run the Strapi application on my machine. Review collected by and hosted on G2.com.

UI a bit slow from time to time. Backup available only at a certain payment level. Review collected by and hosted on G2.com.