My main use case for Storyblok is that it is a headless content management system for me. I set up content in Storyblok, and then I use the Storyblok API client to manage it. Storyblok is not deployed anywhere; I access it through the API, and it is publicly available. While I have my keys, it is software as a service, so it is a headless CMS, and I do not have to deploy anything; it is just accessible for me through the internet.
Storyblok
StoryblokReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
562 reviews
from
and
External reviews are not included in the AWS star rating for the product.
The real value? Fewer dependencies between teams
What do you like best about the product?
The component-based architecture, as it isn’t just a feature but it changes how teams think about content. Leading a 10-person dev team working on multiple mid to enterprise customers, the biggest lever I see is that Storyblok dissolves the boundary between development and content editing without either side compromising. Enabling efficiency improvements across the board.
What do you dislike about the product?
The plugin marketplace still has room to grow and a couple of bulk actions need to be improved.
You have to go on the hunt for some real good community plugins. They exist, but its difficult to find them if you are not on discord and the community hubs.
You have to go on the hunt for some real good community plugins. They exist, but its difficult to find them if you are not on discord and the community hubs.
What problems is the product solving and how is that benefiting you?
Storyblok bridges the gap between technical teams and editors. For our customers, this means they can start working on content before development has even finished implementation. Editors independently create landing pages, storytelling formats, and campaign content while we set up the component library once and keep it clean. It's not so much about reducing dev time – it's about reducing dependencies between teams. That's the actual value our customers report.
Beyond the CMS itself, Storyblok builds its tooling in a way that makes it easy for developers to extend and build on top of it and it's genuinely ready for agentic workflows.
Beyond the CMS itself, Storyblok builds its tooling in a way that makes it easy for developers to extend and build on top of it and it's genuinely ready for agentic workflows.
Headless content workflows have transformed how I design multilingual sites and iterate with clients
What is our primary use case?
What is most valuable?
The best features Storyblok offers include its simplicity, as I can go into there and basically design the content of my website as I build them, which makes it very easy to modify them. There is also nice internationalization.
The internationalization feature helps me as I build websites for multiple languages, and I can basically translate the content of the block, so when a user selects the language on the page, the correct language is downloaded.
The Visual Editor is great, saving me so much time and allowing me to see right away how the content will look. Additionally, the integration with GitHub is excellent; when I trigger the release of the content, I can set it up to trigger a build on GitHub so that it will be built.
Storyblok impacts my organization positively by making it very easy and saving me tons of time to develop; otherwise, I would need to build my own databases with my own CMS, which is not really scalable and wastes time. Now, I can focus on clients, using Storyblok for that.
It helps me focus on other priorities, and while it is hard to tell exactly how much time it saves me, I can focus on the front end now and on what clients want. I can iterate faster and show clients previews, and it is very great.
What needs improvement?
I think it is a perfect tool for me, but it would be nice to have some examples of best practices to set up content there, as I have a lot of freedom, and it is not really clear how to build it from scratch; I may run into problems if I do not know best practices right away.
I think some tutorials on how to build from scratch content for a big website would be great.
I think Storyblok is the best CMS out there; however, I would rate it a nine because there is still room for improvement, particularly with the documentation.
I take off that one point because the documentation and best practices examples are missing.
For how long have I used the solution?
I have been in my current field for four years. I have been using Storyblok on and off for four years.
What do I think about the stability of the solution?
Storyblok is pretty stable.
What do I think about the scalability of the solution?
Storyblok's scalability is great; it is a very robust tool, and I can build reusable components that are scalable, with no issues in terms of performance. I could even build my scalability layers on top of that.
Which solution did I use previously and why did I switch?
While not in my company, I previously tried building my own CMS that worked but was not as robust and feature-rich as Storyblok; I also had to host it on my own. I used something for a little bit, but I forgot.
What was our ROI?
The return on investment helps me scale my business; without it, I would not even exist probably, so the return on investment is huge.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was pleasurable; everything is clear right from the get-go, and if I need to change anything, it is free that I can use.
Which other solutions did I evaluate?
I do not recall evaluating other options as it was a long time ago, but I did, and Storyblok was the best option.
What other advice do I have?
I advise others looking into using Storyblok to start using it; it is easy, but you need to be careful and design how the content should look like beforehand. Maybe do not start with your own CMS; just use headless Storyblok. I would rate this product a nine out of ten.
Effortless Website Building for Everyone
What do you like best about the product?
I appreciate how easy it is to use, with a quick setup and convenient drag-and-drop functionality. You don't have to be an expert in HTML or CSS to create your own website. Changing images and text is simple, and you can publish your updates directly to the site. Overall, even those without any web design experience can get started and build pages with ease.
What do you dislike about the product?
At times, I find myself wishing there were additional blocks available to enhance my design options.
What problems is the product solving and how is that benefiting you?
Our entire team finds it simple to write and publish blogs, as well as make quick updates to our Shopify website whenever needed.
Flexible, Scalable, and Empowering for Content Teams
What do you like best about the product?
Storyblok’s component-based, headless architecture gives us the flexibility to structure content exactly how we need it, while the Visual Editor empowers non-technical users to make changes safely and efficiently. It scales well as requirements grow and keeps both development and content management clean and maintainable.
What do you dislike about the product?
Some of the more powerful features require developer input to set up correctly, so non-technical users may need guidance early on before everything feels intuitive.
What problems is the product solving and how is that benefiting you?
Storyblok removes the limitations of traditional CMSs by separating content from the frontend. This lets us iterate faster, reuse content more effectively, and empower non-technical users to manage updates without developer involvement.
Effortless Setup, Powerful Developer Tools
What do you like best about the product?
I like the 'what you see is what you get' editor in Storyblok as it makes the content editing process intuitive. I also appreciate the good API and tooling for editing content, which enhances the user experience. The partner portal is another standout feature for me; it makes the initial setup very easy—just a few clicks and it's all set up, allowing us to kick-off development smoothly. The good developer tools and documentation are also valuable resources in our implementations.
What do you dislike about the product?
None
What problems is the product solving and how is that benefiting you?
Storyblok offers a good partner portal, developer tools, and documentation. It features a 'what you see is what you get' editor and strong API and tooling for content editing. The initial setup is straightforward with just a few clicks, allowing us to quickly kick-off development.
Fast, Flexible, and User-Friendly CMS
What do you like best about the product?
I find Storyblok to be an easy-to-use website content management tool that gives us flexibility and speed, allowing us to set up content independently. This means we can launch updates faster without heavy developer dependency and control our website within our ecommerce business team. It's also easy to make localizations across markets. I also appreciate how easy it is to upload content, and how straightforward the initial setup was. Everything about it just works well for me.
What do you dislike about the product?
Sometimes there are bugs and deployments are erased.
What problems is the product solving and how is that benefiting you?
Storyblok is an easy-to-use content management tool. It gives us flexibility and speed, allowing us to set up content independently, launch updates faster, and manage our website with our e-commerce business team. It's also easy to make localizations across markets.
Flexible Content Management with a Learning Curve
What do you like best about the product?
I find Storyblok great for projects across my company, including an eCommerce platform, a PLC site, and an educational site. I appreciate how it solves the reusability of components, making it easy and effective for content editors to use them. I like that it's like a sandbox, allowing flexibility to tailor it to my needs, such as deploying over 20+ domains using one space. The folder-level architecture and restrictions make this possible, and I find that very valuable.
What do you dislike about the product?
Copying and pasting the contents is easy if you are using one space per project, but we need to manually copy and paste contents in the folders as we cannot use the dimension app. Another thing is the commercetools app; it is not possible to add multiple markets to the same space, which causes problems. Also, the onboarding made us a little bit nervous since there is less walkthrough for developers.
What problems is the product solving and how is that benefiting you?
Storyblok solves the reusability of components, making it easy for content editors. Its folder level architecture allows deploying over 20+ domains efficiently, although copying content manually across folders is a downside.
Powerful, but worth its price
What do you like best about the product?
For our developers, it is very straightforward to program with it. Our editors also find the operation easy.
What do you dislike about the product?
Storyblok unfortunately pursues a very expensive pricing strategy in the enterprise sector, which used to be significantly cheaper. The support could also be improved.
What problems is the product solving and how is that benefiting you?
We are implementing a headless e-commerce system that offers very good performance.
Empowers Non-Tech Teams with Ease
What do you like best about the product?
I use Storyblok for managing our website, and I really enjoy its ease of use and the intuitive UX/UI. It's very straightforward, making editing and creating super easy. I appreciate how anyone on the team can jump in, create landing pages for campaigns or content, and work on things together without needing technical knowledge. The ability to easily create content, duplicate website pages, and pause them as needed has made our team more efficient and saved us time.
What do you dislike about the product?
The asset limits are sometimes too low for the package it offers. Also, it can be a bit of a pain in the backend for the technical person to sometimes configure the elements.
What problems is the product solving and how is that benefiting you?
Using Storyblok, our team can manage website changes without needing technical support, which boosts efficiency and saves time. It's easy to create and duplicate pages, and the intuitive interface makes it accessible for everyone to contribute.
Intuitive and Effortless Website Management
What do you like best about the product?
I find Storyblok really user-friendly and easy to navigate, which helps us keep our website up to date. I like how intuitive it is and that it's easy to make updates. The initial setup was extremely easy. I also really appreciate that all changes update quickly.
What do you dislike about the product?
I haven't had any issues with Storyblok.
What problems is the product solving and how is that benefiting you?
I find Storyblok user friendly and intuitive, helping me easily navigate and keep our website up to date with no complaints.
showing 1 - 10