Kontent.ai Reviews & Product Details

What I like about Kentico is that you learn how to operate it very quickly.

We sometimes experience glitches and bugs as the software is still being developed.

We take care of our whole website and publishing with Kentico.

Simple and clear application design. There is no need to manage CMS onside (like Liferay portal administration and maintenance) Great technical support.

Missing deletion log, missing tracking changes in Content types, missing possibility to recover deleted Content Items and missing possibility to recover the previous state of Content Types

Content Management: 1. System content (like main system screens in mobile application) 2. Campaign (Marketing) Content like banners, news, ...

The Kentico Cloud offers content, front and back end developers to work asynchronously. What this means for development is that it cuts the development time of a website down considerably. Usually, content development is the hold-up whenever a new site is being created.

I would prefer to have some sort of visual structure like the Kentico Document tree as the main navigation. I understand why the Kentico Cloud doesn't focus on this as many people reuse content all over.

We were trying to solve the speed of development. The Kentico Cloud has helped us with this.

Support requests are answered very quickly and the team are always eager to help. Even when asking silly questions they answer patiently and comprehensively. The platform itself is very robust and easy to use. I especially like the modern interface and intuitive layout.

I found it difficult to create content models around our complicated product catalogue. I don't feel that this is a failing of Kentico but more of this kind of system as a whole.

Our current CMS is outdated, slow, and hard to use. We wanted a more modern solution that allowed us to reuse content across channels.

The smooth interface for the editor and easiness to get started, be it for the content editor or for the developer. The support has been very quick to solve the very few hiccups we encountered with the platform. In terms of performance, we only had an issue once, delaying the publishing process, which has been fixed by the product team. As the CMS is SaaS base, you can benefit from the latest features released by Kentico. You do not have to bother about terrible upgrades. This is a good fit when you need to create digital solutions integrated within a complex ecosystem of systems and information sources, and you need a central system to manage all your (extra) content which can then be easily reused.

The fact the features are not up to par with the current Kentico CMS on premise offering. But we can see on their public roadmap they are going there, the products evolves quickly, and Kentico listen to their customers. In comparison with other major enterprise headless CMS solutions, they lack, at the writing time, a few things (but in their roadmap pipe) to make the full development process around the CMS devops ready (handle schema change at once, automate schema change by code, multiple publishing target) .

We used it mainly to experience the headless CMS capabilities of Kentico Cloud. We ended up creating a bunch of website for a couple of start up companies within our group based on the same web platform, and templates. We could deploy a new website in a matter of minutes. The main benefit was speed, and of implementation, and ease of management. We did not have to bother about infrastructure anymore.

The initial implementation was quite simple and the responsiveness is great.

Deserializing the JSON objects can be difficult with complex templates. We figured it out, but it took a little work.

We were attempting to get away from an older CMS that was costly, slow, and complicated. We were able to implement the free version of Kentico Cloud with no costs but development, the load times of the sites are drastically improved, and access points for the data are loaded in one place.

Ability to create a custom backend, easy learning curve, cool trial formula. It is fast and reliable. Requests and API are prettyr straightforward

To me it is more oriented towards react, Angular and thos new framework that generate HTML from a Javascript environement. Gap between starter formula and pro formula for little agency like mine

We do not need to settle a whole CMS backend like wordpress for a "small" website where just a few content area needs to be updated

The KenticoCloud platform allows me to resource developers with any background to quickly deliver web properties that can be managed by content authors and managers, without being constrained by issues like, "does this developer have WordPress plugin experience", or "does this developer have experience with OSGI and AEM". KenticoCloud's strong API allows us to use tools, technologies, and frameworks familiar to development staff while still providing a rich editing experience for management of content.

At times very simple feature requests, like adding additional macros to preview API urls, fall through the cracks.

Rich content management and authoring experiences, without architecturally constraining the delivery solution. Our business has been able to spin up brand new web properties several times a month using any of our own delivery solutions using minimal developer resource investments.

1. The roadmap is very clear, and they seem to run on fortnightly iterations in a true agile fashion, so there are very regular feature releases and updates. This allows them to respond very quickly to the community, but also make it clear what longer-term features are in the pipeline. And you don't have to wait for an annual release to get new features - they're released when they're ready as it's a SaaS platform. 2. There are simply no breaking changes as they update the platform. There's no API version 1, API version 2, etc that you should use if you want to use the latest version. It's just Kentico Cloud, and it just works.

Being a cloud platform, there is currently no option to extend or customise the CMS user interface, as we're used to being able to do with old-fashioned enterprise CMS platforms where we are building and deploying the whole code base to servers. Obviously there are pros and cons to this (not having to build and deploy a huge CMS is amazing), but it can be frustrating in those edge cases where you'd really like to make a tweak, but there's currently no workaround, you make do with what is there. I believe they currently have extension support on the roadmap, but it's not currently available.

I use Kentico Cloud to implement exactly the user experience our clients need/want, without being limited by what the CMS platform will allow. A headless CMS lets you focus purely on content and structure, and treat the presentation of the website or app or whatever you're building as its own concern. As for benefits, the main one is that Kentico Cloud allows us to spin up a client's CMS incredibly quickly - literally on day 1 of a project. We can be working on content and information architecture immediately, without having to wait for visual design or development to start. This has the added benefit of the designs actually being influenced by the right content, and not the other way around, and developers testing their work with real content rather than slabs of lorem ipsum and placeholder images. The other clear benefit is that as a SaaS platform, there is no hosting, maintenance, upgrading, patching etc required, and no "build and deploy" required for the CMS itself, only for your presentation. So our code repositories are super small and it's easy to manage continuous integration and delivery pipelines.

We are just starting to use all of the benefits of Kontent.ai. What we've been utilizing it the most for up until now is our image gallery on our website. It's really easy to use and keep things organized.

I don't like that you can't update a photo without having the url change that was associated with it to begin with. If you could update a photo but also keep the same url, that would be nice.

Having a headless cms, and having an updated cms in general. This allows us to have more capabilites within our site that we do not currently have on our old cms.