Strapi review

Strapi is an open-source content framework for modeling content and turning it into REST and GraphQL APIs. It is not a finished website or a hosted CMS by default: your team shapes the backend, admin panel, and content structure, then deploys on its own infrastructure or uses Strapi Cloud.

The Content Type Builder lets teams define content models through a no-code interface. Reusable components and dynamic zones let editors arrange structured content blocks. Developers can add custom controllers, services, and middleware, and customize the admin panel. That makes Strapi a fit when the API and content model need to match a particular product, rather than forcing the project into a fixed set of CMS fields.

Hosting is a separate decision. The published pricing lists Strapi Cloud plans from $35 per project per month; it does not list a free hosted plan. Self-hosting is also an option, but the published pricing details do not specify its infrastructure costs.

Strapi’s main advantage is control. Teams can model content, expose it through REST or GraphQL, and customize backend logic instead of treating the CMS as a fixed box. The Content Type Builder lowers the barrier to creating models, while custom controllers, services, and middleware give developers room to handle requirements the default API does not cover. Admin customization can also help fit the editing interface to a team’s workflow.

Components and dynamic zones are useful when content needs repeatable, movable blocks rather than one undifferentiated text field. That structure gives the frontend a defined shape to work with, though it also means the team has to decide how much freedom editors should get.

Strapi can be self-hosted or run on Strapi Cloud. For hosted projects, the pricing details list $35 per month for Starter, with 100,000 API requests, 50 GB of asset storage, and 50 GB of monthly bandwidth. Pro costs $90 monthly and raises those limits to 1 million requests, 250 GB of storage, and 500 GB of bandwidth. Those are concrete starting points for teams comparing hosting against managing their own deployment.

Strapi’s flexibility comes with choices to make and maintain. One Reddit thread comparing it with Directus includes users who preferred Directus’s interface and workflow; another commenter said Strapi’s documentation was lacking. These are individual reports, not a measure of every team’s experience, but they are worth weighing if editors need a polished, obvious workflow without much setup. A commenter on r/Strapi also described Strapi as resource intensive, while another reported running it for years without major issues.

The hosted bill can rise with traffic and environments. Starter is $35 per project per month for 100,000 API requests, 50 GB of storage, 50 GB of bandwidth, one environment, and seven-day observability. Pro is $90 for 1 million requests, 250 GB of storage, 500 GB of bandwidth, and weekly backups; it includes one environment. Business is $450 for 10 million requests, 1,000 GB each of storage and bandwidth, two environments, and a 99.9% uptime SLA.

Overages cost $1.50 per 25,000 API requests, $0.60 per extra GB of storage, or $30 per 100 GB of bandwidth. Annual billing saves up to 17%, but annual plan prices are not published. Compare the hosted limits and editor workflow before switching.

Strapi Cloud’s listed monthly prices are per project: Starter is $35, Pro is $90, and Business is $450. That’s a $55 jump from Starter to Pro, then $360 more from Pro to Business. The higher tiers add request capacity, storage, bandwidth and environments; Business also lists a 99.9% uptime SLA. Starter includes 100,000 API requests, 50 GB of asset storage and 50 GB of bandwidth monthly. Pro raises those limits to 1 million requests, 250 GB storage and 500 GB bandwidth. Business lists 10 million requests, 1,000 GB storage and 1,000 GB bandwidth.

Watch the overages: extra requests cost $1.50 per 25,000, storage is $0.60 per GB, and bandwidth is $30 per 100 GB. Extra environments cost $60 monthly on Pro and $300 on Business. Annual billing saves up to 17%, but annual plan prices aren’t listed. There’s no listed free hosted plan; self-hosting is an alternative, but its costs aren’t specified here.

Switching to Strapi means rebuilding your content models and API setup around its framework. The Content Type Builder can create models without code, but custom controllers, services, middleware, components and admin changes may add migration work. Treat that as project-specific: the published material does not document a migration tool or estimate effort.

Strapi offers a choice between Strapi Cloud and self-hosting, so you are not required to keep hosting with Strapi. That does not make custom backend code automatically portable; plan to assess dependencies and rewrite work before moving. Data export formats and procedures aren’t specified in the published material, so verify them before committing. The fit may weaken if editors need a familiar writing workflow or the hosted usage add-ons make the bill hard to predict. The published sources include no Reddit posts, so we can’t substantiate a claim about what users there tend to cite when leaving.