Kontent.ai Reviews & Product Details

The .NET API is great. The magic of DisplayFor in your model where it auto renders all the nested content models is a huge time saver.

No integrated search in the platform that can be used by consumers of the content. Third Party workarounds are required.

Management all website content.

I like that the content management app is really nicely done. There is the flexibility of creating your won blocks, there is i18n, templates, and great tutorials. SEO covered too. Kentico Kontent is so robust that I don't see that anybody can compete with it.

There is some work needs to be done in order to lunch your website. But much less than in other cases.

Content versioning, verification and releasing. Getting content from the single place into any other platforms

We're using Kentico to handle content and more. To preserve data from business logic in the current system that has no other space. In case of change in technical requirements it is very easy to expand / update the existing structure. And teaching end-users (editors) what is to be done there is also very easy.

Some features are still needed to maintain data integrity in business-level projects, where data validation is necessary to automate. It includes unique verification rules, additional field constraints options, etc. What also amazed us is that the measured traffic includes access to property.

You can begin very quickly. Kentico Kontent has a simple user experience and a distinct gui. I obtain fast and useful responses every time I contacted technical support. And the reliability and availability of APIs have never been problematic. The key questions are answered in the documents and many design tools and SDKs are available to ensure a smooth development process.

Four things: Content creation and collaboration capabilities - easy to set up custom workflows. Content ecosystem hub unifying content silos - training users only on a single system and having content only within a single spot. Multilingual support. On the technical side the well-documented API allowed us to integrate in almost no time.

Nothing, in particular, it does what its meant for.

Increasing engagement and interaction of visitors.

Really easy integration to all of our services and apps. Delivery API libraries makes the integration really fast.

I miss the option to use SSO (Single Sign On) with the Professional version of the Kentico Kontent. However it is included in the Enterprise package.

Unified access to the same content without the need to duplicate it across multiple solutions. We do not need to set up complicated infrastructure to start using the Kentico Kontent.

The speed of content entry and the flexibility of content assembly.

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!

The two main areas we have utilised Kentico Cloud are: 1. Componentised content-managed websites where content needs to be structured but easily assembled into rich, engaging website pages. 2. Omni-channel digital experiences where structured content needs to be delivered to multiple channels easily

The whole platform is fast and responsive. Creating the content model is a breeze, it's a pleasure to use. It allows non technical users to get up and running in no time. I contacted support a few times with very specific and semi technical questions and they responded within minutes, the best customer support I have worked with. I also contact support with a feature request and after an approval flow it was implemented and I can now use the enhancement in my project. The documentation and examples are very well written and allow you to work on integrations like webhooks without wasting time on trying to figure out how things work.

It would be nice to have a personalization engine / rules, on the other hand maybe it's good if Kentico Cloud sticks to it's core business, offering a very good headless CMS

Speeding up go to market Delivering a CMS at a much lower cost Offering a user friendly platform to marketers Completing integration with other platforms using webhooks

generic items as childs vor content are extremly useful

the visual design could use some improvement

Marketing content, structured data whicj has to be changed and manualy put in

Ease of use in configuration, as well as ease of use for data entry.

Lack of connectors to other CMS solutions.

Headless CMS. Platform for managing content creation.

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.

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 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.

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.

- Endless component reuse possibility - Manage multiple projects within different environments - Customer care service that is prompt to answer and dedicated to find solutions that suit the customer - The CMS is customizable in the back end and front end - It comes with bunch of features - It is easy for the PM to assign tasks and collaborate with various stakeholders at the same time - Setting up the workflow and project monitoring features - The must is the AI feature that comes along, and this is an add-on to the content creation process - Easy to connect with the different APIs

For now, I don't have any issues to report, but I do like the fact that the team's continuously make efforts to improve the user experience with the addition of new features, active feedback listening, and also with UI improvements.

In my journey as a Digital Content Lead, Kontent.ai has helped me manage and build content for all our 30+ brands. With Kontent.ai, I'm able to manage all the content production processes and collaborate with team members in real time by assigning tasks efficiently, creating workflows, and monitoring live projects. Kontent.ai has simplified handling multiple pieces of content across various web environments and improved collaborating with several amount of stakeholders including developers, graphics, creatives, and SEO agencies. This CMS platform has significantly improve the content creation flow and journey at American Bath Group.

Kontent.ai being headless and API first definitely has a major advantage over other monolithic systems by using its "microservice architecture" and giving an experience that is fast to compose and deliver to channel visitors.

Adoptation to headless and getting clients to understand what "headless" truely is and what it can do for them can be a struggle. With a headless system this does put the responsibility onto the client and/or systems IT personnel to maintain several front facing platforms and tools vs one platform update. However, I do beleive this task is outweighed by the advantages of headless being omnichannel.

Most of our customers that require or will benefit from a headless system typically have multiple in house systems that needs to be accounted for when designing their new digital solution. Kontent.ai allows an easy and seamless integration into many current client CRM, ERP, or eCommerce systems.

I love how easy it is to customize components as much as I need to. I use Kontent as a headless CMS with Next.js and the API is easy to configure, with a quick response time and efficient filtering. I was also able to add a Cloudinary integration in a matter of minutes which is a nice bonus for my use case.

Not much I can think of. Maybe a bit more typing on the JS SDK, it would be nice to have extended types for components containing other components instead of "Elements.RichTextElement".

We need to have all of our pages editable by multiple people in the company, while not taking too much bandwidth from the web dev team. Kontent is the perfect solution as we're able to reproduce the shape of every component of every page easily (using content models within content models) and to build the entire website with content coming from Kontent. With the Next.js tech-stack, we don't even have to rebuild the website every time a change is made in Kontent, it's instantaneously available. We are also able to translate the website into many different languages quickly that's a big plus for us.

It's easy to use. It has a wealth of learning documents, tutorials and E-learning courses. The support is amazing online chat works great always someone on the line to answer nearly instantly.

Haven't found any downsides yet the marketing team and the developers love to work with it.

They solved the problems we were having with multi-language and multi-sites of course this greatly reduces the cost of the platform for a medium-sized company like ours.

Kontent.ai works with so many different tech stacks from .NET, React, Angular, PHP, Android, etc. The Developer documentation is robust and getting started with the solution is very easy. My experience with the AE working with our company was phenomenal as he was incredibly responsive in helping get all our questions resolved. Additionally, the ability to utilize the developer mode for free during evaluation allowed us to create a solid POC before moving forward.

I would love to see additional integrations formed with 3rd party vendors. Currently, the library of integrations is limited, however, I suspect this will grow as the platform grows in popularity. More of a personal grip that is not a major issue but I dislike the name. It is difficult when talking about the CMS internally as the name is Kontent but sounds like "Content" which often can confuse. We have been calling it Kentico.

Kontent.ai is solving the problem of too much architecture required by traditional CMS systems to function. Additionally, headless deployment is often more secure and much faster OOTB compared to traditional CMS solutions. As our business grows we will utilize the system to expand beyond the web into other mediums.