Kontent.ai Reviews: 4.3/5 — Solid Choice

User interface is good. Available features covered all of our use cases. They also seem to be actively working on even more features and are impressively responsive to feedback.

There's not a whole lot I dislike about Kontent. The JavaScript SDKs I've been using are alright and are improving consistently. Perhaps more security features for asset management would be nice.

Headless CMS, so we solved the problem of being able to manage the content of our website easily, without having to change the code. We can also manage content and languages for multiple regions.

Kentico Kontent is a great headless CMS tool that is easy to use for our business clients. Our development team can help our business create their content structure and model so that all they have to do is go in and enter their content, review, and publish when they are ready. Very quick and easy to learn, even for the not so tech-savvy users.

There are still some limitations in Kentico Kontent. One that has bothered our business clients is the ability to add images in line with text (like in a newspaper article).

We are able to give the power to our business clients to be in full control of their content and when they want it to be published. This allows our team to focus more on improving the solution and the website features.

I enjoy how seamless and overall User Experience design of this CMS. It is easy to follow and has consistent functionality. In comparison to other competitors, it has better technical support and overall layout.

I don't particularly appreciate how the URL slugs do not generate properly, and some features do update in real-time in the environment. I would like to see more tips within Kontent to engage the user.

We are bridging the gap between non-technical audiences and using a CMS for content creation. It is beneficial because we can improve their user experience with their feedback, and Kentico makes changes easy to implement.

I love the spotlight concept, allowing you to view pending changes real-time as if it was on the website.

I dislike that you can currently not create environments via the public api. However, I do know this is now a work in progress.

We are decoupling content from the website code, allowing new content without continuous development & following a change procedure.

I like the visual aspects of the software and how I can find things by looking at the website page and then choosing to edit things from there. In competitor's software, that isn't always and option.

I don't love that I have to go in to tiny image websites and reduce the size of the file, perhaps in the future this could be automated by Kontnet when users upload images.

We are solving the problem of allowing the marketing team to make edits on their own vs. developers, therefore allowing the marketing team to be more productive and be able to make changes quicker.

It makes for great workflows and collaboration.

Not a lot to dislike - they've been consistently improving the product.

We've reduced complexities tenfold, making migraines a lot less frequent across several product teams.

Ease of use for content editors, in-page editing of page content, great APIs, and customization of the CMS. Great consulting team and support from the sales team during product selection.

Subscription level pricing and metrics have changed at short notice. This means that pricing comparissons have to be re-checked before purchase to save unexpected surprises.

Deployment of a single enterprise content management system across multiple brands and businesses which permits content sharing and granular permissions management.

Web Spotlight is inspired - it means content editors can focus on understanding and editing the content without needing to worry about understanding the complexity of the content modelling.

Content modeling is completely free, you can build the content model any way you like. This is wonderful, but sometimes too much choice is paralyzing. It would be nice to have a better tool for moving content types and changes to content types between projects (and environments within a project).

We're moving content from an outdated self-hosted CMS to an evergreen cloud headless CMS, we're getting benefits from the performance and the simplicity of creating new environments for development.

The user interface is very user-friendly and self-explanatory. Many features (notes, comments, tasks, etc.) simplify collaborative writing. The documentation is very detailed and helpful.

Kontent is still a young headless CMS. Currently, e.g. the taxonomy handling with multilingual websites is still suboptimal. Presumably, the feature will follow shortly.

The flexibility that Kontent brings with it through the headless approach allows it to react quickly to new marketing needs.

I love the support, the API output. THe user experience

There is no way to force default values for instance. Content item fields could have more options.

Currently working for a client migrating their platform to Kentico.

Easy to use interface, Preview Option is fantastic

Lots of options should be grouped in categories

We have used for our ecommerce portal, it is very easy to manage static pages and static content inside the application

Having worked on various CMS over the past 20 years, Kentico's flexibility and modularity really stands out for me. It allows us to create a wide variety of pages for different content. The workflow steps are a great feature and allow us to allocate tasks to different members of the team as is the Project Overview function, allowing us to manage workflow.

Searching for asset folders as oppose to the files themselves would be a useful function. Similar an undo function for when you accidentally delete content or similar.

Building organic traffic is the number one target for us and Kentico has allowed us to do this quicker than many other CMS thanks to its flexibility. We are creating various types of content, from reviews and guides to news and top 10 lists. Having a large team working on different types of content brings its own challenges but the workflow steps and project overview helps with managing content and deadlines.

the UX of the product is very easy to use. Also, the pricing of the product scales as you use (API first) and provides you with a good headstart at a low budget. Features like user management, content management, digital asset management, and others are pretty useful and help get the job done. the integration ecosystem is quite solid and reduce your effort, cost & time to market.

we can't create separate groups as part of a single project with roles and responsibilities at a content item level. this limits global organizations with multiple roles in a multi-brand setting. please be vary of these things as this might impact your implementation and vision in the longer run.

My client had an old knowledge management system with no content management capabilities and a new experience layer. they were looking for a headless CMS which could manage a multi-brand ecosystem. Kentico Kontent matched their requirement with great features and functionalities at the right price point. I would highly recommend everyone to check out the product.

All sections are accessible in logical sequence & easy to navigate. Errors are usually advised before you can even preview your changes, this saves time. Even a team member with no previous experience could be easily onboarded to help with content, etc. for website - This was beneficial as working product was produced during limited timeframe. Format allows for visually impactful working website + easy to update as needed in future.

In some sections, it was 4-clicks to edit or same to publish. Understanding this is due to being down a few layers on the page, might be helpful to have a short cut?

Updating and maintaining our website, collaboratively between Corporate and Opco levels. Having a shared, easy to use platform that reduces onboarding time for team members to contribute while working under tight deadlines.

Kentico Kontent is a straightforward platform that makes it easy for content editors to create, edit and collaborate on different types of content. At the same time, the platform is easy to set-up from a technical standpoint, with easy to configure content models and a wide-array of of SDKs to help you handle data fetching, data migration, backups, ect... This is on top of the amazing Kentico support team, who are always available to answer any questions you might have.

Some of the initial hurdles we struggled with when implementing our new website Kentico Kontent had to do with migrating sections of the old site that were very dependant on the tree-hierarchy model we were used to seeing in more traditional CMS. At the time, the platform wasn't well set-up to accomodate this requirement given that it fully embraced the Headless flat-hierarchy approach to content structure ( i.e it was hard for content editors to visualise the whole sitemap and see how pages could be nested below one another). Since then, the platform has made significant improvements in terms of bridging the gap between the Headless CMS and more traditional CMS with features like WebSpotlight.

After having had the experience of being hamstrung by a custom platform with limited support, we wanted the flexibility to choose best-of-breed micro-services and not be locked into an all-in-one CMS. Kentico Kontent gives us the scope to expand content beyond the web and leverage new technology as it emerges. It also provides us with an ideal platform to manage a wide range of content meant for different channels, with great editing and collaboration features.

The ability to simply reuse or duplicate and then amend already created content is hugely beneficial. This saves a lot of time when it comes to the creation of new pages or components and makes it much easier to rollout website update consistently across the website where a component is shared. Kontent also includes a number of collaboration tools which support working with my colleagues as well as my own task management. Being about to come back to a task, add notes and allocate it to team members makes website maintenance more manageable alongside other marketing activities as you're able to pick up where you left off much more easily. The filtering and navigation of our components is also very useful, searching by keyword, narrowing down my selection by the type of component makes it quick to find when I'm looking for.

Within our deployment of Kontent it is not currently possible to preview changes as they are made and publishing the page or component is required - as a result, there have been occasions where further amends have had to be made.

Flexibility and the ability to react to the business demands is the greatest benefit, I am no longer dependent on development time to make a number of changes and it allows me to react faster.

Kontent has a very easy to use interface for building complex data structures. It's easy to use for developers; it's easy to use for business users. I like the fact that there are a pre-defined datatypes available to use, while still having the ability to create custom data elements. The delivery API is very fast and is easy to implement.

I don't like the fact that for rich text content, the only format available is HTML. I would prefer if there was a flag that would allow me to request that content as Markdown (or something like that). It also feels like the JSON response from the delivery endpoint is also larger than needed.

We were trying to decouple the content that was being created from the display of this content. Kentico Kontent allows us to define all of our data / pages in one location and then allow the web developer to display this as desired on-screen. Content editors can change the content at any point without worrying about code; developers can write web applications against a well defined API and not worry about the content.

Its formidable administration tool is cooperative and easy to use, highlighting some of its multilingual functions, which is what I like the most, since it promotes development in economic operations in different languages, contributes to the complete life cycle of some content particularly from my company, intuitively includes a well-documented delivery API and an integration of any stack system from any digital experience with it.

It offers an unprofitable subscription package for small projects, analyzing that it is not suitable for organizations with low labor performance, considering its high cost of starting the software functionality that even medium-sized companies cannot pay the necessary requirements for the process of operation, and finally we can highlight that kentico kontent does not have electronic data forms, which makes its management of notification information somewhat vulnerable.

it is effective for our company, since it offers a content solution that provides all organizations with a life cycle, it has a highly complex system, which performs the necessary services, since it allows the marketing experts of our company to focus more in its creation of experiences in attractive lines due to its forceful or rather easy administration tools, certifying a good result in a general sense, we can mention that we also use it to index documents and customizable models.

Love how flexible it is to use the product. Right now we are using it only as a headless CMS but will soon be expanding into the other integrations. The pricing is straight forward. One thing the team liked is how the content is organized into one giant pool. The SDK was easy to work with and provided us flexiblity to cache results in our own CDN to reduce billing on there platform

There is not much I can think of off the top of my head. Overall after pre-sales we did feel a little rough hand off between our account manager and sales staff.

We were looking to get on a stable hosted SaaS headless CMS platform. Our old headless CMS was a self hosted open source project which was unable to keep up with bug fixes and cost us a lot of labor during upgrades to there product. The old product had quite a few bugs which did not allow the business to manage content on there own. There was also not a defined workflow or approval process

The speed and ease of development, coupled with the ongoing features being added make Kontent stand out. The development team leading in areas such as SSG's is also impressive. Scaffolding projects for smaller clients is absolutely rapid, and there are now features that allow you to scale out these projects more rapidly. The roadmap has also helped me plan for what is coming and allow me to better compare it to other competitors. The API has also been easy to use, both when developing new tools, or using it directly. We have used it both in JS and .NET and both experiences have been top class in comparison to others.

It feels like a walled garden for the best features. The enterprise level of $999 is understandable, but extremely expensive in comparison to other competitors. To be able to unlock enterprise level features by only contributing at least $12,000 a year is just out of reach for many, many businesses. What's more as an early adopter developer, it feels like a slap in the face, as we cannot develop enterprise level features which prevents us from accurately budgeting out client projects without taking out an enterprise plan. Also the number of times I say 'updating content in kontent' is ridiculous and does end up causing confusion with clients.

Quickly scaffolding out sites to allow us to deliver MVPs quicker, whilst also freeing up our text stack to make sure our developers are using the most relevant and productive tools they can. It is also allowing us to approach projects in different ways. For example, we can now look at planning out the future of products at a wider level than just a website, and instead start planning content for multiple platforms in 2-5 years time, not just for the initial delivery.

The ease of use and understandability of the platform. It's very straightforward and I can easily filter the results of what I'm looking for. The fact that I no longer have to exchange emails with attachments. I love being able to filter the results to just my assignments, for example. And if I want to check on a past project, I can search for the title of it. We can assign steps and contributers to a project, so when I'm done the writing phase, I assign it back to my boss, who makes sure the assignment hits the necessary topics. After that, she can easily assign it over to the editor. If the editor needs changes made, he will assign it back to me. It couldn't be simpler.

Formatting a Word document sometimes seems a little frustrating and more confusing than it should be. It also seems like the formatting could be more consistent. I don't understand sometimes why things break the way they do, like a new paragraph versus just another line. Also, sometimes loading time is a little frustrating, or it doesn't load at all.

I work for a freelance company online and I'm able to easily find my assignments from them, and turn them in once they're complete. It's made our exchanges much simpler, as I no longer have to email them attached Word documents, and it's easy to get their feedback right back on the same platform.

Kontent is our leading choice for a headless CMS / Content as a Service platform. Not only are the features great, and ever expanding but there's also great technical support from Kentico development team including best-practice examples available and regular webinars with the product leads. The Kontent development team are open to ideas and are ready to evolve products to a client's needs. We have a great relationship with the whole Kontent who really give confidence in the product.

There's little to dislike with the product, we have seen the development over the past couple of years and most irritating features have been ironed out. As with any service deprecation of features in the past has caused quick reassessments of the solutions for sites but the Kontent team are on hand for advice.

Building websites within existing marketing infrastructures can be problematical, Kontent is helping us solve use-cases where we need to integrate with many other SaaS platforms rather than replace them with a monolithic CMS application. Quick, agile content creation scenarios are facilitated with the product as well, where our geographically separated teams contributed to the production of the website content.

There are many CaaS products out there in the market with all of them offering similar feature sets. Kentico Kontent stands out as one of the best. The UI is very simple and intuitive enabling editors to get up and running quickly and easily. Great strides have been made by the Kontent team to enhance and refine the selection of APIs plus the plugins and connectors for static site generators (e.g. Gatsby) and GraphQL, enabling developers to make use of the latest and greatest technologies to deliver fast and immersive front ends. Custom extensions have enabled us to collaborate with complimentary systems across DAM, ecommerce and optimisation to produce strong platforms for our clients. The team are highly responsive and their continuous contact and interaction with the community enables them to focus on important features which are quickly delivered.

There isn't much to dislike with the product. Any of the gripes we had with the product have quickly been resolved and the team is very receptive to feedback to plug any gaps. Some work is required on the multiple workflows - a requirement sought after by enterprise clients. While there are ways to achieve the same result, a simpler feature is an essential.

For many of our clients, legacy systems have become unwieldy and limitations on omni-channel delivery and performance have forced clients to begin the lengthy process of digital transformation. Kentico Kontent has been key in helping to support the transition to decoupled architectures, often beginning with smaller projects before moving into wider adoption. The flexible nature of the plans enables us to spin up smaller sites and proof of concepts before scaling out across digital landscapes to transform the channels used by the client (and introduce new channels). The separation of content (and CMS functionality in general) from the presentation layer has enabled us to embrace the modern tech that our bespoke digital products have been utilising for years, delivering big wins in performance and SEO across our client base. Most importantly, the use of Kontent and the architectural approach it brings delivers wider-reaching cost-savings across development, infrastructure, maintenance and scalability.

How quickly you can set up a website with a full fledged CMS.

Lack of asset organization. Also more security features for assets behind login as well as audit history for assets. More options for what to include in development API by status.

Let marketing control easy website updates.

It is super easy to get started. KC has transparent user experience and clear interface. Each time I contacted tech support, I got fast and helpful answers. And we never experienced problems with the performance and availability of APIs. All the main questions are answered in documentation and there are lots of custom tools and SDKs for keeping the development process smooth.

A lot of features are still required which would be oriented to maintain data consistency in enterprise-level projects, where it is important to automate the process of validating data. This includes custom validation rules, more options for fields restrictions, etc. Also what was surprising for us: that access to assets is included in the calculated traffic. This means that image links cannot be included directly on a site with lots of visits and a custom caching should be implemented.

We are using Kentico for content management and more: to keep there business-logic data which doesn't have any other storage in the existing architecture. It is super easy to extend/update the existing structure in case technical requirements change. And also it is super simple to teach end users (editors) about what needs to be done there.

I believe the ability for changes and suggestions to come through and the Kentico Cloud team, always willing to listen to help us, goes a long way. The awesome support and consultancy allow for any additional support that we may require. The plugins that allow us to use static site generators like GatsbyJS really help with the community

I guess the subscription plans that are out there, which hopefully can be tailored to client requirements

The fact we have content friction between the different channels, Kentico Cloud definitely help to resolve this and helps content to be delivered from a single content hub. The

I enjoy how simple the user interface is and how quickly the support team responds to queries.

The fact that you cannot get the asset urls directly and that long names cannot be seen on the minimized linked items.

Dynamic layouts have been solved ( with easy to using models )

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.

- headless approach - training of content managers is really fast during good usability - simple admin menu and permission management - usability!!!! the best thing

- hard to say that from a PM and user perspective, because for your projects it was always perfect and perfect configurable. only thing i found: "filter content" in section content, cant be reduced or minimized to the left. its always visible and i really dont use it in all my projects.

implementation of a white label WebApp and copying it several times => centralized cms content of all projects in different languages etc.

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.