Strapi Pricing Overview

We have a lot of very specific content formatting and structural needs. No matter what I've thrown at Strapi so far within the CMS, it seems to adapt well on the fly. Something I like a lot is being able to customize the administrative front-end for our editorial team. This affords them an incredibly user-friendly interface, all while guaranteeing a stunning experience by connecting it all to a custom front-end. The opportunity for us to use this at scale for future content distribution needs is already very promising. It's genuinely quite fun to use once you familiarize yourself with the feature set.

Working with content "collection" types feels a little different from past CMS work, but once you get the hang of it it makes building richer content very fast and reliable. The distinction between "Saved" and "Published" states also takes a little getting used to, semantically. Lastly, we're currently figuring out how to make certain input fields feel more familiar and easier to parse through. But these feel like solvable problems that are far outweighed by the positives.

It's allowing us to better share control over our content distribution pipeline with our colleagues, and introduce more consistency to our workflow as designers and developers. It's ultimately saving us a great deal of time and energy, and guaranteeing our end users will receive a more consistent and timely experience.

Most sites (while perhaps not all) require dynamic substance to be put, altered, checked on, and erased from their site, so I used to construct (reuse) an administrator dashboard for each utilization and deal with the data set picking and association, backend, and so on. With Strapi, I can simply make a new Strapi project, snare it with a data set facilitated by a PAAS administration, and the CMS part is finished! It's an amazingly efficient arrangement and more versatile because an entire organization is upholding it with updates and fixes thanks to their group.

Working with content "assortment" types feels somewhat not quite the same as past CMS work, but when you get the hang of it, it makes building more extravagant substances extremely quick and solid. The differentiation between "saved" and "distributed" states likewise takes a little getting acclimated to, semantically. Ultimately, we're right now sorting out some ways to make specific info fields feel more recognizable and simpler to parse through. Yet, these vibe-like feasible issues are far offset by the upsides.

Strapi is taking care of the issue of demonstrating content and giving it to applications in a simple way that saves a ton of time and exertion. What used to take a long time to plan, which is setting up the backend, demonstrating the data set with crude dialects like MySQL, etc., building courses to get to the data set, giving jobs to approval, and so on, is presently finished by Strapi, so you just focus on the main job, not the reflections that accompany each task. The Strapi tool has permitted our groups and tasks to easily and immediately get our information accessible across different applications and undertakings with practically

Our team of developers are doing their best to make us feel comfortable using the back end of our game app. They were able to create a wizard for us ! I love that you, although the interface is intuitive, you can get help if needed. Thanks to Strapi you can keep things simple and functional for optimal results. My experience with this ongoing project has been really pleasant and user-friendly for every level of tech savyness ;)

Still learning but haven't had any bad experience so far, will update if we do with time.

Enables all the stakeholders (other non-for profits in different cities of BC, Canada) to be responsible for their part of the game and be able to upload and update their own content freely with no cost.

Strapi is an awesome product for quickly setting up CMS and API for your products. We started working with Strapi in Dec 2020. Since then, we have used Strapi in three of our projects. Basic things like Rate Limiting, Authentication, Roles and Permissions are pre-built into Strapi. If you know Strapi, you can set up your fully functional E-Commerce store in a day.

There are some technical issues that I am confident would be fixed in the next major release. One that comes to my mind is that context is not available in lifecycle hooks. Another thing I would want the Strapi team to consider is to make Strapi on Serverless environments. Also reducing the size of node modules can help a lot.

Setting up CMS for non-technical users was one of the biggest issues for our firm. It would cost our clients a lot of money, training sessions and time. After using Strapi, the cost is less, fewer frustrations and happy clients.

Strapi is easy to get up and running quickly, even for the most junior developer. Its total cost of ownership is down to earth, especially as nearly all SaaS alternatives are overpriced. It has a solid API and has no artificial predefined limits.

No sdks and new features develop slowly.

Needed a blazing fast content management system at a scale that WordPress chokes and SaaS Headless CMS providers demand an exuberant amount of money.

Very easy to adopt, wonderful client service and good pricing.

Not the easiest to customize, according to our dev team, but gave us a lot of the major stuff we needed out of the box

Quick time to production. It would've taken us much longer without it

For us, as a non-profit organization with limited funds, Strapi offers one of the best solutions on the market when it comes to headless CMS: - It’s easy to install and configure - It can be deployed to a PaaS (e.g., Heroku) such that we don’t have to deal with the runtime environment, OS and so on - We keep complete control over UI, extensions, data, and models - Maximum flexibility through extensions, i.e., use the HTML editor of your choice - It is open source - Excellent documentation—most questions have been asked and answered before - GraphQL API (it’s an extension)

Unfortunately, this highest flexibility comes at a cost: We have to install, deploy, and test it ourselves, but Strapi is about to launch the Strapi Cloud bringing this flexibility to a SaaS. So don’t take this dislike too serious.

We are developing new projects on a modern tech stack, e.g. with NextJS. Thus, we heavily rely on a predictable and potent API. With Strapi, we can decide whether to consume REST or GraphQL—both work well. Editors get a fantastic user experience with components in models, the media manager, and the navigation extension for drawing the site’s/menu structure.

I really enjoy how easy Strapi is. You can build complex APIs including relation, automatic slug, field assertions and so on. You can also define multiple roles and give different read / write / update / delete conditions for each of these roles. You can also give more complex permissions with just a click like "a user can update a resource only if he created it".

Roles management for community edition is quite restrictive. It may not be an issue with other editions but I couldn't try it at this time. Anyway, pricing are quite expensive for small companies.

At the time I write these lines, I've only used Strapi for local development. But it really helped me to develop faster. I used to develop my APIs from scratch.