Xperience by Kentico

Xperience by Kentico supports four content type targets (reusable content, pages, emails, headless items) with a broad set of field types and a reusable field schemas feature allowing shared field collections across types. The Management API MCP server exposes 20 CRUD tools for content types, and AIRA AI-assisted generation is now available for fields defined in reusable field schemas (April 2026 refresh). No schema-as-code option exists — types are UI-defined — which limits parity with headless-first platforms.

Content types support references to other content items including polymorphic references (linking to a large number of possible content types — addressed with a GraphQL query optimization in 2025). Standard one-to-many references with reverse traversal through GraphQL. Not a graph-native platform; reverse-lookup is available but not as ergonomic as Hygraph.

Page Builder provides a widget/section/zone system for composing structured pages. Headless channels support structured content items with defined content types. Component nesting is supported via widget composition in Page Builder. Structured output for headless is GraphQL JSON (or the new Headless REST API JSON in preview) — no native Portable Text equivalent.

Standard field-level validations (required, regex, min/max length, file type) are built in. Custom validation is extensible via .NET code since Xperience is an ASP.NET Core platform. No evidence of a no-code cross-field validation rule engine or webhook pre-save hooks for marketers.

Content versioning is supported across all content types — reusable content, headless items, web pages, and emails. The version history UI allows review and restore of earlier versions. Scheduled publishing is available, including for content sync batches. Preview of Page Builder versions was announced in 2025.

Page Builder provides drag-and-drop widget management described as an 'almost WYSIWYG experience' — marketers can rearrange and configure developer-prepared widgets on live page layouts without code. This is a genuine in-context page editor for non-technical users, though widget types must be pre-built by developers. Not a full freeform visual editor like Webflow.

Rich text editing is powered by Froala WYSIWYG editor (v5.0.0), with inline rich text editors available within Page Builder widgets. The AIRA rich text editor refinements feature moved from preview to GA in the April 16, 2026 refresh, adding AI-assisted rewriting/tone adjustments during authoring. Output remains HTML-based rather than a portable AST, limiting channel portability.

Built-in Media Library provides upload, organization, and basic asset serving with automatic dimension adaptation for different layouts. First-party Bynder DAM integration is available for enterprise asset management. No documented URL-based transformation pipeline (resize, focal point, WebP/AVIF on the fly) in the native library — transforms appear to be layout-responsive rather than on-demand.

No evidence of real-time co-editing with presence indicators. Standard DXP content locking model applies. Workflow step notifications (added 2025) allow async commenting when content moves between steps. This is async collaboration, not real-time co-authoring.

Configurable multi-stage workflows are supported across all content types (pages, reusable content, emails, headless items) with role-based transitions between custom steps. Workflow step notifications with comment boxes were added in 2025. The April 16, 2026 refresh added a broader role-based access control model for the administration UI (applications/pages/UI elements) with a new Role management app and permission evaluation API, reinforcing the permissions underpinning workflow stage transitions.

Each headless channel auto-generates a strongly-typed GraphQL API endpoint for content delivery, with polymorphic query optimization added in 2025. The April 16, 2026 refresh (version 31.4.0) introduced a Headless REST API in preview for retrieving content items over HTTP with JSON responses, closing the previous GraphQL-only gap. With both REST and GraphQL now available for delivery (REST still preview), the API tier moves from GraphQL-only to GraphQL + REST, removing the -5 rubric penalty.

SaaS deployments integrate Cloudflare CDN for performance and DDoS protection. Cache dependency builder (added March 2025) provides granular cache invalidation keyed to content changes. Security events from Cloudflare are visible in Xperience Portal. CDN is SaaS-only — self-hosted deployments require customers to configure their own CDN.

Webhooks exist for content events (standard for a .NET DXP platform). The Management API exposes events for content type changes. However, no detailed documentation evidence was found for comprehensive webhook filtering, HMAC signing, retry logic, or delivery logs in the 2025–2026 timeframe. Scored conservatively as adequate.

Xperience by Kentico is a hybrid DXP — Page Builder for traditional website channels plus headless channels with GraphQL and (as of April 2026) a preview Headless REST API for external apps. Primary SDK is .NET/ASP.NET Core with an official Next.js integration. Rich text output is HTML (not AST), limiting format-agnostic multi-channel portability. Not purpose-built headless like Contentful.

Xperience by Kentico ships a built-in CDP with rule-based Contact Groups, behavioral activity-based conditions, and unified Profiles that merge customers, contacts, and members. The April 16, 2026 refresh extended identity resolution with flexible matching on external identifiers or native fields (e.g., member email), sharpening segment membership across touchpoints. Not higher because firmographic/B2B enrichment and pre-built Segment/mParticle connectors remain absent.

Page Builder widgets support native content personalization rules tied to contact groups, delivering different widget variants to different audiences with in-editor preview per segment. The platform claims 90% satisfaction for personalization in G2 Winter 2026. Scored below 75 because variant-level preview for headless channels is less seamless than top-tier DXPs, and personalization on headless frontends requires code-side integration.

The primary A/B testing path in Xperience by Kentico is via the VWO integration listed in the community integrations hub, suggesting native experimentation is limited. Kentico 13 had a native A/B testing module, but the XbyK platform has not prominently shipped equivalent native experimentation with statistical significance reporting. Scored 45 as an external integration path exists but genuine built-in A/B testing with full analytics is not confirmed.

No evidence of a built-in algorithmic or ML-based content recommendation engine in Xperience by Kentico. Content recommendations would require custom development or a third-party integration. AIRA provides AI-assisted content operations but not audience-facing personalized recommendations.

Xperience by Kentico includes basic full-text search capabilities built on Lucene (inherited from the .NET platform), supporting page content indexing and basic search. The platform's own docs encourage using Algolia or Azure AI Search for production-quality search, implying the native option is functional but not highly optimized for relevance tuning, faceting, or autocomplete.

Official Algolia integration with code-first index creation, page content type indexing, and support for .NET API, JavaScript API, and InstantSearch.js is documented on Algolia's developer hub and Kentico's roadmap. The integration is on Kentico's officially supported roadmap with a 7-day bug-fix policy. Azure AI Search is also a documented integration path. Scored 72 because the integration is well-supported but configuration remains code-first rather than UI-driven.

Xperience by Kentico has been incrementally adding native commerce capabilities: digital commerce discounts (January 2026), product catalog management, orders, and customers are now included. The October 2025 refresh added in-preview digital commerce updates. However, native commerce is still maturing — it entered preview in late 2025, and full cart/checkout parity with dedicated commerce platforms is not yet confirmed. Scored at the mid-range for a DXP platform with emerging native commerce.

An official Shopify integration (github.com/Kentico/xperience-by-kentico-shopify) connects to Shopify via Storefront and Admin APIs, enabling product management, cart operations, discount coupons, and checkout. The integration carries a 7-day bug-fix SLA indicating first-party support. No documented BigCommerce or commercetools connectors were found, limiting the score.

The Content Hub architecture supports structured content types with custom field schemas, making it feasible to manage rich product editorial content (descriptions, image variants, attributes) alongside commerce data. Native commerce features added in 2025-2026 include product catalog management. Scored 58 because product-specific content patterns require developer setup rather than out-of-box product content templates.

Xperience by Kentico includes built-in web analytics covering page views, audience engagement, customer journey mapping, marketing automation performance, email analytics, and content A/B testing data. Power BI integration with pre-built reports provides deeper content performance visualization. The platform also captures contact activity data natively. Scored 68 rather than 75+ because the analytics UI is less polished than best-in-class and relies on Power BI for deeper content health reporting.

Google Analytics / GA4 integration is supported via standard tag management and documented in the Kentico ecosystem. Power BI is a first-party integration. Segment and Amplitude connectors are not listed as official first-party integrations, though Zapier enables connectivity. Scored 62 for solid GA4/Power BI coverage without official deep CDP-level streaming integrations.

Xperience by Kentico supports multiple website channels under a single instance with a shared Content Hub, allowing reuse of reusable content items across sites while maintaining independent page structures, locales, and publishing configurations per channel. The platform is cited in customer case studies for multi-site consolidations. Scored 70 because cross-site shared governance tooling (enforced component constraints, global style policies across channels) requires developer configuration rather than out-of-box brand governance UI.

Xperience by Kentico supports per-language content variants in the Content Hub with locale fallback chains (since v30.9.0, date/time formatting also locale-aware). Marketers can create language variants of content items and web pages from within the CMS. Field-level localization is supported through the content item variant model. Scored 68 because some field-type-level locale exclusions and advanced locale routing require developer configuration.

Xperience by Kentico has a Translations queue application and supports bulk content translation via AIRA for AI-assisted machine translation. An official integration with XTM Cloud TMS is available. Linked item translation and bulk content translation were enhanced in 2025-2026. Scored 60 because XTM is the primary documented TMS connector (Phrase/Smartling/Lokalise not confirmed as official integrations).

The Content Hub provides centralized content governance with RBAC across multiple website channels and headless channels. Shared component libraries (widgets, page templates) enable brand consistency. Cross-channel publishing permissions restrict editor access by channel. Scored 62 because native multi-brand policy enforcement (e.g., enforced style guides, approval gate cross-brand workflows) requires custom configuration rather than being a first-class feature.

Xperience by Kentico includes a Media Library within the Content Hub with metadata tagging, folder organization, asset reuse tracking across content items, and AIRA-powered auto-metadata generation (2025 updates). Image format conversion per content field is configurable. A Bynder integration (official GitHub module) extends to full enterprise DAM. Native DAM lacks versioning history and rights/expiry management of purpose-built DAMs. Scored 58 for a solid asset library with growing metadata capabilities but missing versioning and rights features.

Xperience by Kentico's SaaS deployment includes built-in CDN delivery for assets. Per-field image format conversion is configurable, and the platform generates content delivery URLs for assets automatically. The April 2025 refresh added a copy CDN URL button for media assets. Focal point and WebP/AVIF support are not explicitly documented in search results, limiting confidence for a higher score.

No evidence of native video hosting, transcoding, adaptive bitrate streaming, or thumbnail generation in Xperience by Kentico. The Media Library can store video files, but production video workflows would require embedding from Vimeo, YouTube, or integrating a dedicated service like Mux or Cloudinary. Scored 30 for basic video upload/storage without native streaming or transcoding.

Xperience by Kentico's Page Builder provides drag-and-drop widget placement into configurable sections, in-context editing with live preview, non-technical page composition, and personalization variants per widget. Editors create layouts with section templates and assemble pages without code. Scored 72 rather than 75+ because the frontend is ASP.NET MVC-based so full visual editing of arbitrary headless frontends is not a first-class feature, unlike Sitecore Pages or Contentful Compose.

Xperience by Kentico has marketer-managed configurable workflows with custom steps, role-based authorization per step, and applies to reusable content, web pages, emails, and headless items. The July 2025 refresh added workflow step comments and notification emails for contextual handoffs. Multi-step parallel approval paths are not explicitly documented, keeping the score below 75.

Xperience by Kentico supports scheduled publishing (publish at future date/time) and content sync to promote content between environments. A calendar-style content calendar view is not prominently documented as a native feature in the current XbyK platform. Embargo/expiry and release bundles (atomic multi-item publish) were not confirmed. Scored 55 for scheduled publishing without strong evidence of a content calendar UI or release bundle feature.

No evidence of simultaneous multi-author editing with conflict prevention, presence indicators, or inline commenting in the content editor in Xperience by Kentico. Workflow step comments (July 2025) add team context in approval handoffs but are not real-time in-document collaboration. Version history is maintained through workflow states. Scored 35 for basic workflow-level collaboration without real-time co-editing.

Xperience by Kentico's Form Builder supports custom forms, submission data storage, autoresponder emails on submission, and advanced marketing automation triggers from form submissions. The January 2026 refresh added form field visibility conditions (conditional logic). CAPTCHA support and spam protection are documented features. Scored 68 rather than 75+ because progressive profiling and multi-step form sequences require custom implementation.

Xperience by Kentico has a first-class native email marketing capability with subscriber lists, email campaigns, templated emails, autoresponders, and automation-triggered email sequences. The platform handles email design, scheduling, and list management natively without requiring an external ESP. Scored 65 rather than 70+ because deep bidirectional sync with enterprise ESPs (Marketo, Salesforce Marketing Cloud, Mailchimp) as first-party integrations is not confirmed.

Xperience by Kentico ships a native Automation module supporting behavioral trigger-based flows, drip email campaigns with wait intervals, condition-based branching paths, and lifecycle activity tracking. The January 2026 refresh enhanced automation conditions to evaluate activity type and activity value. Scored 62 because marketing automation is present and capable for mid-market DXP use cases, but lacks the campaign orchestration sophistication and lead scoring depth of Bloomreach or HubSpot.

Xperience by Kentico's built-in CDP now consolidates customers, contacts, and members into unified Profiles with identity resolution. The April 16, 2026 refresh added flexible identity resolution matching on external identifiers or native fields (e.g., member email) to merge profiles across touchpoints, enabling richer unified customer data for personalization and automation. Scored 71 because external CDP connectors (Segment, mParticle, Tealium) are still not official, and B2B firmographic enrichment remains limited.

Xperience by Kentico has a Community Integrations Hub with official and community integrations across search (Algolia), commerce (Shopify), DAM (Bynder), CRM, analytics, and optimization categories. First-party integrations carry 7-day bug-fix SLAs. Zapier provides 6000+ app connectivity. The ecosystem is growing but not as large as Sitecore or AEM marketplaces. Scored 55 for a solid mid-sized integration directory with strong official connectors in key categories.

Xperience by Kentico supports outbound webhooks used in AIRA Lambda workflow integrations, and async global event handling APIs were added to support DI-based event subscriptions. The platform has a .NET event system covering content create/update/delete/publish operations. However, webhook configuration is code-first with no documented UI for topic selection, signed payloads, or retry/logging dashboards. Scored 52 for functional webhook/event support that requires developer configuration without a managed webhook admin interface.

Xperience by Kentico added a dedicated STG (Staging) environment for SaaS plans (May 2025) with content sync to promote content to production. Branch-based preview environments can be configured via CI/CD pipelines. Page Builder provides in-context live preview for .NET-rendered sites. Scored 62 because universal preview for arbitrary headless frontends (React, Next.js) requires custom preview implementation, and shareable external draft preview links are not documented as a first-class UI feature.

Xperience by Kentico supports custom role definition, ACL-based web page permissions, channel-level access control, and SSO integration with Microsoft Entra, Okta, and Auth0. Xperience Portal access is managed via Auth0 RBAC. Content-type-level and workflow-step-level role assignments are configurable. Scored 65 rather than 70+ because field-level permissions and SCIM provisioning for user lifecycle management are not confirmed as built-in features.

Xperience by Kentico provides a GraphQL API per headless channel with auto-generated schemas and a REST API for tracking endpoints. API key security, dynamic caching, and per-channel endpoints are well-designed. The .NET Content Item Query API supports advanced filtering, sorting, and projection. Not higher because GraphQL is read-only (no mutations or subscriptions) and documentation depth is below headless-first platforms.

GraphQL responses are dynamically cached improving performance for repeated queries. 2025-2026 updates added performance optimization for queries with fields linking to many content types (EnableUnionQueryOptimization config key). No published rate limits, response time SLAs, or performance benchmarks found. Not higher due to lack of CDN-backed delivery documentation and no published performance guarantees.

Official SDK exists for .NET only, distributed as NuGet packages (Kentico.Xperience.*). The .NET SDK is well-maintained with typed content access and LINQ queries. No official JavaScript, Python, Ruby, Go, or mobile SDKs. Non-.NET consumers must use the GraphQL API directly without a client library. This limits the platform to .NET teams for server-side work.

Community Integrations Hub hosts integrations from Kentico, partners, and the community as NuGet packages. Official integrations include Algolia search, Azure AI Search, Zapier, Google Tag Manager, GA4, Application Insights, and Cloudflare CDN. Digital Commerce integrations in preview. MCP server and new April 2026 KentiCopilot plugins (KX13 content auditor and AI-assisted migration tool) extend the ecosystem. Total catalog remains modest compared to larger platforms, with gaps in DAM, translation, and general AI service connectors.

Comprehensive .NET extensibility: custom modules with DI, global event handlers for content lifecycle hooks, custom Page Builder widgets and sections, custom form components, and custom admin UI pages built with React. NuGet-based package distribution. April 2026 Refresh adds a formal KentiCopilot plugin model (KX13 content auditor, AI-assisted migration) alongside the existing MCP server — confirming a pluggable AI-agent extensibility surface. Limited only by the requirement for .NET/C# skills — no low-code extension approach exists.

SSO via external authentication providers including OIDC through ASP.NET Core Identity integration. MFA is available for admin users. API authentication uses API keys for headless channel endpoints. SAML support requires additional custom configuration beyond built-in OIDC. Adequate for most enterprise requirements but SAML not being first-class limits the score.

Role-based access control with predefined and custom roles. Permissions configurable at module, content type, and content tree node levels. Per-page permissions provide content-level access control. No field-level permissions — access control operates at the content item level. Adequate for most organizational structures but lacks fine-grained field-level control offered by some headless CMS platforms.

Xperience by Kentico SaaS holds ISO 27001 certification and SOC 2 Type II audit, verified annually with continuous monitoring. GDPR and CCPA compliance with consent management tools. Trust Center provides evidence and policies. Multiple Azure regions across NA, EU, APAC for data residency. Regular penetration testing and security assessments. Not higher due to no documented HIPAA BAA availability.

Significant CVEs in 2025: CVE-2025-2746 and CVE-2025-2747 (CVSS 9.8) are critical authentication bypass flaws in Xperience 13 Staging Service, added to CISA KEV list. CVE-2025-2748 chains XSS to RCE via custom file handlers. Additional DoS and stored XSS vulnerabilities disclosed. Vulnerability Disclosure Program exists but is reward-free. The severity and CISA KEV inclusion of these 2025 CVEs significantly worsens the track record.

Genuine dual deployment: SaaS (single-tenant Azure infrastructure) and self-hosted via standard ASP.NET Core hosting. SaaS customers choose their Azure region from NA, EU, and APAC. Self-hosted supports Docker containers and any compatible infrastructure. SaaS includes STG (staging) environment for any service plan. The dual model provides strong flexibility for regulated industries.

Public status page at status.xperience-portal.com with uptime history. Platform-specific SLAs for SaaS customers. 24/7 worldwide support team with internal alerting. Azure SQL Database high availability. April 16, 2026 Refresh adds extensible SaaS uptime monitoring supporting up to 6 checker configurations across regions, giving customers multi-region synthetic probes for their own uptime visibility. Not higher because the specific SLA percentage (e.g., 99.9% or 99.95%) remains undocumented publicly.

ASP.NET Core architecture supports horizontal auto-scaling with multiple instances. Azure SaaS deployment provides managed up/down scaling with multi-region support. CDN integration recommended in docs for global content distribution. No published scale limits or enterprise-scale benchmarks with specific metrics.

SaaS includes automated daily backups with retention and geo-redundancy to remote storage. RTO and RPO are documented: RTO approximately 1 hour, RPO 1–24 hours. Annual DR testing confirmed. Self-service backups and restores available via Xperience Portal for both production and non-production environments.

Standard .NET local development with ASP.NET Core dev server and hot reload. .NET CLI tools for project setup and code generation of strongly-typed classes. Full platform runs locally with good production parity. Developer Learning Map, kickstart guides, and AI development hub with MCP server available. Not higher because it requires the full .NET stack plus SQL Server locally — no lightweight sandbox or emulator.

CI serializes database objects to XML for source control; CD restores to target environments. SaaS STG environment available for any service plan, enabling pre-production content authoring with production parity. Azure DevOps multi-stage pipelines supported via Xperience Portal API. Branch-based preview deployments supported. Not higher because schema migrations still require CI/CD feature configuration rather than a standalone migration CLI.

Comprehensive documentation at docs.kentico.com with Learn Portal unifying all educational resources. Full API reference at api-reference.kentico.com. Developer Learning Map, kickstart guides, and AI development hub. AI-powered documentation chatbot. Free e-learning for all key roles. Not higher because examples are C#-only, no interactive playground, and no multi-language code samples.

No TypeScript type generation from content schemas. No official TypeScript or JavaScript SDK for content delivery. The admin UI uses React and TypeScript internally for UI customization, but this is not exposed as a developer-facing content delivery SDK. Type safety is provided via C# generated classes in .NET only. Frontend developers consuming the GraphQL API must manually create TypeScript types or use third-party codegen tools.

Kentico has tightened its Refresh cadence from ~6–8 weeks toward near-monthly: documented Refreshes include March, May, July, October, December 2025 and January, February, March 2026, and now an April 16, 2026 Refresh landing back-to-back with March. Each Refresh bundles meaningful features (digital commerce GA, AIRA agents, form field conditions). Not higher because patch-level cadence between named Refreshes is still not independently visible.

The official docs changelog is structured and versioned, and each Refresh has a corresponding community blog post that details new features, developer-facing changes, and breaking notes (the April 16, 2026 Refresh follows the same structured format). Breaking changes are surfaced per release. Not in the 80+ tier because migration guides and codemods are not as automated/prominent as top-tier platforms.

Kentico maintains a public product roadmap at roadmap.kentico.com with 'Released', 'In Preview', and 'Planned' tabs visible to all. Regular community blog posts provide roadmap Q&A and expert chat series. The CEO published a public 2026 outlook. Not scoring 85+ because community voting/Canny-style prioritization is not strongly evidenced.

Kentico has managed the major migration from legacy Kentico Xperience 13 (end-of-life 2026) to Xperience by Kentico with documented migration paths and partner support. Within the Refresh cadence, breaking changes are called out in release notes. No evidence of automated codemods or 12-month formal deprecation windows, keeping this out of the 75+ tier.

Kentico runs a community portal (community.kentico.com) with MVP and Community Leader programs, and active GitHub repositories (e.g., Kentico/community-portal). The platform has ~10,000 customers and 355 G2 reviews (substantial for a DXP), but GitHub star counts are modest given the .NET/commercial nature of the product. Not a large open-source community.

The community portal publishes frequent content (including the April 16, 2026 Refresh post continuing monthly cadence), runs an MVP/Community Leaders recognition program, and held Partner Connection 2025 in Prague. Kentico team members actively contribute to the community blog. GitHub repos show regular activity (KentiCopilot, community-portal). Engagement appears genuine for a mid-market B2B product; response times not independently verified.

Kentico has a formal partner program with certified agencies and an annual Partner Connection conference (Prague 2025). The website lists partner integrations created by Kentico, partners, and community. No evidence of major global SIs (Accenture, Deloitte) at the level of tier-1 DXPs, but a solid mid-market agency network is evident.

There is a reasonable volume of community tutorials, blog posts, and YouTube content (especially from partners), but Xperience by Kentico is not widely covered on Udemy or Pluralsight. The platform is .NET-specific and mid-market, limiting the breadth of third-party educational content compared to larger open-source or headless platforms.

Kentico targets the .NET/C# developer ecosystem, which is large in absolute terms but niche for DXP specialization. A certification program exists, and LinkedIn shows active job postings for Kentico developers particularly in mid-market agencies. Not widely recognized in Stack Overflow developer surveys, limiting talent pool compared to platforms like Drupal or WordPress.

Revenue grew from $20M (2017) to $42M (2024), 10,000 customers, and the platform achieved G2 Leader status across Summer, Fall 2025 and Winter 2026 DXP grid reports. Digital commerce GA in July 2025 expanded TAM, and sustained feature delivery through the April 2026 Refresh reinforces the growth narrative. CMS Critic noted Kentico 'achieves big milestones in 2025' citing AI and Xperience as key drivers. Not higher because logo announcements and case study publishing cadence are not at enterprise tier-1 level.

Kentico is a privately held, largely self-funded company backed by Expedition Growth Capital, with $42M revenue in 2024 and 226 employees. The CEO published a positive 2026 outlook, and there are no signals of layoffs or distress. The company is growing organically and profitably. Not scoring higher because there is no recent growth round and limited public financial disclosures.

Xperience by Kentico holds G2 Leader status in DXP (Summer, Fall 2025 and Winter 2026 reports), Gartner Peer Insights 4.5/5, and Info-Tech Research Group Champion (Composite 8.3/10, NPS +77, 85% likely to recommend). The platform differentiates on ease of use, .NET developer experience, and mid-market fit with integrated digital commerce and AI (AIRA). Not in the 80+ tier because Gartner Magic Quadrant inclusion is not confirmed.

G2 shows ~355 reviews for Kentico with 98% rating 4 or 5 stars and 92% recommending it, placing it firmly in the 75–85 scoring band. Gartner Peer Insights averages 4.5/5. Recurring positive themes: ease of use, flexibility, and support quality. No significant pattern of negative sentiment around pricing or reliability visible in search results.

Kentico publishes a 'How to Buy' page and a public PDF listing SaaS at $1,990/month and self-managed at $990/month, with two tiers (Standard, Advanced). Channel add-on pricing and enterprise customizations require contacting sales, but the base structure is visible. Scores in the 60–65 range for partial public pricing with sales-gated expansion. April 16, 2026 refresh is a product feature update and does not alter pricing transparency.

Fixed-cost SaaS subscription based on pre-defined cloud levels avoids consumption spikes — a strong signal. Channel-based licensing (one main channel included, add-ons for more) is predictable for most buyers. SaaS Resource Upgrades (bandwidth, email, storage) are priced separately but are opt-in. Penalized slightly because multi-channel projects require add-on purchases that may not be transparent upfront.

Standard tier covers single-channel web projects; Advanced tier unlocks multi-channel and enhanced digital marketing features. AIRA (AI automation) launched as a separate add-on in February 2026. Splitting multi-channel and advanced marketing behind a higher tier is a meaningful gate for real DXP use cases, though core CMS functionality is accessible at the base tier. April 16, 2026 refresh did not alter tier boundaries.

Pricing is annual-only ($24,600/yr SaaS minimum, $11,880/yr self-managed minimum). No monthly billing option found. No startup or nonprofit program documented publicly. No exit provisions or trial-to-paid discount path beyond the 7-day trial. Enterprise DXP norm but still penalized for rigidity.

Only a 7-day hosted trial is available; there is no permanent free tier. The core platform is not open source. Compared to open-source DXPs like Drupal or even headless CMS with free tiers, this is a significant gap for solo developers or small teams evaluating the platform. Score reflects trial-only entry with no free-forever path.

SaaS cloud infrastructure is described as ready in 30 minutes. However, Xperience by Kentico requires .NET/C# setup, content type modeling, and Kentico-specific conventions before a working site is live — likely a half-day to a full day for an experienced .NET developer. Kentico's consistent monthly refresh cadence (most recently April 16, 2026) continues to improve developer kickstart templates, CLI tooling, and page builder defaults, marginally reducing onboarding friction. Still mid-range for a DXP.

Community and partner reports place agency implementations at 3–6 months for real projects. Migration from Kentico Xperience 13 requires code rewrite (not upgrade), adding months to brownfield projects. For greenfield .NET shops, timelines can be faster due to .NET tooling advantages. Scores near the DXP average; not exceptional but not poor.

.NET/C# is mainstream, which limits the talent premium compared to proprietary-language DXPs. However, Kentico-specific certification, proprietary content modeling conventions, and the relatively niche Xperience by Kentico platform mean a moderate premium over generic .NET devs. kentico-developer.com positioning as a specialist consultancy confirms non-trivial expertise gap.

SaaS tier bundles hosting (Cloud Level 1 or 2) into the subscription with no additional infrastructure spend. Self-managed tier requires customer-provisioned hosting (Azure/AWS estimated $10,000–$30,000/yr additional). For buyers choosing SaaS — the primary positioning — hosting is included and fixed-cost. Score reflects the SaaS path as the expected default for new buyers.

SaaS deployment is fully managed — no server patching, scaling, or monitoring burden. Content ops still require trained editors and periodic upgrade attention. Self-managed adds DevOps overhead. Scoring reflects the SaaS majority path; ops burden is modest compared to on-premise DXPs like AEM or HCL DX. Monthly refresh cadence (most recently April 16, 2026) is automatically applied to SaaS customers, keeping ops overhead low.

Kentico provides an open-source Migration Toolkit on GitHub, and data export/migration is supported. However, custom code migration is explicitly not handled — all bespoke development must be manually rewritten on exit or upgrade. Kentico's proprietary content modeling and API conventions create moderate data-layer lock-in. Exit effort is moderate-to-high for customized implementations.

XbyK uses ASP.NET Core MVC patterns that map well for .NET developers, but developers must learn platform-specific abstractions: Page Builder (widgets, sections, templates), content types vs. page types vs. reusable content, channels, and a proprietary API layer (not Entity Framework). The certification exam covers content modeling, custom modules, Page Builder, and CI/CD — a non-trivial concept surface. JS-only developers face a steep ramp before any productivity. Not as opaque as older DXPs but still meaningfully proprietary.

Kentico maintains a structured Developer Learning Map, Developer Kickstart guide, community quickstarts, a training-guides GitHub repo (v31+), and a Certified Developer path. The April 16, 2026 refresh added KentiCopilot Migration Tools (Content Auditor CLI + Content Migration Claude Code skill) that meaningfully improve the onboarding story for KX13 teams upgrading to XbyK — a major onboarding pathway. Still no in-app tour or first-class framework-specific (Next.js) guided path, so not higher.

The primary development model is ASP.NET Core/.NET 8 MVC — mainstream in enterprise .NET circles but a non-starter for JS-only developers. While a Headless API exists for decoupled/Next.js setups, there is no first-class Next.js starter or React-centric workflow. The platform uses its own API layer rather than standard ORMs. MVC patterns are standard but the Page Builder widget registration system and content repository API are platform-proprietary.

Kentico provides .NET project templates installable via the .NET CLI and a training-guides repository (v31+) with a working reference implementation. These cover MVC project scaffolding, basic content types, and Page Builder setup. However, no polished multi-framework starter with CI/CD config, example content, and deployment scripts exists for headless (Next.js/Nuxt). The MVC boilerplate is functional but lean.

Setup requires .NET 8 SDK installation, .NET CLI template registration, database server configuration (SQL Server), site creation, and admin/presentation layer wiring. For SaaS/cloud deployments, database provisioning is managed, reducing ops burden. Standard ASP.NET Core appsettings.json patterns apply, but the two-application model (admin + presentation) adds configuration surface. Moderate for experienced .NET developers; heavy for those new to the ecosystem.

XbyK uses a structured content type system with code-generated C# models, which makes schema changes type-safe and refactorable. CI/CD serialization is documented (community.kentico.com/blog/xperience-by-kentico-ci-cd-developer-scenarios), supporting schema-as-code workflows. No publicly documented severe field-count limits. The content model distinguishes reusable content, pages, and headless items — well-designed but requires upfront planning. Schema migrations in a live environment are less risky than older DXPs.

XbyK's Page Builder has a built-in preview mode alongside the edit mode — editors can preview unpublished changes at high fidelity without developer intervention. A read-only mode (added 2025) allows viewing component properties without creating a new version. However, implementing preview for headless/decoupled setups requires additional frontend wiring. For the standard ASP.NET Core presentation model, preview is well-integrated; for headless Next.js, it requires custom middleware.

A Certified Developer exam exists and is actively promoted by Kentico — not mandatory but strongly expected for agency partners. Passing requires knowledge of Page Builder internals, custom modules, content modeling patterns, GDPR, and CI/CD — not just general .NET skills. The platform is inaccessible to JS/Python developers. Solo generalist developers comfortable in .NET 8 can be productive but need platform-specific training before first delivery.

XbyK is designed for professional development teams, not solo developers. Migration guides reference 3–6 month timelines and costs from $10K (small) to $150K+ (enterprise), implying dedicated dev + ops + solution architect roles. The platform's architecture (Page Builder, custom modules, SQL Server database, CI/CD pipeline management) requires at minimum a 2–3 person team with a .NET developer, a DevOps/infrastructure person, and ideally a solution architect for content modeling. Solo developer deployments are possible for simple sites but not typical.

Page Builder already lets marketers self-serve page layout, widget placement, and content edits post go-live, and the read-only inspection mode reduces friction for editors. The April 16, 2026 refresh further reduces developer dependency: AIRA now assists with segment condition building, a Campaign Manager agent provides cross-campaign lifecycle insights, and an SEO & GEO Specialist agent runs keyword-based page scoring — tasks that previously required dev or specialist involvement. Not higher because new widget types, page templates, and new content types still require developers.

Xperience by Kentico delivers monthly 'Refresh' updates via NuGet package upgrades — developers update packages and redeploy, which is manageable. Breaking changes are rare (documented as 'only in major Refreshes for obsolete code'), and the changelog clearly flags affected areas. The April 16, 2026 Refresh (v31.4.0) continues the monthly cadence without breaking changes. Not higher because SaaS still requires developer-initiated NuGet updates and redeployment, unlike fully auto-updating headless SaaS platforms.

SaaS infrastructure (Azure, Cloudflare) is vendor-managed, eliminating OS/runtime patching burden. Weekly hotfix releases provide a rapid delivery vehicle for application-layer security fixes. The critical 2025 CVEs (CVE-2025-2746/2747/2748, CVSS 9.8) specifically affected Kentico Xperience 13 — a different product — not Xperience by Kentico's codebase. Not higher because some shared code lineage and the XbK app layer still requires timely NuGet hotfix adoption by customers.

Within-XbK Refresh upgrades rarely impose breaking changes — deprecations come with advance notice and changelog documentation. The April 2026 Refresh added KentiCopilot AI-assisted migration tooling (KX13 content auditor CLI + Claude Code skill-based migration plugin) to reduce KX13→XbK pain, though that migration itself remains disruptive for KX13 customers. Media Libraries sunset after July 24, 2026 still forces a migration to Content Hub for all existing XbK deployments. Not lower because XbK's internal deprecation windows are 6–12 months and well-communicated.

SaaS deployment offloads infrastructure dependencies (Azure SQL, Blob Storage, Cloudflare CDN) to Kentico, reducing operational surface. At the application layer, projects still carry an ASP.NET Core/.NET NuGet dependency tree where the NuGet version must match the database version — mismatches prevent application startup, adding upgrade coupling risk. Not lower because SaaS significantly reduces infra complexity vs. self-hosted; not higher because the version-locked NuGet model adds friction on each monthly Refresh.

SaaS Portal now includes extensible uptime monitoring (up to 6 custom checkers per environment with configurable URLs/HTTP methods/response codes, multi-region execution, and historical reporting) added in the April 16, 2026 Refresh — alongside existing dashboards for server errors, response time, CPU/memory, and Cloudflare-integrated security events. An AIRA Usage Overview dashboard tracks AI credit consumption. Microsoft Application Insights is bundled. Not higher because self-hosted deployments have no built-in monitoring and require custom APM, and even SaaS customers must configure alerting thresholds beyond Portal defaults.

Built-in content workflows handle publish/review pipelines, and the February 2026 AIRA Content Strategist plus the April 2026 AIRA SEO & GEO Specialist (per-page search/GEO recommendations) and Segment Condition Builder assist content/audience work. However, there is still no native automated broken reference detection, orphaned content alerts, or stale content identification — content hygiene remains largely manual editorial work. Third-party Siteimprove integration is available for broken link scanning but requires additional cost and setup. Not lower because AIRA tooling and workflows reduce day-to-day burden; not higher because automated hygiene is absent natively.

SaaS deployment with Cloudflare CDN handles edge caching and DDoS protection automatically. Portal metrics (response time, CPU, memory) provide visibility into performance degradation without custom setup. Auto-scaling is handled by Kentico. Not higher because ASP.NET Core output caching strategy still requires developer configuration, and self-hosted deployments require full query optimization, index tuning, and cache layer setup.

G2 Winter 2026 Grid Report awards Leader status with 98% of reviewers rating 4–5 stars and 92% recommending; 'ease of support' is specifically called out as a top-scoring category. Customer reviews consistently cite fast response from in-house engineers and good resolution quality. Standard and Premium tiers both provide 24/7 support. Not higher because dedicated CSM and best SLA guarantees remain gated behind the Premium tier.

Kentico Community Portal provides a Q&A forum with team member participation, monthly Refresh blog announcements (April 16, 2026 post is most recent), and an MVP/Community Leaders program that fosters developer engagement. Stack Overflow questions are answered with reasonable velocity. The community remains small relative to WordPress, Drupal, or major headless CMS platforms, limiting coverage for niche or advanced integration questions. Not lower because Kentico staff actively participate and the monthly cadence keeps developers informed.

Weekly hotfix releases provide a consistent, rapid delivery channel for bug fixes — a cadence that few traditional DXPs match. Customer reviews specifically praise fix turnaround ('if there is a bug, it will be fixed before you know it'). Monthly Refreshes handle larger fixes alongside features. Not higher because lower-priority bugs may sit for multiple Refresh cycles, and the 2025 critical CVE volume in the KX13 codebase suggests some QA debt that could surface in shared components.

Xperience by Kentico includes a Page Builder with drag-and-drop widget placement and pre-defined page templates, enabling marketers to create landing pages from existing templates without developer involvement. Version history for pages (March 2025) allows marketers to restore prior widget configurations. Content sync enables staging-to-production promotion with one click (May 2025). Developers must define new layouts and widgets first, so net-new page structures still require developer work. Scores at the lower end of the 65+ tier.

A dedicated Campaigns feature (March 2026) combines campaign briefs, associated digital assets, and linked customer journeys with AIRA Campaign Insights for AI-driven KPI evaluation. The new production-ready Campaign Manager Agent (April 2026) evaluates campaign performance against KPIs, audience groups, and journey metrics and generates final reports comparing success across multiple campaigns — a significant step toward portfolio-level campaign orchestration. Email Builder (production March 2025) provides visual drag-and-drop email authoring with A/B testing of email subject/content. Marketing automation with conditional branching is native. Multi-channel coordination and a dedicated content calendar UI are still absent.

The SEO & GEO Specialist Agent (April 2026, production-ready) reviews pages for both classic SEO attributes and AI readability/comprehension, provides keyword-based scoring and prioritized recommendations — closing the previously noted gap of no in-box SEO audit/scoring tool. Multiple vanity URLs per page with canonical URL selection (June 2025), URL management application for centralized redirect management (May 2025), and forward-slash support in custom URLs (July 2025) give solid SEO URL hygiene. Standard meta title/description fields are on all content types. The community XperienceCommunity.SEO package adds automatic sitemap generation, dynamic robots.txt, and llms.txt. GEO scoring for AI crawler readability is a forward-looking differentiator.

Native Form Builder supports lead capture with validation rules, conditional logic, and field visibility conditions (January 2026). Lead scoring, email marketing, and marketing automation with value-based activity signals (January 2026) are all native. 'Used in' tracking shows which pages each form appears on across channels. Form Builder improvements shipped October 2025. Not a marketing automation powerhouse, but well above headless CMS baseline with genuine out-of-the-box lead capture, scoring, and nurture.

Identity Resolution (April 2026, production-ready) unifies customer, contact, and member profiles under single identities and automatically merges profiles when visitors log in with existing accounts — a meaningful upgrade from the earlier preview-only CDP unified profiles. AIRA Segment Condition Builder (April 2026, production-ready) uses AI to assist marketers in defining complex multi-rule segment conditions. Widget-level personalization in Page Builder delivers separate content variants per contact group based on behavioral, demographic, and activity-based segments. Email widget personalization (June 2025) allows per-segment email variants. Membership Roles (March 2026) enable tiered channel-specific content access. No full page-level rules engine or real-time behavioral personalization yet.

A/B testing does not exist in Xperience by Kentico as of April 2026. All A/B testing documentation on docs.kentico.com references legacy KX12/KX13 only. The XbK changelog from 2025–2026 contains no A/B testing entries. Email Builder includes email subject/content variants but these are personalization variants (per segment), not statistically validated A/B experiments with conversion tracking and winner selection. Page-level experimentation is a confirmed gap in the new platform.

Page Builder with template-based page creation, version history for pages, content sync from staging to production (May 2025), and shareable preview URLs (December 2025) support a reasonable content velocity workflow. AIRA inline text generation and transformation tools are available in all rich text editors (January 2026). Drag-and-drop asset uploading during content creation (November 2025) reduces friction. Bulk operations are not explicitly featured, and new page types still require developer setup of widgets.

XbK natively supports website channels, email channels (Email Builder), and headless/API delivery (REST/GraphQL) for mobile apps and SPAs — covering web, email, and headless channels from a single content hub. Order status notifications extend commerce content to transactional email channels. Structured content in the Content Hub enables reuse across any API-connected surface. Social media publishing from KX13 was not ported to XbK. Native 4+ channel support without social.

Customer journey analytics (March 2025) visualizes contact progression and drop-off through journey stages with date-range filtering. AIRA Campaign Insights evaluates KPI performance across campaigns (March 2026), and the new Campaign Manager Agent (April 2026) generates final reports comparing success across multiple campaigns — extending the in-platform marketing analytics surface beyond single-campaign dashboards. Form submission tracking with channel and language metadata (October 2025) surfaces form performance. No native web analytics module comparable to KX13's visitor tracking — page views, sessions, and source attribution still require external tools (GA4/GTM).

Widget-based Page Builder naturally constrains authors to developer-defined components — marketers can only place pre-built widgets, preventing arbitrary HTML or off-brand layout choices. This enforces structural consistency indirectly. However, there is no platform-level design token management, approved color palette enforcement, or style locking system. Brand consistency relies on developers building a constrained widget palette and CSS, not on platform-enforced guardrails. Moderate consistency through architectural constraint, not explicit brand governance tooling.

The social media publishing module from KX13 (Facebook/Twitter/LinkedIn posting, analytics) was not ported to Xperience by Kentico. Standard meta fields on content types support Open Graph and social card metadata through developer-configured fields. No dedicated social scheduling workflow, push-to-social workflow, or social preview management UI exists in XbK. Authors can configure OG meta fields but there is no native social channel integration beyond standard meta tags.

Content Hub replaced KX13's media library as the centralized asset repository with taxonomy-driven organization, AIRA auto-tagging of images (March 2025), AI focal point detection for smart cropping (February 2025), dimension-specific image variants, auto-scaling on upload (April 2025), CDN link generation, and 'Used in' tracking to see where assets are referenced. Media libraries officially sunset July 2025. Bynder DAM official connector covers enterprise DAM needs. No built-in rights management or video transcoding, but meaningfully above basic media library tier.

Language variants are available on all content types — pages, reusable content items, headless items, and products. Language fallback prevents blank content. Translation workflow with multi-step review and approval is built in. Phrase Localization Platform and XTM Cloud official connectors support professional TMS-driven translation workflows. Admin UI fully localized (July 2025). AIRA provides translation assistance. Per-channel language strategies allow separate locale approaches per brand/region. Limited locale-specific campaign calendar or transcreation workflow tooling — localization applies to content generally, not with marketing-specific campaign variant management.

XbK's connector ecosystem is still maturing from the KX13 rebuild. Zapier provides general automation connectivity. Bynder (DAM), Phrase (localization), Textmetrics (content optimization), WProofreader (writing assistance), and Campaign Monitor (email sending) are official connectors. No native Salesforce CRM bidirectional sync confirmed for XbK — this existed in KX13 but has not been publicly announced for XbK. No native HubSpot or Marketo connectors. The platform's .NET 8 APIs support custom integration but the pre-built MarTech connector library is thin compared to KX13.

Products are managed as content types in the Content Hub, allowing reuse of descriptions and assets across websites, emails, mobile apps, and headless channels — production-ready as of July 2025. Content-type architecture is flexible: physical goods, digital goods, memberships, and gated content are all supported. However, the framework is architecturally modern but less feature-complete than KX13's mature e-commerce module — dedicated attribute modeling depth, product bundle configuration, and product taxonomy richness require custom implementation. Not a purpose-built PIM.

Kentico's native digital commerce includes catalog discounts, order discounts (December 2025), and generic coupon codes (January 2026), plus order and customer management applications — more than most CMS platforms. However, dedicated merchandising tooling — category page ranking, search result merchandising, cross-sell/upsell content surfaces, product spotlight modules — is not evident. The commerce framework remains extensible but thin on native merchandising UI for non-developers. No 'Buy X Get Y' or product bundle discounts yet (these existed in KX13).

XbK's digital commerce is a native framework, not an integration layer for leading external commerce platforms. No native connectors to Shopify, commercetools, Salesforce Commerce Cloud, or BigCommerce are confirmed. The extensible architecture supports custom ERP/PIM/CRM connections via API but these are custom integration work. Commerce Migration Tool added support for migrating KX13 customers and orders (January 2026) — this is a legacy migration path, not live federation with third-party commerce platforms.

Because products are modeled as content types in the Content Hub, Page Builder pages can blend editorial content and product references in the same authoring surface — buying guides, feature spotlights, and product-adjacent editorial are structurally natural. However, there are no first-class shoppable content patterns: no 'shop the look' widget, no inline add-to-cart embedded in editorial content, no lookbook authoring mode. Editorial-commerce blending is architecturally possible but not an out-of-the-box authoring pattern for non-developers.

XbK's checkout is a developer-configured flow with configurable extension points — the IOrderCreationService orchestrates order creation (October 2025). Trust badges, shipping callouts, or upsell banners within cart/checkout are not managed from the CMS as a first-class feature. Content from the Content Hub could theoretically be injected into checkout templates via developer code, but there is no marketer-facing UI for cart content management. Commerce content lives in the Content Hub but transactional flow customization is developer territory.

Order status email notifications are managed from the CMS via the Email Builder with commerce-specific merge tags/placeholders (June 2025). Order confirmation, processing, and delivery status emails can be designed and managed by marketers using the visual email builder. Beyond email notifications, post-purchase content (product onboarding sequences, review solicitation, loyalty content) is not featured as a native capability — it would require custom marketing automation sequences.

Membership Roles (March 2026) enable gated content access by role, which can be applied to restrict product catalogs or pricing content to authenticated B2B buyers. The content-type product model supports custom pricing tiers via the extensible pricing pipeline. However, there are no purpose-built B2B commerce features: no account-based pricing portal UI, no RFQ/quote workflow, no buyer/seller account hierarchy, no gated spec sheet management system. B2B patterns are achievable with significant custom development.

XbK supports basic search within website channels, and community search packages (e.g., Lucene-based integrations) extend this capability. However, no commerce-specific faceted search, synonym management, or search landing pages are native. Blended content-product search results would require custom implementation. The platform's search infrastructure for public websites is functional but not commerce-optimized — there is no search merchandising capability or AI-powered product discovery layer.

Catalog discounts and order discounts are production-ready (December 2025), and generic coupon codes are native (January 2026) — covering core promotional mechanics. Content scheduling via workflow and scheduled publishing allows time-activated promotional banners. Page Builder widgets can display promotional content. However, dedicated countdown timer widgets, tiered pricing tables with display logic, and channel-specific promotional content targeting are not documented as native features.

XbK's multi-channel architecture supports multiple website channels from a single instance, each with its own domain, page tree, and configuration. The Content Hub provides shared product content (descriptions, images, attributes) accessible across all storefront channels, while per-channel page trees control storefront-specific editorial and legal content. Language variants per channel allow region-specific pricing and content. This is architecturally sound for multi-storefront but requires developer configuration and there is no storefront-specific governance UI for non-technical teams.

Content Hub with AI focal point detection (February 2025) and dimension-specific image variants provides solid image management for product photography. Video can be embedded via content items. Maximum dimension auto-scaling on upload prevents oversized images. CDN delivery for all assets. However, 360-degree product views, AR/3D model hosting, image hotspots, and zoom functionality are not native — these require custom frontend development or third-party plugins. Basic image galleries and video embeds are possible.

XbK has no marketplace or multi-vendor commerce features. There are no seller profile management tools, seller-contributed product description workflows, or content moderation at marketplace scale. Multi-author content is technically possible via RBAC permissions, but this is generic collaborative editing rather than marketplace-specific tooling. The native commerce framework is single-vendor by design.

All product content types support language variants, enabling locale-specific product descriptions. The extensible pricing pipeline supports multi-currency display (via custom implementation). Per-region tax configuration is supported. Phrase and XTM connectors enable professional translation of product content. However, currency-aware content blocks, regulatory content templates (EU labeling, CA Prop 65), and market-specific promotional calendar management are not native — they require custom development.

Customer journey analytics visualizes progression and drop-off through marketing journeys including commerce touchpoints (March 2025). AIRA Campaign Insights evaluates KPIs including conversion metrics (March 2026). However, there is no dedicated content-to-revenue attribution within the CMS — connecting which content pages assisted or drove purchases requires external analytics tools (GA4 with enhanced ecommerce integration). Commerce analytics data is not surfaced as content performance metrics within the editorial interface.

SSO with OAuth/OIDC providers (Microsoft Entra ID, Auth0, Okta) is native. RBAC with page-tree-level ACLs scopes editorial permissions to specific channel sections. Membership Roles (March 2026) introduce tiered visitor-facing content access with channel-tree inheritance — enabling content visible only to specific membership tiers. Department-level audience-based content visibility (restricting individual pages to specific org units) remains limited; this is primarily editorial RBAC and membership-tier gating rather than fine-grained department/team content partitioning for intranet use.

Content lifecycle features including workflows, content versioning with full history, and multi-step approval processes are available. The Content Hub provides taxonomy-driven content organization. However, dedicated knowledge management features are absent: no content expiry/review scheduling, no stale content flagging, no structured knowledge article lifecycle distinct from standard content, no internal search quality tuned for knowledge retrieval at scale. Xperience is marketed as a marketing/commerce DXP — knowledge management is not a strategic use case.

Xperience by Kentico is purpose-built for marketing and commerce use cases, not employee intranets. Legacy Kentico versions (K8/K9) had explicit intranet feature sets, but the Xperience rebuild focuses entirely on digital marketing, commerce, and headless delivery. Membership Roles (March 2026) provide tiered content access which marginally supports restricted internal portals, but there are no native employee directory integrations, news feed widgets, social/community features, push notifications, or org chart tools. Building a full employee portal requires substantial custom frontend work.

XbK has no native internal communications features. A website channel could be configured as an employee news site with access-controlled content, but there are no targeted announcement tools, read receipts, acknowledgment tracking, or mandatory-read workflows. Audience segmentation exists for marketing (contact groups) but these are visitor-facing, not employee-department-targeted. Internal comms beyond basic intranet pages require custom frontend development.

No native employee directory, skills/expertise database, org chart, or team page management exists in Xperience by Kentico. Content Hub could theoretically model employee profiles as content items, but there is no out-of-the-box directory UI, org chart visualization, or HR system integration (Workday, BambooHR). This requires complete custom development from scratch.

Content versioning and workflow-based approval are available for all content — policies could be modeled as content types and managed through standard editorial workflows with version history. However, there are no purpose-built policy management features: no document acknowledgment tracking, no mandatory-read enforcement, no automated review/expiry reminders, no audit trail specific to policy acceptance. Standard CMS versioning is present but policy lifecycle management is absent.

No native onboarding journey or structured role-based content path features exist in XbK. Marketing automation with customer journeys could theoretically be adapted for employee onboarding sequences, but the automation is designed for marketing contacts/customers, not employee data integration. Progressive disclosure over 30/60/90 days, HR-triggered new-hire portals, and task checklists would all require substantial custom development without native platform support.

Basic search within XbK website channels is available, extendable via community packages (Lucene-based integrations). No federated search across connected enterprise systems (SharePoint, Confluence, Drive). No AI-powered relevance ranking or faceted filtering for internal content volumes as native features. The platform's search infrastructure is adequate for public-facing website search but not designed for enterprise federated knowledge search with cross-system indexing.

All XbK website themes/templates are responsive and mobile-accessible via browser. However, there is no native mobile app for employee portal access, no offline content synchronization, and no push notification capability for intranet content. Headless delivery via API could enable custom mobile apps but this is custom development. The platform is designed for responsive web delivery to public visitors, not native mobile experience for frontline workers.

No LMS integration or native micro-learning features exist in Xperience by Kentico. The platform's integration catalog does not include Cornerstone, Workday Learning, or any LMS. Course assignment, completion tracking, and certification management would require full custom development with a separate LMS platform.

No community or social features exist in Xperience by Kentico. The social and community modules from legacy Kentico versions were removed in the XbK rebuild and have not been reintroduced. There are no comments, reactions, discussion forums, peer recognition, polls/surveys, or idea submission features. The platform is positioned exclusively for marketing and commerce, not community or collaboration.

No native Microsoft 365/Teams, Google Workspace, or Slack integration exists in XbK. The integration catalog does not list any workplace tool connectors. KentiCopilot provides MCP integration with developer tools (Claude Code, Cursor, GitHub Copilot) but this is a developer experience feature, not an employee communication integration. Webhook-based connections to workplace tools would require custom development.

Content versioning with full history is available for pages and content items. Workflow-based approval processes provide review stages before publishing. Content sync (staging to production) adds a promotion mechanism. However, automated review date scheduling, stale content flagging, ownership assignment for content freshness accountability, and archival workflows are not documented as native features. Content lifecycle management is manual — editors must proactively archive or review content without automated nudges.

XbK's analytics capabilities (customer journey analytics, campaign insights) are designed for external visitor and customer measurement, not internal employee content consumption. There are no department-level content view dashboards, failed intranet search term reports, employee engagement heatmaps, or adoption dashboards for intranet ROI. Internal analytics is not a supported use case.

XbK supports multiple website channels within a single instance, each with separate content models (namespaced content types), separate domains, and separate page trees. The Xperience Portal is multi-tenant by architecture, with SaaS support for multiple website channels from one instance. This is silo-based channel isolation within a shared application instance — not true per-tenant environment isolation. Organizations requiring completely separate environments (separate databases, separate deployments) must provision separate XbK instances.

The Content Hub enables shared reusable content items and assets across all website and headless channels — a genuine cross-brand content sharing mechanism as a first-class architectural feature. Developers can create Razor Class Libraries (RCLs) to organize components shared between channels. The multichannel sample repository demonstrates this pattern officially. This is a workable content-sharing model, but shared component libraries require developer setup of RCLs and are not self-service for brand managers.

Centralized user management, advanced permissions with page-tree-level ACLs, and workflow approvals are available across all channels within a single XbK instance — providing meaningful cross-brand governance for teams in one system. Per-channel role scoping with configurable workflow per channel allows some brand autonomy within central oversight. Content standards enforcement across brands and cross-brand approval routing are limited; governance is primarily at the user/permission level rather than enforced content schema policies per brand.

XbK uses channel-based licensing: one main channel included in the platform license, with additional channels purchased separately. This creates approximately linear per-brand cost scaling — each new brand channel adds incremental cost. No evidence of volume tiers or economies of scale for large many-brand portfolios. Not super-linear (no separate high-cost per-brand licenses), but not economically advantaged for large multi-brand deployments either.

Each XbK website channel has its own dedicated frontend (separate Razor Class Library, separate CSS/static assets, separate logo and visual identity). Per-channel theming is architecturally clean with genuine visual isolation between brands. However, this is all developer-managed CSS and component configuration — there is no platform-level design token management, no visual theme editor for brand managers, and no version-controlled brand style propagation system. Per-brand visual identity is achievable but requires developer implementation.

Per-channel language configurations allow each brand to have its own language strategy. Language variants per content item enable brand-specific translated content. The Phrase and XTM connectors support professional translation workflows. However, brand-specific translation approval chains are not documented — translation governance appears to be a single shared workflow rather than per-brand translation routing. No brand-locale governance matrix with per-brand translation approval chains and regional legal content governance is confirmed.

XbK's analytics (customer journey analytics, campaign insights) are scoped per channel/campaign, not aggregated at portfolio level. There is no cross-brand dashboard showing content velocity, publishing cadence, or engagement comparison across the brand portfolio. Each brand/channel team sees their own metrics. Portfolio-level aggregation requires manual external analytics work.

Workflow configurations are available per channel in XbK — approval chains and review stages can be configured independently for each brand channel. Central admin retains audit visibility across all channels. This provides meaningful per-brand workflow autonomy within a centrally auditable system. However, the configurability of per-brand workflows is not extensively documented as a self-service feature — it appears to require admin-level configuration rather than brand-team-managed workflow design.

The Content Hub enables sharing of reusable content items across all channels — press releases, product descriptions, and legal copy can be authored once and referenced (not duplicated) by multiple brand channels. This is structural content reuse, not a formal syndication system with override points and push-update workflows. Corporate-to-brand content syndication with controlled local adaptation (e.g., the brand can override a product blurb but can't override a legal disclaimer) is not a documented native capability.

Basic compliance configuration is available per channel — cookie consent and GDPR handling are supported via standard web mechanisms (consent banners configurable per channel). Cloudflare security event monitoring is surfaced in the Portal (January 2026). However, there are no platform-enforced publishing guardrails that prevent non-compliant content from going live per brand, no per-brand accessibility standard enforcement, and no data residency controls per channel. Compliance is primarily developer/admin configured, not platform-enforced guardrails.

The RCL (Razor Class Library) pattern in XbK supports a shared component library maintained centrally with per-channel brand extensions — a documented and officially sample-supported pattern. However, this design system lives entirely in code: there is no platform-level design system management UI, no component versioning system, no update propagation mechanism, and no brand-extension workflow for non-developers. Central component libraries require developer discipline and code-level versioning (Git), not platform tooling.

A single XbK instance provides a central admin who can manage users across all brand channels. Per-channel role scoping allows brand teams to have autonomous editorial permissions within their channel. SSO via OAuth/OIDC (Microsoft Entra ID, Auth0, Okta) works across all channels from a single identity provider configuration. Cross-brand contributor roles (accessing multiple channels from one account) are supported via the unified user management. Meets the 'basic per-brand user management with central oversight' tier.

Content types in the Content Hub are shared across channels by default, providing a common baseline model accessible to all brands. Per-channel namespacing allows channels to have unique content types extending the shared model. However, a formal model extension pattern — where Brand A adds video fields to a global product page type and Brand B adds comparison tables without forking the base type — is not a documented platform-native capability. It requires developer-managed code-level inheritance, not a platform-managed model extension workflow.

No portfolio-level reporting dashboard exists in XbK. Metrics (customer journey analytics, campaign insights) are scoped per campaign or per channel. There is no executive view of content freshness across the brand portfolio, publishing SLA adherence tracking, cost allocation per tenant, or capacity planning data. Multi-brand deployments would require custom reporting built externally (BI tools, external analytics aggregation) to achieve portfolio-level visibility.

Xperience by Kentico includes built-in GDPR tooling — consent management, right-to-erasure, data portability, and contact anonymization. EU data residency is available via Azure EU regions with documented EU-only data storage for the portal (Auth0 EU, EU-stored logs). A Trust Center exists at trust.kentico.com hosting compliance materials. However, DPA availability to all pricing tiers and a publicly published sub-processor list were not independently verified, preventing a higher score. The April 16, 2026 refresh could not be verified via web search (search quota exhausted) but monthly Xperience refreshes have not historically introduced new GDPR-relevant tooling beyond the existing module set.

No HIPAA BAA is offered and no healthcare-specific compliance documentation exists for Xperience by Kentico. Kentico's compliance page and Trust Center list SOC 2 Type 2, ISO 27001, GDPR, and CCPA but make no mention of HIPAA. As a SaaS DXP, the platform could technically host healthcare content but without a vendor-executed BAA this is insufficient for covered entities.

GDPR and CCPA are explicitly listed on Kentico's compliance pages. The platform is described as DORA-aligned and Digital Services Act-ready, providing coverage for EU financial and digital services regulations. No FedRAMP, IRAP, C5, LGPD, PIPEDA, or PCI-DSS certifications were found. Breadth is GDPR + CCPA + DORA alignment, which exceeds GDPR-only but falls well short of broad regional coverage.

Kentico has achieved SOC 2 Type 2 compliance with annual audit cadence and continuous monitoring. Evidence is available via the Trust Center at trust.kentico.com. Specific Trust Service Criteria covered were not independently verified but likely include Security and Availability given the SaaS hosting scope. Score reflects confirmed SOC 2 Type 2 with annual cadence, held back slightly due to unverified TSC breadth.

Kentico holds ISO 27001 certification covering the Xperience by Kentico SaaS platform (not merely the underlying Azure infrastructure), with annual surveillance audits confirmed. The certification covers the full information security management system. No ISO 27018 for cloud PII processing was found, which prevents scoring above 75.

Beyond SOC 2 Type 2 and ISO 27001, Kentico's compliance posture includes DORA alignment and Digital Services Act readiness, but these are architectural alignments rather than formal third-party certifications. No CSA STAR, PCI-DSS, Cyber Essentials Plus, FedRAMP, IRAP, ENS, or C5 certifications were found. Regular penetration testing is documented but not a named certification.

Xperience by Kentico SaaS runs on Microsoft Azure with customers able to select their Azure region to meet data residency requirements. EU, US, and other Azure geographies are available. The SaaS documentation explicitly confirms EU data storage for the portal (Auth0 EU, Azure EU), with a full list of supported regions published at trust.kentico.com. Score limited by inability to verify contractual residency guarantees in the SaaS agreement.

Xperience includes built-in right-to-erasure (data erasure module), data anonymization, and personal data management APIs as part of the GDPR compliance toolkit. Content export is available via the platform API. Post-termination data retention period was not documented in publicly available materials, and no self-service erasure portal (vs. API-based) was confirmed for end-user data subject requests.

Xperience by Kentico provides an Event Log application in the administration interface that records system events and admin actions. Activity logging tracks contact-level interactions for marketing analytics. However, no native SIEM integration or log export to external security systems was found in documentation. Log retention configuration and compliance-specific reporting capabilities were not documented for the current Xperience product. The April 16, 2026 refresh could not be verified via web search; no delta applied pending verification.

No formal WCAG 2.1 AA conformance statement or accessibility documentation for the Xperience by Kentico authoring interface was found. Third-party integrations (Siteimprove) exist for content accessibility validation of published sites, but this covers delivered content accessibility, not the authoring UI. The legacy Kentico CMS had an accessibility standards article on devnet, but no equivalent for the current Xperience product was located.

No VPAT, ACR, or Section 508 conformance statement was found for Xperience by Kentico. The legacy Kentico CMS had a devnet accessibility article but it is not applicable to the current product. No ATAG 2.0 assessment documentation was located. The absence of procurement-ready accessibility documentation is a significant gap for public sector buyers.

AIRA (GA since fall 2025) provides native text generation, refinement, and rewriting across pages, emails, headless items, and content items. The Content Strategist agent evaluates pages against custom tone profiles and suggests brand-aligned rewrites. Scores below 70 because bulk generation controls and advanced prompt template governance are still maturing.

AIRA includes auto alt-text generation during mass upload, smart tagging of images by content analysis, auto focal point selection, and smart cropping for variant generation. No evidence of native DALL-E or Firefly image generation — generative image creation is not available. Scores in the 40–60 range for auto alt text and smart tagging without native image generation.

AIRA includes AI-powered translation as a core capability, listed alongside drafting, copy refinement, and headline suggestions. The Content Strategist agent applies tone profile rules across locales. Specific MT engine details (provider, quality scoring, bulk throughput) are not documented publicly, limiting confidence in the depth of controls.

The April 16, 2026 refresh expanded the AIRA SEO & GEO Specialist agent to analyze both 'human and AI readability and comprehension' and provide optimization recommendations for traditional search and AI-powered discovery experiences. Combined with one-click fixes for SEO titles, meta descriptions, schema markup, and auto alt-text on mass image upload, this is now a robust GA offering. Scores below 70 because on-page scoring dashboards and bulk metadata generation at scale are still not fully confirmed.

The April 16, 2026 refresh added the AIRA Segment Condition Builder, letting marketers construct audience segments through natural language with AI translating references into condition rules. Combined with existing AIRA auto-tagging, campaign management, Customer Journey insights, and Content Strategist rewrite/publish via API, Xperience now has multiple AI workflow assists woven into editorial. Still short of the 70+ tier due to lack of documented bulk enrichment or stale content lifecycle automation.

The April 16, 2026 refresh added the Campaign Manager Agent to the AIRA Agentic Marketing Suite, completing the trio alongside Content Strategist and SEO & GEO Specialist. The Campaign Manager evaluates journey statistics against KPIs, analyzes audience contact group performance, and generates final campaign reports. Agents operate under admin permissions with approval gates. Scores below 75 because the roster is still smaller than Contentstack Agent OS and agent marketplaces are absent.

AIRA's Customer Journey Insights analyzes behavior data, identifies conversion drop-off points between funnel stages, and suggests next best actions. The Content Strategist agent provides strategy-level recommendations. No evidence of a dedicated content intelligence dashboard with topic clustering, content health scoring, or editorial priority queues beyond these agent outputs.

The Content Strategist agent audits pages against custom tone profiles, flags brand voice deviation, and suggests rewrites. The SEO & GEO Specialist covers metadata quality, on-page structure, and (per April 2026 refresh) AI-readability analysis. Two dimensions (brand + SEO) are covered in GA agents. Accessibility scanning and large-scale duplicate/thin content detection are not documented, capping the score.

Azure AI Search with semantic ranking is available as an official integration (GitHub: Kentico/xperience-by-kentico-azure-ai-search), enabling natural language queries and geo-spatial search. Algolia integration also available. However, Azure AI Search remains a roadmap item per the Kentico roadmap board, suggesting it is not fully GA. Native vector search or embedding generation is not built into the platform core.

The April 16, 2026 refresh introduced the AIRA Segment Condition Builder, which uses AI to translate references to pages and forms into segment condition rules, plus Identity Resolution that unifies customers, contacts, and members into singular profiles using configurable identifiers. These elevate the platform from rule-only to AI-assisted personalization where rules are AI-generated but execution remains traditional (per the 40–60 band). A genuine ML scoring/predictive segment engine comparable to Bloomreach Loomi or Sitecore CDP is still absent.

Kentico ships multiple official MCP servers: a Documentation MCP Server (remote endpoint at docs.kentico.com/mcp), a Content Modeling MCP Server (part of KentiCopilot), and a Management API MCP Server for content type creation/editing — all launched December 2025 or later. A community NuGet-based MCP server also exists. Scores below 75 because read/write/publish of content items (not just content types) via MCP is not yet confirmed in official servers.

AIRA configuration supports linking a custom Azure OpenAI key, and the official GitHub module (Kentico/xperience-module-openai-azure) enables Azure OpenAI integration. AIRA can combine models from OpenAI, Anthropic, and Meta providers. Full multi-provider BYOK with data residency controls is not fully documented for non-Azure providers, placing this in the 50–70 range.

The April 16, 2026 refresh added two KentiCopilot plugins: a Kentico Xperience 13 content auditor CLI tool and an AI-assisted content migration tool. These join the existing KentiCopilot MCP-based content modeling APIs, AIRA SDK for custom content agents, and Azure AI Search RAG-ready indexing. Still short of the 70+ tier because official LangChain/LlamaIndex integration guides and agent-optimized delivery endpoints remain undocumented.

AIRA logs all agent activity for auditing and accountability, enforces admin-configured permissions and approval gates before publishing, and supports style/tone compliance checks. Customer data is commercially protected and discarded after each interaction. Hallucination detection, IP indemnification, and detailed per-prompt audit logs are not publicly documented, keeping this short of the 70+ tier.

The April 16, 2026 refresh introduced the AIRA Usage Overview — a dedicated tracking dashboard that displays credit consumption and request counts by feature over the last 30 days, directly addressing the prior observability gap. This moves Kentico into the 'basic usage tracking and cost visibility' band (45–65). Scores below 65 because per-user metrics, prompt effectiveness analytics, and quality trend monitoring are not yet documented.