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 composed across types (composition replacing the older inheritance model). The May 14, 2026 refresh (31.5.0) expanded AIRA assistance to text fields across all content type targets including headless items, and the Management MCP server now mirrors administration UI validation for content type field rules and visibility conditions. 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 EnableUnionQueryOptimization key). Standard one-to-many references with reverse traversal through GraphQL. The May 2026 content reuse locator surfaces where a content item is referenced across channels but does not change the underlying relationship model.

Page Builder provides a widget/section/zone system for composing structured pages. Headless channels support structured content items with defined content types. The May 14, 2026 refresh extended the Management API to retrieve and manage Page Builder components (widgets, sections, and their data) plus retrieve page templates, enabling programmatic access to structured page composition. Structured output for headless is GraphQL JSON (Headless REST API 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. The Management MCP server now performs content type field validation matching the administration UI — including validation rules and visibility conditions — improving programmatic consistency but not adding new validation primitives. No 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 — with headless items exposing Draft (Initial), Published, and Draft (New version) statuses. The version history UI allows review and restore of earlier versions. Scheduled publishing is available, including for content sync batches. The May 14, 2026 refresh added granular content synchronization with detailed/dependency selection between environments, letting authors selectively choose which versioned items to promote.

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. AIRA refinements went GA in April 2026, and the May 14, 2026 refresh expanded AIRA generation/refinement to text fields across pages, emails, headless items, and reusable content items — using linked items and page previews as context. Output remains HTML-based rather than a portable AST, limiting channel portability.

Asset management is consolidating into the Content Hub — legacy Media Libraries and their APIs are scheduled for full removal by July 24, 2026, with non-destructive migration into content item assets (files copied into a dedicated Content Hub workspace; GUIDs, folders, and custom fields preserved). AIRA offers AI-driven focal point suggestion and improved responsive image support, and first-party Bynder DAM integration remains available. Legacy ~/getmedia/ links to migrated assets lose URL-based resizing and no documented on-the-fly transformation pipeline (WebP/AVIF, arbitrary resize) exists — the unified Content Hub with AI focal points modestly improves the native asset story amid short-term migration burden.

No real-time co-editing with presence indicators exists, but conflict handling has materially improved: the May 2026 refresh added content overwrite protection (prevents accidental loss when two team members edit the same item), and the June 29, 2026 refresh introduced content locking as a core collaboration feature — global locking for web pages, reusable content items, and headless items with in-progress signals, an override-lock role permission, and automatic lock release on workflow-step change, publish, or revert. Combined with async workflow-step comment notifications this is solid lock-based collaboration, but still short of Google-Docs-style co-authoring.

Configurable multi-stage workflows are supported across all content types with role-based transitions and comment-enabled step notifications. The April 2026 refresh added a Role management app with permission evaluation API for the admin UI. The May 14, 2026 refresh added Workspaces and page permission management for hierarchical access control, a Content reuse locator surfacing cross-channel usage during editorial decisions, granular content synchronization between environments, and content publishing workflows with notifications — together a substantial editorial-governance upgrade.

Each headless channel auto-generates a strongly-typed GraphQL API endpoint for content delivery, with union/polymorphic query optimization. The April 2026 refresh (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. Both REST and GraphQL are now available for delivery (REST still preview; GraphQL read-only, no mutations/subscriptions), and the May 2026 Management API additions for Page Builder components further round out the API surface.

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.

The .NET global event system supports custom code handlers for object create/update/delete and lifecycle events on content items, web pages, and headless items. Zapier integration Phase 2 added inbound actions in 2026, providing webhook-like data exchange with 6,000+ external tools by triggering create/update/delete based on Xperience events. Native webhook documentation still lacks public detail on HMAC signing, filtering, retry logic, and delivery logs — Zapier brokers much of the integration surface rather than the platform exposing a first-class webhook framework.

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. The May 2026 Management API additions for Page Builder components plus granular content synchronization improve programmatic multi-channel publishing flows. Rich text output is HTML (not AST), limiting format-agnostic portability versus purpose-built headless platforms.

Xperience by Kentico ships a native CDP with rule-based Contact Groups, behavioral activity-based conditions, and unified Profiles that merge customers, contacts, and members. The April 16, 2026 refresh added admin-configurable identity resolution with flexible matching on external identifiers or native fields plus new segmentation tools and extensible APIs. Not higher because B2B firmographic enrichment and pre-built Segment/mParticle/Tealium connectors remain absent.

Page Builder widgets support native content personalization rules tied to contact groups with in-editor preview per segment, and the June 2025 refresh added Email Builder widget-level personalization for email campaigns. G2 Winter 2026 reports 90% personalization satisfaction. Held below 75 because variant-level visual preview for arbitrary headless frontends remains less seamless than top-tier DXPs.

Xperience by Kentico offers native A/B testing for both pages and marketing emails with variant creation, conversion goal configuration, and built-in analytics for evaluating results. The December 2025 refresh added an official VWO integration as an additional optimization path. Held at 55 because multivariate testing depth and statistical significance reporting are less mature than dedicated experimentation platforms.

No evidence of a built-in algorithmic or ML-based content recommendation engine in Xperience by Kentico for audience-facing personalized recommendations. AIRA provides AI-assisted content operations (which belong in cat10) but not native recommendations served to site visitors. Recommendations would require a third-party engine or custom development.

Xperience by Kentico includes basic full-text search built on Lucene.NET with page content indexing; the March 2026 refresh let SaaS projects deploy without a full rebuild of Lucene indexes, an operational gain but not a relevance upgrade. The platform's own guidance still promotes Algolia or Azure AI Search for production-quality search, indicating the native option is functional but limited in relevance tuning, faceting, and autocomplete.

Official Algolia integration with code-first index creation, page content type indexing, .NET API, JavaScript API, and InstantSearch.js support is on Kentico's officially supported roadmap with a 7-day bug-fix policy. Azure AI Search is also a documented integration path with semantic and geo search capabilities. Held at 72 because configuration remains code-first rather than UI-driven.

Native digital commerce became production-ready in July 2025 with product catalog, orders, customers, and granular promotions; 2026 additions include catalog discounts, stock tracking, and a faceted product-listing filter (AND/OR taxonomy logic with URL state). Products are modeled as content items in the Content Hub for full versioning/localization/workflow. Held at 58 because it remains a framework — storefront UI, tax calculation, and payment processing still require custom implementation, unlike turnkey commerce platforms.

An official Shopify integration delivered as a NuGet package connects via Storefront and Admin APIs with product synchronization every 15 minutes, shopping cart management, discount coupons, and direct checkout on Shopify. The integration carries Kentico's 7-day bug-fix SLA indicating first-party support. Held at 65 because BigCommerce, commercetools, and Salesforce Commerce Cloud connectors are not documented as first-party.

Products are modeled as content items in the Content Hub rather than fixed SKU objects, giving fully customizable schema, versioning, localization, and workflow, plus taxonomy-based organization by category/brand/custom attributes and SEO-friendly descriptions reusable across channels. This is a stronger pattern than generic content types repurposed for products. Held at 65 because product-specific UI patterns (variant pickers, attribute matrices) still require developer setup.

Xperience by Kentico includes native web analytics covering page views, audience engagement, customer journey mapping, marketing automation performance, email analytics, and A/B testing data. Power BI integration with pre-built reports adds deeper content performance visualization, and contact activity tracking feeds CDP profiles. Held below 75 because the analytics UI is less polished than best-in-class DXPs and content health/lifecycle metrics rely on Power BI.

Google Analytics / GA4 integration via tag management is documented, Power BI is a first-party integration with pre-built Kentico reports, and Zapier provides 6000+ app connectivity. Held at 62 because Segment, Amplitude, and other CDP-style streaming connectors are not listed as official first-party integrations.

Xperience by Kentico supports multiple website channels under a single instance with a shared Content Hub, enabling reuse of reusable content items across sites while keeping per-channel page structures, locales, and publishing config independent. The architecture is regularly cited in customer multisite consolidations. Held at 70 because cross-site governance tooling (enforced component constraints, global style policies) requires developer configuration rather than first-class brand governance UI.

Xperience by Kentico supports per-language content variants in the Content Hub with locale fallback chains, field-level locale variants via the content item model, and (April 2026 refresh) basic admin UI localization for date and time formats. Marketers can create language variants of content items and web pages directly in the CMS. Held at 70 because advanced locale-specific publishing rules and locale routing still require developer configuration.

Xperience by Kentico has a Translations queue application supporting bulk content translation, linked item translation, and AI-assisted translation via AIRA (which can also adapt for tone of voice). An official XTM Cloud TMS integration is documented. Held at 60 because XTM is the primary TMS connector confirmed first-party — Phrase, Smartling, and Lokalise are not.

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, and channel-level permissions restrict editor access. Held at 62 because native multi-brand policy enforcement (enforced style guides, cross-brand approval gates) requires custom configuration.

Legacy Media libraries will be removed July 24, 2026, with the Content Hub serving as the unified DAM going forward: metadata schemas via content types, custom tagging/taxonomy, folder structures, asset reuse tracking, smart cropping with focal points, and AIRA-assisted auto-tagging. The Bynder integration extends to full enterprise DAM. Held at 62 because Content Hub assets do not support file versioning (only the latest file is retained) and rights/expiry management of purpose-built DAMs is still missing.

SaaS deployment includes built-in CDN delivery for assets with per-field image format conversion and max width/height configuration. The April 2025 refresh added a copy-CDN-URL button, and AIRA delivers 1-click image optimization with smart cropping and focal point preservation. Held at 65 because WebP/AVIF support and responsive image presets are not explicitly documented as first-class delivery features.

Videos can be uploaded and stored as content item assets in the Content Hub, but there is no native video transcoding, adaptive bitrate streaming, thumbnail generation, or captions management. Production video workflows require embedding YouTube/Vimeo or integrating Mux/Cloudinary. Scored at the low end for basic video upload/storage without native streaming infrastructure.

Page Builder provides drag-and-drop widget placement into configurable sections, in-context editing with live preview, non-technical page composition, and per-widget personalization variants. The May 2026 refresh added Management API support for Page Builder enabling programmatic component retrieval. Held below 75 because the .NET-rendered frontend is the first-class target; full visual editing of arbitrary headless React/Next.js frontends is not equivalent to Sitecore Pages or Contentful Compose.

Xperience by Kentico has marketer-configurable workflows with custom steps, role-based authorization per step, applied to reusable content, web pages, emails, and headless items. The July 2025 refresh added workflow step comments and notification emails for contextual handoffs. Held below 75 because multi-step parallel approval paths and SLA/due-date enforcement on tasks are not explicitly documented.

Xperience by Kentico supports scheduled publishing, workflow-based publishing states, and (May 2026 refresh) Content Sync Detailed Selection providing granular control over content item promotion across environments with dependency selection. Held at 58 because a calendar-style content calendar UI is not prominently documented as a first-class XbyK feature, and atomic multi-item release bundles remain implicit via Content Sync rather than first-class bundles.

The June 2026 refresh added core content locking (globally for web pages, reusable content items, and headless items, with a role-based override permission and automatic release on workflow change/publish/revert), building on May 2026 content overwrite protection that prevents accidental loss when teammates edit the same item. There is still no simultaneous multi-author co-editing, presence indicators, or inline commenting. Scored 40 at the top of the locking-only band because both explicit locking and conflict prevention now ship, but real-time co-editing is absent.

Form Builder supports custom forms, submission data storage, autoresponder emails, and (January 2026 refresh) form field visibility conditions for marketer-managed conditional logic without custom development. CAPTCHA spam protection is documented and submissions trigger marketing automation flows. Held below 75 because progressive profiling and multi-step form sequences require custom implementation.

Native email marketing capability with subscriber lists, email campaigns, Email Builder with widget personalization (June 2025), templated emails, autoresponders, and automation-triggered sequences. Native A/B testing for emails with built-in analytics. Held at 65 rather than 70+ because deep bidirectional sync with enterprise ESPs (Marketo, Salesforce Marketing Cloud, Mailchimp) as first-party connectors is not confirmed.

Native Automation module supporting behavioral trigger-based flows, drip email campaigns with wait intervals, condition-based branching, and lifecycle activity tracking. The June 2026 refresh added Marketing Automation Extensibility — custom actions, custom triggers, and custom conditions — letting developers ship reusable trigger steps and rich context-based branching for marketers, on top of the January 2026 activity-value condition enhancements. Held below 70 because lead-scoring sophistication and campaign orchestration breadth still lag Bloomreach and HubSpot.

Built-in CDP unifies customers, contacts, and members into a single profile with admin-configurable identity resolution (April 2026), new segmentation tools, and extensible APIs. Identity resolution matches on external identifiers or native fields (e.g., member email) to merge profiles across touchpoints, enabling unified data for personalization and automation. Held at 71 because external CDP connectors (Segment, mParticle, Tealium) remain absent and B2B firmographic enrichment is limited.

Community Integrations Hub offers official and community integrations across search (Algolia, Azure AI Search), commerce (Shopify), DAM (Bynder), CRM, analytics, optimization (VWO), and TMS (XTM). First-party integrations carry 7-day bug-fix SLAs, and Zapier extends to 6000+ apps. Held at 55 because the directory is smaller than Sitecore or AEM marketplaces.

Xperience by Kentico supports outbound webhooks (used for AIRA Lambda workflow triggers) and async global event handling via DI-based event subscriptions covering content create/update/delete/publish operations. Held at 52 because webhook configuration is code-first with no documented admin UI for topic selection, signed payloads, retry policies, or delivery logs/dashboards.

Dedicated STG (Staging) environment for SaaS plans was added May 2025, with Content Sync between environments. The May 2026 refresh added Content Sync Detailed Selection for granular content promotion with dependency selection. Page Builder provides in-context live preview for .NET-rendered sites; branch-based preview environments can be configured via CI/CD. Held at 65 because universal preview for arbitrary headless frontends and shareable external draft preview links are not first-class UI features.

Custom role definition, ACL-based web page permissions, channel-level access control, content-type and workflow-step role assignments, and SSO via any OAuth/OIDC provider (Microsoft Entra, Okta, Auth0, Duo) are supported. Xperience Portal access is managed via Auth0 RBAC. Held below 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 built-in UI tool for browsing and testing queries; the April 2026 Refresh (v31.4.0) added a preview Headless REST API for retrieving content items over HTTP as JSON, broadening consumer options beyond GraphQL. The .NET Content Item Query API and IContentRetriever support advanced filtering, sorting, and projection. Not higher because GraphQL is read-only (no mutations or subscriptions), the REST API remains in preview, and fields using custom data types are unsupported in the headless GraphQL schema.

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. The May/June 2026 Refreshes expanded KentiCopilot with a Management MCP Server (content creation via Management API extensions) and Page Builder support. 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. The June 2026 Refresh released configurable custom Marketing Automation actions (registered actions appear in the marketer's automation step dialog) and the KentiCopilot Management MCP Server with Management API extensions enables agentic content-creation workflows. 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 available for admin users; API-key authentication for headless GraphQL/REST endpoints. The May 2026 MFA-bypass advisory (CVSS 8.6, brute-forceable MFA codes without account lockout) has since been patched, partially restoring the prior deduction. Not higher because SAML still requires custom configuration beyond built-in OIDC, and the MFA weakness was recent.

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 (security, availability, confidentiality scope), verified annually with continuous monitoring. GDPR and CCPA compliance with consent management tools. Trust Center powered by SafeBase provides evidence, pentest reports, 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.

May 21, 2026 security advisory disclosed a critical SQL injection vulnerability (CVSS 9.4) in Xperience by Kentico admin UI affecting versions 22.0.0–31.5.0 and an MFA bypass (CVSS 8.6), both directly in the active product line — not just legacy KX13. Older 2025 CVEs continue to appear on CISA KEV (CVE-2025-2746/2747/2749). Vulnerability Disclosure Program exists but is reward-free. The frequency and severity of high-impact CVEs across both Xperience 13 and Xperience by Kentico 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.

Xperience by Kentico SaaS is publicly documented as designed for 99.9% uptime, with Kentico responsible for SaaS environment, Xperience Portal, and deployment API availability 24/7/365. Public status page at status.xperience-portal.com with uptime history. The April 2026 Refresh added extensible SaaS uptime monitoring supporting up to 6 checker configurations across regions. Not higher because 99.9% is mid-tier vs. 99.95%+ from headless leaders, and historical uptime data not granularly published.

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 first-party 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 GraphQL codegen tools against the published schema.

Kentico now sustains a near-monthly Refresh cadence: documented 2026 Refreshes landed January 22, March 23, April 16, May 14, and June 29, each bundling meaningful features (content locking, marketing automation extensibility, agentic AI agents, AIRA campaign tooling). This proven ~monthly delivery over consecutive months pushes it into the high tier. Not higher because patch-level cadence between named Refreshes remains 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 invested in migration tooling for the legacy Kentico Xperience 13 (EOL 2026) → Xperience by Kentico transition, now including AI-assisted content migration via Claude Code skills driving the Kentico Migration Tool and expanded commerce-entity (customers, orders) migration support. Within the Refresh cadence, breaking changes are called out in release notes. No evidence of formal 12-month deprecation windows or semver codemods, 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 content on a sustained near-monthly cadence (through the June 29, 2026 Refresh), runs an MVP/Community Leaders recognition program that grew its cohort into 2026, and held Community Program Summits in 2026. Kentico team members actively contribute to the community blog and run UX feedback and early-access sessions with program members. Engagement appears genuine for a mid-market B2B product; forum 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 sustained G2 Leader status through the Winter 2026 DXP grid report. Continuous feature delivery through the June 2026 Refresh (digital commerce, agentic AI suite) reinforces the growth narrative. Not higher because logo announcements and case study publishing cadence are not at enterprise tier-1 level.

Kentico is a privately held company backed by Expedition Growth Capital (invested 2022), with $42M revenue and ~226 employees (up from 212 in 2023). 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 (through the Winter 2026 report), 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 agentic 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, 92% recommending it, and 96% saying it is headed in the right direction, placing it firmly in the 75–85 scoring band. Gartner Peer Insights averages 4.5/5. Recurring positive themes: ease of use (90%), ease of admin (90%), and support quality (91%). No significant pattern of negative sentiment around pricing or reliability visible.

Kentico publishes a public 'How to Buy' page and a downloadable pricing PDF showing SaaS from ~$1,990/mo ($23,880/yr) and self-managed from ~$990/mo ($11,880/yr), with Standard and Advanced tiers documented; some 2026 third-party listings now show a modest uptick to ~$24,600/yr SaaS and ~$12,600/yr license-only. Channel add-on pricing, AIRA credit packages, and enterprise customizations still require contacting sales, but the base structure is publicly visible. Scores in the 60–65 range typical for partial public pricing with sales-gated expansion.

Fixed-cost SaaS subscription based on pre-defined cloud levels avoids consumption spikes — a strong predictability signal — and channel-based licensing (one main channel included, add-ons for more) is predictable for most buyers. Newer AIRA/Agentic Marketing Suite runs on a credit consumption model with a monthly allocation plus opt-in expansion, introducing a metered element that a new Usage tab helps track. Penalized for multi-channel and AI credit add-ons that may not surface until scoping.

Standard tier covers single-channel web projects; Advanced tier unlocks multi-channel and enhanced digital marketing features, and AIRA (agentic AI marketing) is a separate paid credit add-on that launched Feb 1, 2026 with pricing not public. Splitting multi-channel and AI marketing behind higher tiers/add-ons is a meaningful gate for real DXP use cases, though core CMS functionality is accessible at the base tier.

Pricing is annual-only (~$23,880/yr SaaS minimum, ~$11,880/yr self-managed minimum) with no monthly billing option found, and no startup or nonprofit program is documented publicly. Independent reviewers flag recurring annual subscription increases, and no exit provisions are published beyond the standard trial. Enterprise DXP norm but rigid relative to SaaS competitors that offer monthly terms.

Only a 7-day hosted trial and a 30-day local evaluation license are available; there is no permanent free tier and the core platform is not open source (though Kentico publishes MIT-licensed companion repos). Compared to open-source DXPs like Drupal or headless CMS with free-forever tiers, this is a significant gap for solo developers or small teams evaluating the platform.

SaaS cloud infrastructure is described as ready in 30 minutes, and the Kickstart .NET CLI workflow gives developers a running local instance quickly. However, content type modeling, channel setup, and Kentico-specific conventions add a half-day to full day before a working site is live for an experienced .NET developer. The ongoing monthly refresh cadence (Mar/Apr 2026 releases) keeps shipping DX improvements but doesn't fundamentally accelerate first-value.

Partner reports place typical KX13→XbK migrations and agency implementations at 3–6 months and 6–12 months for highly customized/enterprise scopes, with KX13 end-of-life on Dec 31, 2026 driving a wave of time-sensitive replatforming. Migration is a controlled replatform (not an upgrade) requiring custom code to be rewritten for .NET Core, adding months to brownfield projects; greenfield .NET shops trend faster. Scores near the DXP average — adequate but not strong.

.NET/C# is mainstream, which limits the talent premium versus proprietary-language DXPs like Sitecore or AEM. However, Kentico-specific certification, proprietary content modeling conventions, and the relatively niche XbK platform mean a moderate premium over generic .NET developers. Dedicated certification programs and specialist consultancies confirm a non-trivial expertise gap.

The SaaS tier bundles hosting (pre-defined Cloud Levels) into the subscription with no additional infrastructure spend, while the self-managed tier requires customer-provisioned Azure/AWS hosting estimated at $10K–$30K/yr additional. For buyers choosing SaaS — the primary positioning and starting point in Kentico's published pricing — hosting is included and fixed-cost.

SaaS deployment is fully managed — no server patching, scaling, or monitoring burden — with the monthly refresh cadence auto-applied to SaaS tenants. Content ops still require trained editors and periodic upgrade attention, and 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.

Kentico provides an open-source Migration Toolkit on GitHub and supports content/data export, reducing content migration costs materially. However, code migration is explicitly not handled — all bespoke development must be manually rewritten on exit or version upgrade — and proprietary content modeling plus API conventions create moderate data-layer lock-in.

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 content repository API (not Entity Framework). The certification exam covers content modeling, custom modules, Page Builder, and CI/CD — a non-trivial concept surface, and KentiCopilot AI scaffolding helps navigate but does not reduce it. Cleaner than KX13's Portal Engine hybrid but still meaningfully proprietary.

Kentico maintains a structured Developer Learning Map, Developer Kickstart guide, community quickstarts, a training-guides GitHub repo, and a Certified Developer path — and through mid-2026 has aggressively layered AI-assisted onboarding on top: an AI development hub, a KentiCopilot plugin marketplace where all prompts/instructions are exposed as skills, and Management/Documentation MCP servers (107+ tools by the June 29, 2026 refresh) that scaffold projects and, per Kentico, 'lower the seniority bar' for new developers. Not higher because there is still no in-app interactive tour and no first-class framework-specific (Next.js) guided learning path.

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 GraphQL channel and (as of 2026) a preview Headless REST API support decoupled/Next.js setups, there is still no first-class Next.js starter or React-centric workflow maintained by Kentico — Next.js integration remains community-documented and secondary. The platform uses its own content repository API rather than standard ORMs, and Page Builder widget registration is platform-proprietary.

Kentico provides .NET project templates via the .NET CLI, a training-guides reference implementation, an xperience-component-starter for Page Builder components, and in 2026 added an open-source 'Admin Design Components' reference project plus KentiCopilot skills that scaffold projects and custom actions following best practices. Still no polished vendor-maintained multi-framework (Next.js/Nuxt) starter with example content, CI/CD config, and deployment scripts, so the headless story remains lean.

Setup requires the .NET 8 SDK, .NET CLI template registration, SQL Server provisioning, site creation, and admin/presentation-layer wiring across a two-application topology — moderate for experienced .NET developers. The June 29, 2026 refresh improved configuration readability and added a KentiCopilot marketplace plugin that auto-generates and upgrades CD repository.config files from git history, reducing a historically fiddly config step. Still heavier than a headless CMS given the two-application model and SQL Server dependency.

XbyK uses a structured content type system with code-generated C# models, making schema changes type-safe and refactorable, with documented CI/CD serialization for schema-as-code. The 2026 Management MCP server now supports programmatic retrieval/management of content types, reusable field schemas, workspaces, taxonomies, and tags, further lowering the risk of drift. No publicly documented severe field-count limits; the reusable-content vs. page vs. headless-item separation is well-designed but requires upfront planning.

Page Builder has built-in preview and edit modes with a read-only inspection mode (2025), letting editors preview unpublished changes at high fidelity without developer intervention for the standard ASP.NET Core presentation model. For headless Next.js, preview still requires custom middleware to consume the preview API and route draft content, so it is not plug-and-play. 2026 Management API/MCP Page Builder support helps tooling but does not remove the headless preview wiring.

A Certified Developer exam still exists and is strongly expected for agency partners, covering Page Builder internals, custom modules, content modeling, GDPR, and CI/CD — not just general .NET skills, and the platform remains inaccessible to JS/Python-only developers. Kentico's 2026 AI-dev push (KentiCopilot skills, MCP servers, Claude Code/Cursor/Copilot support) explicitly aims to 'lower the seniority bar,' modestly reducing the platform-specific expertise needed before first delivery. Not higher because the proprietary Page Builder/module model and certification expectation persist.

XbyK is designed for professional development teams, not solo developers. Migration guides reference 3–6 month timelines (6–12 for large/customized solutions) and costs from $10K to $150K+, implying dedicated dev + ops + solution architect roles. The architecture (Page Builder, custom modules, SQL Server, CI/CD, two-application topology) typically needs a 2–3 person team minimum; solo deployments are possible for simple sites but not typical.

Page Builder lets marketers self-serve page layout, widget placement, and content edits post go-live, with read-only inspection reducing editor friction, and AIRA now assists marketers directly: the April 2026 refresh added SEO & GEO Specialist and Campaign Manager agents plus segment-condition building, and the May 14, 2026 refresh (31.5.0) extended AIRA text-field assistance across all content type targets including headless items. 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. The June 29, 2026 Refresh (v31.6.0, plus July hotfix 31.6.1) continued the monthly cadence without breaking changes, and breaking changes remain rare (documented as only in major Refreshes for obsolete code) with clear changelog guidance. 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 and weekly hotfix releases provide a rapid delivery vehicle for application-layer fixes, but security advisory 2026-05-21 disclosed a critical SQL injection (CVSS 9.4) in XbK's own admin UI query infrastructure affecting versions 22.0.0–31.5.0, plus an MFA brute-force weakness (CVSS 8.6) in the same range — both requiring customers to update to the latest version. Lowered from prior scoring because the critical-CVE exposure is now in XbK's own codebase, not just the legacy KX13 lineage. Not lower because advisories are clear, fixes shipped promptly via the Refresh channel, and SaaS still removes OS/runtime patching burden.

Within-XbK Refresh upgrades rarely impose breaking changes — deprecations come with advance notice and 6–12 month changelog-documented windows — and June 2026 expanded KentiCopilot AI-assisted KX13→XbK content migration tooling to ease that path. However, the Media Libraries sunset lands July 24, 2026 — now ~2.5 weeks away — forcing all existing XbK deployments to migrate assets to Content Hub. Not lower because the deprecation window was long and well-communicated with migration guides and tooling; not higher because a forced feature removal is imminent.

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 includes extensible uptime monitoring (up to 6 custom checkers per environment with configurable URLs/HTTP methods/response codes, multi-region execution, and historical reporting) alongside dashboards for server errors, response time, CPU/memory, and Cloudflare-integrated security events. An AIRA Usage Overview dashboard tracks AI credit consumption, and 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 workflows handle publish/review pipelines, AIRA tooling (Content Strategist, SEO & GEO Specialist, Segment Condition Builder) assists content/audience work, and the June 29, 2026 Refresh added content locking that auto-prevents conflicting concurrent edits — reducing day-to-day collaboration friction. 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 exists but costs extra). Not lower because AIRA and content locking reduce operational burden; not higher because automated hygiene is absent natively.

SaaS deployment with Cloudflare CDN handles edge caching and DDoS protection automatically, and Portal metrics (response time, CPU, memory) provide visibility into degradation without custom setup while Kentico manages auto-scaling. 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 reconfirms Leader status with 98% of reviewers rating 4–5 stars and 92% recommending, and 'ease of support' called out as a top-scoring category; reviews consistently cite fast response from in-house engineers. 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 (June 29, 2026 post most recent), and an MVP/Community Leaders program that fosters developer engagement, with Stack Overflow questions answered at reasonable velocity. The community remains small relative to WordPress, Drupal, or major headless CMS platforms, limiting coverage for niche 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 and security fixes — the critical May 2026 SQLi advisory shipped a fix promptly with clear per-fix documentation — and reviews specifically praise fix turnaround. Monthly Refreshes handle larger fixes alongside features. Not higher because lower-priority bugs may sit for multiple Refresh cycles, and the volume of critical CVEs surfacing in shared/own codebase components suggests some QA debt.

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 May 2026 refresh added a guided campaign-brief authoring flow: the Campaign Manager Agent asks marketers a structured series of questions (brand, goals, audiences, KPIs, channels, messaging) and restructures the answers into a formatted brief. The 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. 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.

Xperience by Kentico has no native content-level or server-side A/B testing — all first-party A/B testing documentation still references legacy KX12/KX13 only, and the XbK changelog contains no native experimentation feature. However, Kentico now maintains an official Tag Manager package (github.com/Kentico/xperience-by-kentico-tag-manager) that lets marketers enable a VWO integration directly from the administration UI, injecting VWO SmartCode into a website channel for front-end A/B testing and experimentation (added December 2025). This is client-side experimentation via a tight third-party integration: experiment design, targeting, and statistical significance/winner selection all live in VWO's own platform, and the integration can manipulate only front-end data (no backend experimentation). Email Builder subject/content variants remain per-segment personalization, not statistically validated experiments. This fits the 'experimentation via tight integration' tier at the lower end — a real optimization path exists, but nothing native or content-model-aware.

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 was expanded to text fields across all content type targets including headless items (May 2026), extending assisted authoring beyond the rich text editor. Content overwrite protection (May 2026) and globally configurable content locking (June 2026) prevent lost edits and rework from concurrent editing, and a content reuse locator surfaces cross-channel usage during editorial decisions. 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.

The official Tag Manager package (github.com/Kentico/xperience-by-kentico-tag-manager) lets marketers enable Google Analytics 4, Google Tag Manager, and Microsoft Clarity (session recording, heatmaps, scrollmaps) directly from the administration UI per website channel — first-class configuration of standard analytics tags without developer template edits, though the metrics themselves still live in the external tools. In-platform, 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 Campaign Manager Agent (April 2026) generates final reports comparing success across multiple campaigns. Form submission tracking with channel and language metadata (October 2025) surfaces form performance. Still no native web analytics module comparable to KX13's visitor tracking — page views, sessions, and source attribution remain in 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. The official Tag Manager package adds Intercom alongside GA4/GTM/Clarity/VWO for front-end tag injection, and marketing automation custom actions (June 2026) give developers a first-class extension point to plug external systems into automation flows — a registered custom action appears in the marketer's automation step dialog and has access to contact context, the database, and the trigger state (e.g., a form submission). Zapier provides general automation connectivity. Bynder (DAM), Phrase (localization), Textmetrics, WProofreader, and Campaign Monitor (email sending) are official connectors. Still no native Salesforce/HubSpot/Marketo CRM or MAP connectors for XbK — the KX13 Salesforce connector has not been ported. The .NET 8 APIs plus custom automation actions support integration, but the pre-built MarTech connector library remains thin.

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. The February 2026 refresh added promotion targeting flexibility, letting marketers scope a promotion to all customers or only those authenticated through member accounts — a step toward audience-specific promotional targeting. Content scheduling via workflow and scheduled publishing allows time-activated promotional banners, and 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 still 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.

Workspaces segregate Content Hub content into distinct role-scoped areas, with granular per-workspace permissions (View, Create/Update, Delete) assigned per role and per application — e.g., full Content hub permissions in Workspace A but View-only in Workspace B — so editors only see and act on the content in their workspace. Page permission management adds hierarchical page-level access control. This moves beyond simple content-type RBAC toward content-instance/area-based visibility control. SSO with OAuth/OIDC providers (Microsoft Entra ID, Auth0, Okta) is native, and Membership Roles (March 2026) add tiered visitor-facing content access with channel-tree inheritance. Fine-grained department/team partitioning for classic intranet use is still primarily an editorial-governance construct rather than audience-org-unit content targeting, so it lands solidly above content-type RBAC but short of full audience-based visibility.

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, and content overwrite protection (May 2026) plus globally configurable content locking (June 2026) reduce collaboration conflicts. However, automated review date scheduling, stale content flagging, ownership assignment for content freshness accountability, and archival workflows are still not documented as native features. Content lifecycle management remains 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. Workspaces add content-area governance: content can be segregated into workspaces with per-workspace role permission scoping (View/Create/Update/Delete per application), giving central teams a first-class way to enforce who can act on which content across brands while preserving per-channel autonomy. Content publishing workflows with notifications and a content reuse locator further strengthen editorial governance. Cross-brand content-standard enforcement (schema policies per brand) and cross-brand approval routing remain limited; governance is primarily at the user/permission/workspace level rather than enforced per-brand content schemas.

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. Workspaces let central teams give brand/project groups autonomous content areas with role permissions scoped per workspace (View/Create/Update/Delete per application), so brand teams operate independently while central admin retains oversight. Per-channel role scoping allows brand teams autonomous editorial permissions within their channel. SSO via OAuth/OIDC (Microsoft Entra ID, Auth0, Okta) works across all channels from a single identity provider, and users can hold roles across multiple channels. Comfortably meets the central-admin-with-autonomous-brand-teams-and-SSO bar.

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. DPA availability across all pricing tiers and a publicly published sub-processor list were not independently verified in this pass, preventing a higher score.

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, and log retention configuration and compliance-specific reporting capabilities were not documented for the current Xperience product.

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 May 14, 2026 refresh (31.5.0) extended AIRA text-field assistance to all content-type targets including headless items and lets marketers configure rendered Page Builder pages as generation context. 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 localization/translation as a core capability, listed alongside content creation, insights, and intelligent visual content management. 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 AIRA SEO & GEO Specialist agent (GA) analyzes individual pages for both human and AI readability and recommends improvements for traditional search and AI-powered discovery, requestable via one click on any website channel page. Combined with one-click fixes for SEO titles, meta descriptions, schema markup, and auto alt-text on mass image upload, this is a robust GA offering. Scores below 70 because on-page scoring dashboards and bulk metadata generation at scale are still not fully confirmed.

The AIRA Segment Condition Builder lets marketers construct audience segments through natural language with AI translating references into condition rules, and the June 29, 2026 refresh added extensible marketing automations (developer-registered custom automation actions surfaced in the automation step dialog). Combined with existing AIRA auto-tagging, campaign management, and Content Strategist rewrite/publish via API, Xperience 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 AIRA Agentic Marketing Suite ships three GA agents — Content Strategist, SEO & GEO Specialist, and Campaign Manager (which interviews marketers to author campaign briefs and evaluates journey KPIs) — operating under admin permissions with approval gates. The May 14, 2026 refresh additionally enabled agent-driven autonomous iteration over the full Page Builder widget lifecycle via the Management MCP server. Scores below 75 because the native agent 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, and the Campaign Manager agent analyzes audience contact group performance against KPIs. 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 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 is also available. However, Azure AI Search remains a roadmap item and native vector search or embedding generation is not built into the platform core. No 2026 GA announcement of native semantic/vector search was found.

The AIRA Segment Condition Builder uses AI to translate references to pages and forms into segment condition rules, plus Identity Resolution unifies customers, contacts, and members into singular profiles using configurable identifiers. These place the platform in the 40–60 band where rules are AI-generated but execution remains traditional. A genuine ML scoring/predictive segment engine comparable to Bloomreach Loomi or Sitecore CDP is still absent.

Kentico ships official MCP servers whose scope has expanded steadily since the November 2025 release: the Management MCP server now exposes CRUD for content types, content items, pages, channels, and languages, and the May 14, 2026 refresh (31.5.0) added retrieval/management of Page Builder components and agent-driven autonomous modification of Page Builder pages, with the server mirroring admin-UI field validation and visibility conditions. A Documentation MCP server and Content Modeling MCP server (KentiCopilot) round out the roster. This now clears the 75+ bar (schema awareness, permissions, read/write/publish). Not higher because it targets IDE/dev-agent workflows rather than an always-on hosted content-agent endpoint.

AIRA runs on Kentico-managed Azure infrastructure and can combine models from OpenAI, Anthropic, and Meta, and its configuration supports linking a custom Azure OpenAI key (e.g., GPT-4o); the official Kentico/xperience-module-openai-azure module enables Azure OpenAI integration. Full LLM-provider override to non-Azure providers exists only via community extensions (e.g., inheriting ChatCompletionServiceExtensionsBase), not first-party config, so multi-provider BYOK with data-residency controls remains partial — 50–70 range.

KentiCopilot provides MCP-based content-modeling and management APIs plus a GitHub plugin marketplace; the June 29, 2026 refresh added a digital-experience plugin with an automation-action-create skill that researches a project's API and implements/registers a custom automation action, joining the KX13 content-auditor CLI and AI-assisted migration tools, the 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 June 29, 2026 refresh expanded the AIRA Usage tab: admins can track credit consumption by feature (last 30 days by default) and export the past 90 days of usage data as CSV, building on the April 2026 Usage Overview that surfaced credit consumption and request counts by feature. This puts Kentico solidly in the 45–65 'basic usage tracking and cost visibility' band. Scores below 65 because per-user metrics, prompt effectiveness analytics, and quality trend monitoring are still not documented.