I believe performance-wise, Contentstack can be improved more. I noticed that sometimes it takes time, and I am not sure about the server side, as it may not be responding. We sometimes face legacy issues, but overall it is good, and sometimes the issue may come from the server. I choose nine out of ten because I sometimes face performance-related issues, and I feel that it is a little complex for new users, particularly regarding the dashboard.
Web Developer at a tech vendor with 1,001-5,000 employees
Real User
Top 20
Apr 3, 2026
I majorly work on structuring the CMS on the backend. I feel that we have restrictions on fields. On the backend, we have conditional logic as well. We can display a specific field based on a specific condition, but I feel it is too restricted. We cannot use it with global fields or a modular field. That is something the Contentstack team can address and remove those restrictions. Additionally, two or three months back, I connected with the support team of Contentstack. In the URL field, if we want to add any validation, we do not have that option at the code level or on the backend CMS. We can look at that. We have that field for one default URL, but we should keep that field universally if we want to add a regex-based validation. Some of the restrictions that we really do not want could be optimized further. There are also fewer field options to add. We have JSON RTE, but we should have a raw JSON field as well.
To improve Contentstack, training and examples should be enhanced, and updating SDKs to reflect technology changes would be beneficial. I would highly appreciate additional analytics offering via the API as a needed improvement.
Contentstack can be improved in localization because translation management within the system is difficult and mostly manual. Regarding needed improvements, I would add that license control is also a concern.
Contentstack is a headless CMS that offers a flexible and scalable platform for managing content across digital experiences. Designed for enterprise needs, it empowers teams to deliver seamless, personalized, and engaging customer journeys rapidly.Contentstack enables organizations to manage and deliver digital experiences across multiple channels with ease. It is built for fast deployment, integrating seamlessly with other platforms. Its headless architecture allows for flexibility in...
I believe performance-wise, Contentstack can be improved more. I noticed that sometimes it takes time, and I am not sure about the server side, as it may not be responding. We sometimes face legacy issues, but overall it is good, and sometimes the issue may come from the server. I choose nine out of ten because I sometimes face performance-related issues, and I feel that it is a little complex for new users, particularly regarding the dashboard.
I majorly work on structuring the CMS on the backend. I feel that we have restrictions on fields. On the backend, we have conditional logic as well. We can display a specific field based on a specific condition, but I feel it is too restricted. We cannot use it with global fields or a modular field. That is something the Contentstack team can address and remove those restrictions. Additionally, two or three months back, I connected with the support team of Contentstack. In the URL field, if we want to add any validation, we do not have that option at the code level or on the backend CMS. We can look at that. We have that field for one default URL, but we should keep that field universally if we want to add a regex-based validation. Some of the restrictions that we really do not want could be optimized further. There are also fewer field options to add. We have JSON RTE, but we should have a raw JSON field as well.
To improve Contentstack, training and examples should be enhanced, and updating SDKs to reflect technology changes would be beneficial. I would highly appreciate additional analytics offering via the API as a needed improvement.
Contentstack can be improved in localization because translation management within the system is difficult and mostly manual. Regarding needed improvements, I would add that license control is also a concern.