Strapi

What do you like best about the product?

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.

What do you dislike about the product?

UI a bit slow from time to time. Backup available only at a certain payment level.

What problems is the product solving and how is that benefiting you?

Strapi allows me to quickly and easily build a back office in JavaScript without needing to code, which is convenient for a web developer.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Strapi allows us to centralize all the content management needs for Scouts de Colombia in a single, structured system. Before using it, our information was scattered across different platforms, documents, and custom tools, making it difficult to maintain consistency and ensure that every team had access to updated content. With Strapi, we now manage institutional documents, program information, events, products for the store, and internal resources through unified content types that reflect our organizational structure.

Strapi also solves the challenge of maintaining two different frontends—our Astro-based public site and our Next.js store—while ensuring that all content remains synchronized. Its REST and GraphQL APIs make it easy to deliver the same data to multiple applications without duplicating effort. Permissions and roles help us control who can publish and update content across national teams, which strengthens governance and reduces errors.

Another major benefit is workflow efficiency. Strapi empowers non-technical members to update pages, resources, and announcements, reducing the dependency on developers and accelerating our communication cycle. The flexibility to design custom relations and collections means the CMS adapts naturally to our processes instead of forcing us to fit into a rigid structure.

Overall, Strapi provides structure, speed, consistency, and scalability to our digital ecosystem, helping us support both public engagement and internal operations across a national volunteer organization.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

I use Strapi to avoid manual code updates, save on server costs by not using WordPress, and speed up project structure definition with templates.

What do you like best about the product?

The platform is easy to use and offers internationalization support right from the start. Its API and media asset integration are also well implemented.

What do you dislike about the product?

The pricing feels somewhat high; having to pay $50 just for a second environment seems excessive to me.

What problems is the product solving and how is that benefiting you?

The ability to easily integrate a CMS, API, and CDN with minimal development required is impressive.

What do you like best about the product?

The only positive I can mention is its customizability. Strapi does give you flexibility to tailor things to your needs. However, this benefit was overshadowed by the constant struggles with maintenance, bugs, and deployment.

What do you dislike about the product?

did not have a good experience with Strapi. From the start, it was very difficult to use – the setup and day-to-day development felt overly complicated compared to other CMS solutions. Deployment was another major pain point: it often broke unexpectedly, with little clarity on what went wrong. On top of that, I ran into unpredictable bugs that slowed down development and created a lot of frustration.

Version upgrades were an absolute nightmare. Every time a new version came out, upgrading caused breaking changes or required extensive rework, making it feel unstable and unreliable for long-term projects.

What problems is the product solving and how is that benefiting you?

Strapi didnt solve our problems it just kept giving us more problems