Storyblok
StoryblokReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
490 reviews
from
External reviews are not included in the AWS star rating for the product.
The website is pretty good for managing digital content.
What do you like best about the product?
Storyblok makes it really easy to manage structured content while still giving marketers and editors a visual editor they actually enjoy using. As a developer, I like that the API-first approach lets me use any front-end framework (React in my case) without limitations. The component-based content blocks also make it simple to reuse sections across multiple pages, which saves a lot of time when building out new sites.
What do you dislike about the product?
While I love how efficiently storyblok helps to manage content but it can overwhelming to use in the beginning as everything looks complex . The permission setting are not much optimised too so that can be a problem when working with large teams to manage access across different roles.
What problems is the product solving and how is that benefiting you?
I personally use Storyblok for my personal projects as it helps me separate my content from the code. So now I can focus on frontend and manage my content efficiently.
Great CMS better than competitors
What do you like best about the product?
Provides a lot of useful tools and components. Compared with other headless cms, storblok provides better UI/UX an integration
What do you dislike about the product?
the pricing is not the best compared with
competitors
competitors
What problems is the product solving and how is that benefiting you?
Dynamic content generation
UI customization
UI customization
Good product, but be ware of price increases
What do you like best about the product?
Easy enough to use for my clients, virtual editor, fast CDN. I like their multi framework support and management apis
What do you dislike about the product?
No user management — it would be nice to be able to have user specific content even if it was just basic. I get why they don’t have this but it would be nice.
Biggest thing I don’t like is that they altered their usage policy and plans which is now costing my clients 3x what they were paying a few months ago with no added benefit.
Also it is difficult for users to do bulk changes.
Biggest thing I don’t like is that they altered their usage policy and plans which is now costing my clients 3x what they were paying a few months ago with no added benefit.
Also it is difficult for users to do bulk changes.
What problems is the product solving and how is that benefiting you?
Better than Wordpress essentially. We just need an easy place for clients to edit their websites
Almost perfect CMS
What do you like best about the product?
As a developer, I find Storyblok to be amazingly simple to work with.
As a project manager, I've noticed that Storyblok is quite easy to teach which proves how intuitive the UI is.
These features I like the most:
- Creating blocks
- Creating templates
- Implementing to new and existing projects is super easy
- The api is very easy for integrations
- Real time preview of current state of content
- Save / publish -pattern
- Internationalization features with AI
- Amazing media service
I use Storyblok almost daily.
As a project manager, I've noticed that Storyblok is quite easy to teach which proves how intuitive the UI is.
These features I like the most:
- Creating blocks
- Creating templates
- Implementing to new and existing projects is super easy
- The api is very easy for integrations
- Real time preview of current state of content
- Save / publish -pattern
- Internationalization features with AI
- Amazing media service
I use Storyblok almost daily.
What do you dislike about the product?
1. The latest pricing model did cause problems on selling Storyblok. Especially the 20€/month for each extra language after two languages feels super steep.
2. I really miss the repeater-kind of feature that would essentially make a lot of sense and reduce the amount of required clicks when creating content
3. User roles in smaller plans
2. I really miss the repeater-kind of feature that would essentially make a lot of sense and reduce the amount of required clicks when creating content
3. User roles in smaller plans
What problems is the product solving and how is that benefiting you?
It brings us a way to offer our customers a great CMS experience
Easy to use, hard to master
What do you like best about the product?
Storyblok is quite easy to understand. It offers a nice developer experience. CMS editors do not need exhausting onboardings (if the blocks are developed carefully). Storyblok offers a nice feature set out-of-the-box. Fast responses over the Discord channel.
What do you dislike about the product?
I am missing same basic feature and it does not seem like these features are even on the list. For example hide/show components, a field type to select folders, a field type to select one or multiple tags. All of that need to be developed by the integration team.
What problems is the product solving and how is that benefiting you?
Other Content Management Systems offer in most cases a quite awful developer experience. For Storyblok I can tell that the integration is quite easy. The time-to-market value for us as a agency is pretty important.
Good Interface, not for beginners
What do you like best about the product?
I like the flexibility with the blok building and the live updating editing screen. That's something that stands out in comparison to other CMS systems out there. I like the ability to add custom layouts in the block setup in my custom bloks.
What do you dislike about the product?
For a developer like myself I could understand how to make all the bits and pieces function correctly but I can see how this may be intimidating for beginners. I don't find the setup as easy and straightforward as other CMS systems. Sometimes I find support to be lagging in response time.
What problems is the product solving and how is that benefiting you?
Storyblok is allowing myself and a creative team produce custom bloks that can then be used to build websites for various branches in our company. These building bloks can be used by other colleagues who aren't as tech savvy which bridges the gap between developers and marketing. By creating something that someone else can easy learn to use, it removes the necessity to require constant developer interference where simple content updates are needed to be made. Ultimately, creating our sites in storyblok allow for us developers to gain more time to work on various other projects we have on the go while allowing other departments to continue to make the updates that they need.
Technically strong CMS with great flexibility and preview
What do you like best about the product?
Storyblok feels very technically sound while still being editor-friendly. The live preview is one of the best I’ve seen and gives teams confidence when publishing. Thanks to its flexibility, almost any use case is possible . From straightforward websites to complex multi-market setups.
What do you dislike about the product?
Pricing is transparent, but it ramps up quickly. You’re nudged toward premium or enterprise tiers. That can feel heavy when you just want to start lean and grow from there.
What problems is the product solving and how is that benefiting you?
Storyblok solves the classic pain of editors breaking layouts or waiting on developers for small changes. With structured content and the live preview, our marketing teams can publish faster and stay on brand. The flexibility of the headless approach also means we can integrate with other systems (CRM, ERP, analytics) without hacks or fragile plugins. The result: quicker launches, fewer tickets, and more confidence for both editors and developers.
Amazing product with some rough edges
What do you like best about the product?
It is definitely the best of its kind - a block based system natively integrates with the component system of React and thus makes it easy as a developer to "translate" the structure content editors define into something visual. Compared to WordPress or other legacy CMS systems, it is definitely the go-to-way for people using React, Next.js or similar technologies. If you have simple requirements, you will have a great time using Storyblok. For very simple blog pages and the-like there should be no issues. It is actually pretty easy to get up and running with extensive guides that show you exactly what you need to do. It is easy to integrate as there are example repositories, blog posts, and documentation entries. If you intend to build something more complex though, your are way more likely to run into some limitation though and you may even be bottlenecked by the guides down the line (see below in dislike part).
I work with Storyblok almost daily since we adopted it about 9-10 months ago and definitely like the ease of use in the editor interface, even though I am not really an end-user but you still spend much time in there when testing stuff. Our marketing team had great feedback too, especially in comparison to our old, slow WordPress instance.
It is great that the SDKs are open-source - this helps understanding some internal functionality and can help in resolving bugs without the need to contact anyone. It also allows to potentially directly contribute, but I would say that is a whole different discussion if you as a company want to/should contribute to an SDK of a software you potentially already pay thousands per month for.
I work with Storyblok almost daily since we adopted it about 9-10 months ago and definitely like the ease of use in the editor interface, even though I am not really an end-user but you still spend much time in there when testing stuff. Our marketing team had great feedback too, especially in comparison to our old, slow WordPress instance.
It is great that the SDKs are open-source - this helps understanding some internal functionality and can help in resolving bugs without the need to contact anyone. It also allows to potentially directly contribute, but I would say that is a whole different discussion if you as a company want to/should contribute to an SDK of a software you potentially already pay thousands per month for.
What do you dislike about the product?
The first thing that really startled me was that the API sometimes has a really weird data format - numbers come as string, empty fields are "" instead of null (this also applies to e.g. booleans), etc. We built custom wrappers to normalize the data format and validate content coming from Storyblok. It is a pretty common pattern that you need to do some kind of custom solution building or creating workarounds, especially if you plan to use it extensively for all different kinds of content with different functionalities in mind. While that is not necessarily bad, I have seen multiple GitHub issues mentioning "XYZ should [already] be in the library". I don't want to know how often the same basic stuff has already been (re-)implemented all over the world.
I have found myself countless times scouring through the OSS source code of the React and JS library to find a bug, a solution or undocumented special case. Additionally, some in my opinion "no-brainer" features are definitely missing and resulted in us having to invest many hours into building something custom again and again (for example text alignment in RichText does not exist) - it is great that it is even possible to extend and workaround the system using additional fields or custom plugins, but every time I think about the fact that the Enterprise pricing plan is pretty expensive I say to myself everything should be buttery smooth out of the box.
While the support team is super friendly, at least in all cases I had to reach out to them, out of all feature requests we ever submitted over the course of almost a year now none have landed in the software yet (so prepare yourself to build custom stuff and workarounds). The feature request process is also pretty intransparent and you don't know if it has been considered, rots in their backlog forever or if it was internally discarded.
I have found myself countless times scouring through the OSS source code of the React and JS library to find a bug, a solution or undocumented special case. Additionally, some in my opinion "no-brainer" features are definitely missing and resulted in us having to invest many hours into building something custom again and again (for example text alignment in RichText does not exist) - it is great that it is even possible to extend and workaround the system using additional fields or custom plugins, but every time I think about the fact that the Enterprise pricing plan is pretty expensive I say to myself everything should be buttery smooth out of the box.
While the support team is super friendly, at least in all cases I had to reach out to them, out of all feature requests we ever submitted over the course of almost a year now none have landed in the software yet (so prepare yourself to build custom stuff and workarounds). The feature request process is also pretty intransparent and you don't know if it has been considered, rots in their backlog forever or if it was internally discarded.
What problems is the product solving and how is that benefiting you?
Easy, fast, customizable and rich content building for the marketing team. It benefits the development process since all data is structured.
Flexible Headless CMS with Great Developer Experience
What do you like best about the product?
Storyblok’s visual editor is a standout feature — it gives marketers and non-technical users full control over content while developers enjoy the flexibility of a headless CMS. Its component-based structure makes content scalable, reusable, and easy to manage across multiple projects. The API-first approach and solid documentation also streamline development workflows.
What do you dislike about the product?
Some features, like custom roles and advanced permissions, are only available in higher-tier plans. The learning curve for non-technical users can still be steep at first, especially when working with dynamic components or structured data. Also, performance can occasionally lag in the visual editor for large-scale projects.
What problems is the product solving and how is that benefiting you?
Storyblok helps us solve the challenge of managing and delivering content efficiently across multiple platforms. Its headless CMS architecture allows us to separate content from presentation, which speeds up development and makes it easier to deliver a consistent experience across websites, apps, and digital channels. The visual editor is especially helpful for non-technical users, enabling our team to collaborate without relying heavily on developers. This has improved our content workflow, reduced time-to-market, and allowed us to scale content operations more effectively.
My favourite headless cms
What do you like best about the product?
Storyblok makes the other headless offerings feel clunky and slow. The content is organized in folders that automatically have the equivalent of a URL path to access them, making it super easy to map content to a website IA without some convoluted navigation system. The UI is clean and responsive.
The ability to save presets for each type of content allows you to provide optional complexity while keeping things simple for your customers, and gives peace of mind that the beautiful thing you created isn't going to get ruined by someone that doesn't know what they are doing.
Implementation is easy with a well documented and simple api. There are great tutorials for all the major tech stacks. Customer service is friendly and responsive.
There is a generous starter plan that is always free for developers and small business.
Our customers love Storyblok as much as we do.
The ability to save presets for each type of content allows you to provide optional complexity while keeping things simple for your customers, and gives peace of mind that the beautiful thing you created isn't going to get ruined by someone that doesn't know what they are doing.
Implementation is easy with a well documented and simple api. There are great tutorials for all the major tech stacks. Customer service is friendly and responsive.
There is a generous starter plan that is always free for developers and small business.
Our customers love Storyblok as much as we do.
What do you dislike about the product?
I honestly can't think of anything, sorry.
What problems is the product solving and how is that benefiting you?
Storyblok provides a simple CMS that is easy and fun to use at a competitive price point.
showing 1 - 10