Kentico Kontent Reviews in June 2025: User Ratings, Pros & Cons

Fast, scalable, and super easy to use

What do you like best? The speed of content entry and the flexibility of content assembly. What do you dislike? Not so much a dislike but we're very much looking forward to some of the features that are on the roadmap. We just want those now! What problems are you solving with the product? What benefits have you realized? The two main areas we have utilised Kentico Cloud are: 1. Componentised content-managed websites where content needs to be structured but easily assembled ...

CMS in the cloud, with features of a desktop application.

What do you like best? Kentico Cloud is an ideal environment, for any developer, it allows you to create all kinds of applications, from different programming languages, which allows you to evaluate all types of projects on your platform, without running unnecessary risks on common computers, here you do not have any problems. compatibility of drivers or software that may affect the operation of projects that have been created, thanks to the clean environment, which has all the necessary ...

Very Intuitive and easy to learn.

What do you like best? I liked how easy it was to pick up and learn. Everything is laid out well. What do you dislike? grabbing links from the assets to post on the website is a little cumbersome due to the fact you have to extract only a piece of the url link when you click the asset. What problems are you solving with the product? What benefits have you realized? Providing a quicker turnaround the the clients for website revisions and articles for the website.

A good start but a lot of work left

What do you like best? The UI Is getting better, good features are developer. Centralization of content for multiple platforms What do you dislike? The API and developer experience is not that polished as the UI and editor experience. The Caching on the API side could be implemented in a better way. Currently the first request to the API is very slow due to cache being implemented in an first access manner. What problems are you solving with the product? What benefits have you ...

Functioned as Needed

What do you like best? Content was well organized. It was relatively easy to find what i needed to find. What do you dislike? Going back and forth from one piece of content to another was clumsy. What problems are you solving with the product? What benefits have you realized? Building a new website and content creation is happening in multiple places. It was a good way to see and share all of the work.

Easy and powerful integration

What do you like best? I like the best the fact that developer can quickly implement features that end user can then enjoy What do you dislike? Lack of support for older versions as soon as new version comes out What problems are you solving with the product? What benefits have you realized? Separating of functionality from data, quick integration and powerful user experience

Fast Implementation

What do you like best? The ability to setup content types without the assistance of developers. The workflow of content. What do you dislike? Management and organization of the content very basic. There are no folders for content, they are listed out in alphabetical order. While you can filter and search pretty easily, visual organization would be more helpful. Recommendations to others considering the product: Seriously give this a try. Working with the content is different ...

Great experience while doing stuff

What do you like best? User experience and easy to find all the necessary tools. What do you dislike? Sometimes when editing, UX is bad for deleting items because there is no clearly displayed message for that action. What problems are you solving with the product? What benefits have you realized? Easy setup and content separated from software "things".

Mixed bag

What do you like best? Nice UI Flexibility with organizing data What do you dislike? Spotty performance API lacks some functionalities What problems are you solving with the product? What benefits have you realized? Sharing content between different sites. Having one centralized place to keep business data. Save costs when translating content.

Quality, flexible product

What do you like best? The REST aspects of the API are solid. It's easy to get started with existing REST experience. What do you dislike? It's hard to navigate the documentation. There are many domains findable by search engines, and it's not always obvious which ones are up to date. What problems are you solving with the product? What benefits have you realized? Kentico allows us to integrate data from our own existing API with content entered by a user in the Kentico UI. This ...