Kontent.ai Reviews & Product Details

I love the organization of content, especially the way the nesting works, the reusability of assets and the User Interface.

Being able to add keywords on a smaller scale would be really helpful, especially for big projects with a lot of assets.

We're using Kentico for our online learning platform, as well as a chatbot and our company webpage.

Kentico cloud is continually adding features that help improve our time to delivery. The quicker we can share our content and continue to improve how are content is delivered to our customers the happier we are with our decision of going with the Kentico Cloud solution.

Lots of ideas to continually make my life easier within the kentico cloud CMS. Customer service has been great at communicating when feature work is being completed but I of course always want more, quicker. But that's always going to be a challenge.

Multiple content managed websites with multiple users of all different skills and goals. We can work quickly to spin up new websites, the user experience within Kentico Cloud is easy to use and train on, plus it is continually being enhanced.

We've been using Kentico Cloud internally and with our customers since its initial launch. Kentico Cloud provides an easy-to-use, content development environment which has provided us with a standardized templated way to gather content and work it through the typical development processes a website build goes through. One of the things that is very big in the web world these days, is keeping content pure and simple, while creating complexity of design and action through external components such as CSS. Kentico Cloud gives us the mechanisms to develop those interfaces and create a consistency in content delivery across our various applications.

Where Kentico Cloud is great, it is quite a deviation from the typical way content is managed in a traditional CMS. Where this has its advantages, the onboarding time for content creators, editors and approvers is more significant because you have to create a paradigm shift in their understand on how to work with digital content...especially working with it outside the context of a site design, etc.

One of our first applications of Kentico Cloud is still one of our best uses...as a content development system. We often use it when migrating content during a site redesign. The content that will be migrated or created are put into a consistent format, giving content editors a chance to focus on the content development vs. hung up on the design processes.

Kentico Cloud has a great sdk that makes it super easy to implement

The CMS UI could use some help with tables, but otherwise meets my needs.

I was able to convert an existing Wordpress site over to a Kentico Cloud site for a client. They now have fuller control over the look and feel, while still maintaining the ability to manage the content on their own.

Defining content types, authoring the content is very clean and elegant. Easy to use Workflow, and Publishing options.

1) Unable to define Base Content for Content Types 2) Custom User Interface Controls in Content Authoring

Define content once and use it across multiple front-end applications including mobile apps. Saved a lot of time and avoid duplication.

Kentico Cloud offers a simple and easy to use interface for content owners to do their work concurrently with website development. As a developer, I've found the API for Kentico Cloud is robust, well documented, and easy to implement. Using the offered .NET Core packages as the underlying technology has been a success and feels relatively future-proof at this time.

There are some instances where the content entry options are a bit limiting for content owners that are used to the full-fledged editing experience offered in the Kentico portal engine. The overall editing experience also just looks and feels somewhat different than what has been offered in Kentico, and content owners that have done things the "old" way for a long time, generally have needed a little training to update their skillset.

We have seen a decrease in overall project length as a result of removing the dependency on initial site development in order for content entry to begin. Once the initial content types are defined, content editors can begin their work right away. On websites with hundreds or even thousands of pages, this cloud-based process can take a significant amount of time and having the content process get off to a quick start is a huge win for all involved. The decoupling of the data layer from the presentation layer also offers long term advantages, in that it allows future web projects to use the same data, but have the build change to the latest and greatest technologies.

The approach somehow resembles Kentico EMS and this makes Kentico EMS users almost right at home. The user interface is fast and easy to use. The creation of content types is easy through the drag-and-drop functionality. It can be easily integrated with different technologies. Also, the new features lifecycle is short and agile making it a very fast-changing product.

I think that the pricing structure is simple and the first price level might be considered as expensive for smaller installations. Other than that I would love to see some options when adding assets. The single level might be a problem for a large number of assets.

Kentico Cloud can be easily deployed making it a great start for having a headless CMS installation. The fact that the content is cloud-based removes the hassle for administrators to maintain an extra database/system for content management. Since it works with multiple development environments it can be used to deploy multiple types of application ranging from websites to mobile applications.

As a full stack developer a tend to give more value to how much effort is needed to integrate into additional platforms. Easily configured webhooks, well documented and easy to use feature rich APIs makes Kontent.ai one of the most enjoyable platforms to create integrations for. With minimal effort I've been able to create an automatic translation service, an Algolia indexer and a few other integrations. In all cases the ease of implementation of Kontent.ai's suite of APIs was the least painful aspect. It's truely a joy to develop for. It's GUI is simple yet powerful and I haven't heard any negative remarks about Kontent.ai from the contents I've trained on the system.

I'm not the biggest fan of their payment model and wish some aspects could be increased or decreased based on needs. It's easy to have content model bloat or overly complex models because of variations. I wish there was a way to conditionally show or hide certain content model fields and content models.

A centralized source of content that can be served on different platforms. Ability to create new capabilities around content.

The simplicity as well as the experience when you're on the platform. Everything is easy to find and navigate to, and their knowledge base is full of valuable information. Their support is also rapid and has always provided a stellar answer.

So far, I have not been able to find anything negative, what I expected to work is working as it should. I cannot think of any improvements that need to happen.

We have efficiently created multiple websites in only a couple of months that would have taken us years to do in our previous platform. The price point is also much better than what was out there on the market.

Well thought out UI, searching and filtering content is easy, robust workflow tools, and plenty of documentation when starting out. Content types and items are easy to build and Web Spotlight provides a visual representation for users who are more design-focused.

Unable to get advanced asset management without adding more to your subscription.

As with many headless solutions, one of the main benefits is the flexibility to use whatever technology is required for the project. We were able to get content creators up and running in parallel to design, speeding up the process of the build.

It's super easy to have a running start.

The pricing can be prohibitive for some.

Moving to a headless, or Content-as-a-Service (CaaS), digital infrastructure model has undoubtedly accelerated our clients’ digital transformation. The ability to utilise the same content across multiple endpoints has been a game-changer for several brands that we work with. The pandemic has meant that communications and operational activities are increasingly having to happen in digital spaces. As a result, the efficient delivery of content to different audiences, and through different channels, has become even more critical to maintaining and increasing customer engagement. Utilising Kentico Kontent as the delivery tool for one recent consumer-focused brand meant we could fast-track development and deliver the entire digital product inside three weeks. It’s not about working harder when thinking about switching to a headless or CaaS model, it’s about thinking smarter and leveraging the opportunities on offer.

Slick UI, simple to set up for content distribution to various platforms, easy to integrate into existing systems

At the moment, I don't find any feature or functionality lacking in usual use cases. The previous versions have been greatly improved and I'm not having any dislikes about the product at the moment.

Separating content from the integrated system, allows distribution of content to hundreds of environments with small amount of effort needed.

Support was pretty responsive, core service works well and is fast. API is powerful.

API documentation could be better. The system for managing multiple environments with the CLI tool for migrating between seems half baked. I got stuck in a spot where I basically needed to swap my "Development" and "Production" environments and had to write fragile code to migrate from one to the other.

Content management. Benefits are that our client had direct control over the content which meant we didn't need to slow down to get approved copy or content.

The opportunity to do online content marketing in 24 countries/languages in an efficient and structured way.

We are working with a lot of content types, which makes it sometimes hard to find the content you are looking for.

Thanks to Kentico, we have managed to move content marketing from a global level to local level. The marketing departments in all our countries are able to create or edit their own content.

Easy to use fast interface with the features that keeps improving.Easy to split the workload between editors, great tools for commenting content and discussing required changes. Very well implemented notification system.

Lack of WYSIWYG editor. Better developer support. Content Management API could be improved. Bulk actions could be improved. User management within a single subscription could be better.

Duplication of content if the client has more than one solution, scalability to large amount of environments. Having a Cloud solution allows us to work with multiple platforms, such as web and mobile. Splitting of the workload between editors, and providing them with a simple to use Solution for entering content.

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 features, so that everything works perfectly, this allows executing the final instances of these projects, in this system, and make known its operation to those interested, without having any external inconvenience, which may affect the presentation of an application, website, or the project that is.

very limited customization of the interface and the characteristics of the application, you should work with what is developed, and if you need to modify something, you just cannot, the internationalization of this platform is also somewhat limited, sometimes you need to work in other languages, or show projects, in a different language, and this is not fully developed.

We can create all kinds of content, in this system based on the cloud, avoiding spending money on special equipment, here we can develop all kinds of content, and execute it without any inconvenience, in a secure environment without complications, besides being in the cloud, the information will be more secure, and losses can be avoided, caused by some hardware problem of a physical equipment.

I like the best the fact that developer can quickly implement features that end user can then enjoy

Lack of support for older versions as soon as new version comes out

Separating of functionality from data, quick integration and powerful user experience

User experience and easy to find all the necessary tools.

Sometimes when editing, UX is bad for deleting items because there is no clearly displayed message for that action.

Easy setup and content separated from software "things".

The structured way that information is held within Kentico Cloud is great and makes finding content is easy. Adding new pages, or other content is straightforward and easily navigable. In addition, the ability to use the data in any number of ways through the API is beneficial as it really allows the user to choose the nature and language of their application without being tied in to a particular service.

Although the content is easily navigable and structured, I feel that it starts to become a bit cumbersome when the amount of content becomes quite large.

We built our new website with Kentico Cloud, allowing us to keep the concerns of managing data and managing the frontend implementation separate. This was great for members of the team with minimal knowledge of frontend technologies to enable them to update the website with our dynamic consumption of the content through the API.

We selected headless CMS, because in terms of the steps to get started with designing the content types and content population, it was certainly quicker as a starting point. We did not have to install traditional CMS somewhere or get too deep into page types and their setup. Kentico Cloud enabled the content population to start day-one of the project. There is a wide range of SDKs available for all major platforms.

The solution is still maturing and the content authoring experience could be improved.

Enabled the rapid development of a dynamic Vue.js website, with the ability to scale further as required,