Kontent.ai Pricing Overview

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

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.

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 SDK contains many useful plug-ins which are straightforward to configure. It allowed my organisation to execute our digital strategy with few roadblocks and effective governance.

The pricing model is not ideal - Developer licences should not be limited to 1 month. It is too short of a timeframe to build out prototypes and test the full offering from Kontent.

We are solving the problem of having a "Traditional BAU" approach to enterprise CMS. We are trying to consolidate our content into a single source of truth and then feed it to our various customer-facing outlets.

The flexibility overall and the intuitive nature of the admin interface. It really seems that you have thought of everything!

Nothing, in particular, to report here with regards to feature set and capabilities. I think it'll just be a learning curve as we do more with Kontent. Also, the licensing cost may be an issue for smaller clients or non-profit organizations who are used to a more 'one and done' pricing model.

Distributing content across different ouch points n an organization

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.

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.