Strapi

What do you like best about the product?

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.

What do you dislike about the product?

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.

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

Before using Strapi, content management relied heavily on developers, which slowed down updates and made even small changes take longer than expected. It was also more difficult to keep content organized and reusable across different parts of the project.

With Strapi, we can centrally structure content and allow non-technical team members to manage it directly. This has reduced the need for constant developer involvement and streamlined and optimized updates.

What do you like best about the product?

I use Strapi as a CMS and find that it creates a very good admin panel. I like the UI, which is important for a CMS. The content type builder and content manager are the tools I value the most. The initial setup was easy.

What do you dislike about the product?

Multi language support is terrible. It can have better i18n.

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

Strapi creates a very good admin panel, which is a key benefit for my CMS needs.

What do you like best about the product?

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.

What do you dislike about the product?

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.

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

Strapi is solving the problem of content being too dependent on developers. Before, each small change on a landing page or sign-up page text needed a dev task and a release. Now, we can update content directly in Strapi, which is much faster for acquisition experiments. For exemple, we can change headlines, benefits or CTAs during a campaign and immediately see the impact on conversions.

It also helps to standardise content structure. Instead of copy-pasting text everywhere, we manage content centrally and distribute it through APIs to different channels. This reduces mistakes, keeps messages consistent, and saves time for both marketing and tech teams. In the end, it makes experimentation and growth activites more agile.

What do you like best about the product?

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.

What do you dislike about the product?

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.

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

Strapi solves the problem of decoupling content management from the application code. It allows non-technical teams, such as Marketing and Legal, to create, update, and manage legal documents, website content, SEO metadata, and other editorial content without requiring any involvement from the development team.

This has significantly reduced development bottlenecks and improved autonomy for these departments. Marketing and Legal can publish updates faster and remain compliant without waiting for code changes, while developers can focus on building and maintaining product features. As a result, content workflows are more efficient, and changes can be safely rolled out across multiple websites and applications from a single centralized system.

What do you like best about the product?

Nothing. We had the free plan, and later on we couldn't subscribe to the paid plan, because the project was suspended. Emailed them 5 days back and forth, found no solution. Please avoid them.

What do you dislike about the product?

Everything, we've had some much issues with the support, wasted a lot of our time and energy. Please avoid Strapi.

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

Articles