Kentico Xperience 13

Kentico Xperience 13 uses 'page types' defined via the admin UI field editor, supporting text, textarea, integer, decimal, boolean, datetime, file, media selector, color picker, and custom field types. Types are UI-only — no schema-as-code, no C# code generation as in XbK, and no polymorphic/union fields. Adequate variety for traditional enterprise CMS use, but no new types have been added since the platform entered security-only support. Capability gap widens vs. modern platforms given the feature freeze.

KX13 supports related pages via relationship categories and page type field relationships. These are primarily unidirectional — querying in reverse direction requires manual LINQ. No many-to-many native field type, no graph traversal, and no polymorphic references. The relationship model is the legacy Kentico approach from the pre-headless era. More limited than even mid-tier headless platforms.

Page Builder provides component-level composition with sections, zones, and widgets. Reusable widgets can be shared across pages. Widget nesting works within section/zone constraints. The composition model is functional for standard web content but outputs HTML — no portable structured content format (Portable Text, Rich Text AST). This is the same architecture since KX 12 SP; nothing has changed in the content composition model.

Standard field-level validation covers required, min/max length, regex patterns, and data type checks. Custom validation is possible via .NET code in page type definitions. Form Builder includes field visibility conditions. No visual cross-field validation rule builder — custom rules require .NET development. Functional for standard CMS use but no enhancements in the security-only maintenance window.

Mature version history and workflow integration is one of KX13's genuine strengths. Full version history with view and roll-back per page, draft/published/archived states, scheduled publishing with Publish from/Publish to fields. Version history records include publish, unpublish, and scheduling events. Object versioning also configurable for non-page content. Workflow and versioning are tightly integrated — approved pages can be scheduled and the history captures all lifecycle transitions.

Page Builder provides genuine in-page visual editing with drag-and-drop widget placement, section management, and in-context content editing. Non-technical editors can rearrange page layouts using the widget drag handle and section type switcher. The interface is a near-WYSIWYG experience where content changes are visible before publishing. Competitive with other traditional DXP page editors of this era. No AI-assisted features, no smart asset upload, no KentiCopilot — those are XbK-only features.

Rich text uses a TinyMCE-based editor with configurable toolbar supporting standard formatting (bold, italic, headings, lists, tables, images, links). The toolbar can be customized and extended via plugins. No custom block types, no inline annotations, and output is HTML only — no portable structured format. The editor can be extended with custom TinyMCE plugins but this requires development effort. No AI refinement tools (those are XbK-only). Standard HTML-output WYSIWYG appropriate for legacy DXP.

Media libraries support upload, folder organization, and basic metadata. Image resizing is available via URL parameters in the getmedia handler (width, height, max side), but there is no focal point detection, no WebP or AVIF format output, no automatic optimization pipeline, and no smart variants. Files accessed via direct path bypass all Xperience image handling. This is a notable weakness — all responsive image work requires front-end developer customization. No enhancements possible given EOL status.

No real-time co-editing capability. KX13 uses a document locking model — when one editor opens a page for editing, others see it as locked. No presence indicators, no activity feeds, no commenting on content items. This has been a known limitation for the lifetime of the Kentico Xperience product line. With the platform at EOL, no improvements will be made.

Mature multi-step workflow engine supporting both basic (linear) and advanced (conditional branching) workflow types. Workflows are configurable per page type or tree section with role-based stage transitions, email notifications, and approval chains. Scheduled publishing integrates with workflow — pages move to live only after approval then wait for the publish date. Object versioning records all workflow transitions. This is one of KX13's genuine long-standing strengths, representing years of refinement.

KX13 includes a configurable REST service (disabled by default) for reading and manipulating content data. The REST service covers page data, media files, and system objects. There is no GraphQL — KX13 predates the Kentico GraphQL investment which arrived with XbK. The REST API supports CRUD operations but lacks modern features like field selection, cursor pagination, or filtering depth. A separate headless channel architecture does not exist. The API surface is adequate for basic integrations but dated by current standards.

KX13 is a self-hosted or managed-hosting platform with no built-in CDN. Teams deploying on-premises or via Kentico's managed hosting partners must configure their own CDN layer. There is no native CDN integration, no content-aware cache invalidation on publish, and no edge computing capability. Azure or Cloudflare can be placed in front of a KX13 deployment, but this requires infrastructure configuration outside the platform. Score reflects the self-hosted without CDN baseline.

The internal .NET global event system is robust: sync and async handlers with dependency injection covering content CRUD, workflow transitions, and system object changes. This enables reliable internal integration pipelines for .NET developers. External webhook emission exists but is limited — no admin UI for configuration, no HMAC signing, no retry dashboard, no delivery logs. Outbound HTTP calls can be wired in event handlers but require developer implementation per integration. Adequate for .NET-native integrations, weak for no-code/external webhook consumers.

KX13 is a traditional web-first MVC platform. The optional REST service provides a thin API layer for external data access, but there are no dedicated headless channels, no GraphQL, and no official SDKs for JavaScript, mobile, or other platforms. Rich text output is HTML — not portable. Multi-channel delivery requires custom implementation against the REST service. The platform was designed for .NET MVC web delivery and the headless layer is an add-on afterthought, not an architectural pillar. Well below modern headless or hybrid platforms.

KX13 has a mature Online Marketing module with contact groups using macro-based conditions covering demographics, behavioral activities, and custom attributes — a feature set that has been stable for many years. Personas with automatic scoring are included. Batch-evaluated segmentation only — no real-time streaming. Solid for its era but no active development given security-only support status since late 2024.

KX13 supports both page-level personalization (multiple page variant alternatives based on contact group/persona conditions) and widget-level personalization in Page Builder. Persona-based preview available. Rule-based only with macro conditions — no ML-driven optimization. The dual-level personalization (page and widget) is a slight edge over XbyK's widget-only approach, but the technology is aging.

KX13 includes built-in A/B testing for page variants and email variants with traffic splitting and conversion tracking. No multivariate testing. Statistical methods are basic — no Bayesian analysis, no auto-winner selection. Enterprise license required. Feature is mature but frozen given EOL support status.

KX13 has an official first-party Recombee integration (xperience-module-recombee) providing ML-powered content recommendations based on collaborative filtering and behavioral tracking. The integration adds an admin application, tracks contact page-view activities to feed Recombee's algorithms, and surfaces recommended pages on the live site. Requires a separate Recombee subscription — not fully built-in. This integration is KX13-specific and was not ported forward to XbyK.

KX13 'Smart Search' is powered by Lucene.NET 3.0.3 and supports full-text indexing of pages, forum posts, media library files, and custom data. Multiple index types are supported. Search assistance features (autocomplete-style) configurable. Field-level boosting possible via developer customization. No faceted search, typo tolerance, or relevance tuning UI out of the box. The Lucene.NET version (3.0.3) is dated; an unofficial module upgrades to 4.8 beta but is not official.

No official pre-built connectors for Algolia, Elasticsearch, or Azure AI Search exist for KX13 (those were developed for XbyK only). Custom integration is possible via the REST API, global event system, and NuGet modules, but developers must build index sync logic from scratch. The Zapier bridge can relay events to search services but with significant friction. Contrast with XbyK's official Algolia and Azure AI Search packages.

KX13 includes a full-featured e-commerce module that is a genuine platform strength: product catalog supporting goods, services, e-products, memberships, and bundle types; shopping cart with configurable pricing models; full checkout with customizable payment/delivery methods; order management for registered and anonymous customers; volume/catalog/order discounts, product coupons, and free shipping offers; inventory management. More mature than most traditional DXPs at this tier. Feature-frozen but complete.

No pre-built connectors for Shopify, commercetools, BigCommerce, or Salesforce Commerce Cloud in KX13's ecosystem. KX13's strategy was always native commerce rather than external commerce federation. Custom integration is possible via REST API. The platform's strength is its own e-commerce module, not bridging to external platforms.

KX13 has a dedicated Product Information Management (PIM) module as part of its e-commerce offering. Products support rich descriptions, variant/SKU management, product options, specifications, manufacturer/supplier data, and associated media. Product-specific field patterns and page types exist out of the box — not just generic content repurposed for products. More mature than most DXPs at this tier for product content.

KX13 has a substantial native web analytics module: page view tracking, unique visitors, bounce rates, time on site, conversion goals, campaign analytics, email marketing statistics (opens, clicks, unsubscribes), A/B test results, and contact activity reports. A Looker Studio connector module is available to surface KX13 data (contacts, email stats) in external dashboards. More comprehensive built-in analytics than most DXPs at this tier.

Google Analytics integration available via code snippet injection in page templates. REST API enables export of contact and activity data for external analytics platforms. Zapier bridge (with xperience-zapier module) provides indirect paths to analytics tools. No first-class connectors for GA4, Adobe Analytics, Segment, or Amplitude — analytics integration is primarily developer-driven via REST or tag injection.

Multi-site is a KX13 strength with deep platform support: multiple websites under a single instance each with separate content trees, domain assignment, culture settings, and per-site feature configuration. Global shared objects (pages, media library files) can be shared across sites. Web farm support for distributed deployments. Centralized administration with per-site role assignments. Competitive with tier-1 traditional DXPs.

KX13 supports multilingual websites with separate page versions per language/culture, culture assignment to sites, and fallback chain configuration. Supports double-byte (eastern) languages. Admin UI can be localized. Document-level localization — no field-level granularity. Culture-specific publishing (Publish from/to per culture). Limited compared to platforms scoring 75+ that offer field-level locale control.

KX13 includes built-in machine translation (Microsoft Translator, Google Translate) and human translation workflow with XLIFF export/import. Translation services application manages submissions and status tracking. XLIFF-based human translation creates zip archives of .xlf files for external TMS delivery. Stronger than XbyK's translation capability by having machine translation built in natively. No deep bidirectional TMS sync (e.g., Phrase webhook callbacks), no translation memory.

Brand separation is achievable via KX13's multi-site architecture with per-site configurations and role scoping. No dedicated multi-brand governance model exists — no brand-level permission groups, no shared component library with per-brand overrides, no cross-brand policy enforcement. Adequate for simple brand separation scenarios but lacks enterprise multi-brand management sophistication.

KX13 uses Media Libraries (multiple per site) as its asset management layer: organized folder structures, multiple media types (images, video, documents), and a built-in image editor supporting resize, rotate, crop, format conversion, and grayscale. Bynder DAM integration available for enterprise needs. No asset versioning, no usage tracking across content natively, no rights/expiry management. Functional media library rather than a full DAM.

KX13's on-premises/self-hosted default includes no built-in CDN. External storage is configurable via Azure Blob Storage + Azure CDN or Amazon S3. The built-in image editor provides resize, crop, rotate, and format conversion, but these are not on-the-fly transforms — they must be applied explicitly by users or developers. WebP generation not documented for KX13. Responsive image delivery is developer-implemented. Teams must configure their own CDN and transform pipeline.

Media Libraries in KX13 accept video file uploads as storage, but there is no native video transcoding, adaptive bitrate streaming, thumbnail generation, or caption/subtitle management. Audio file storage similarly passive. Streaming video use cases require embedding YouTube, Vimeo, or an external video platform. This is standard for legacy DXPs of this era.

KX13 offers an MVC-based Page Builder with drag-and-drop widget composition within developer-defined sections and zones. Live preview with persona-based preview switching. Widget personalization conditions configurable in the Page Builder UI. Page templates available for quick page creation. Widgets require .NET (ASP.NET MVC 5) development — no low-code widget authoring. Section layout is template-driven, limiting marketer control over structure.

KX13 has a mature dual-workflow model: basic sequential workflows and advanced workflows with visual designer, conditional branching, automatic page manipulation steps, and role-based routing. Custom workflow states, email notifications on transitions, and version history. Advanced workflows support parallel approval paths and macro-based branching — more powerful than basic multi-step tools. No SLA enforcement or due-date management.

KX13 supports scheduled publishing via Publish from/Publish to date-time fields on pages, with the scheduler running as a background service. Scheduled pages that use workflow must still complete approval before the scheduled time activates. No dedicated calendar UI for content planning, no timeline visualization, no release bundle concept for atomic multi-item deployments. Functional scheduling without the planning UX layer.

KX13 uses content locking — editing a page locks it for other users who see it read-only. Version history (page versioning) enables content recovery and audit trail. No simultaneous multi-author editing, no presence indicators, and no inline comment threads on content items. Collaboration is entirely workflow-gated: comments must be added via workflow transition steps or external communication. A significant gap vs. modern collaborative CMS tools.

KX13 includes a visual Form Builder with drag-and-drop form components, conditional logic, multi-step form capability (via wizard form layout), CAPTCHA support, and submission storage in the database. Form submissions update contacts and trigger marketing automation processes. Progressive profiling via the 'Remember values' feature partially fills forms for returning contacts. More complete than XbyK's form builder which added conditional logic only in Jan 2026.

KX13 has a full native email marketing module: newsletter subscriptions, campaign emails, drag-and-drop Email Builder with widget-based composition, A/B testing for email variants, email scheduling, detailed statistics (open rates, click rates, unsubscribes), and list management. Emails sent via SMTP queue or mass email service. Marketing automation integration for triggered sends. No pre-built connectors for Mailchimp, HubSpot, or Salesforce Marketing Cloud — external ESP sync requires custom work.

KX13 has a mature visual Marketing Automation module with a full process designer: behavioral triggers (form submissions, page visits, custom activities, time-based), conditional branching, lead scoring, email campaign steps, wait steps, contact attribute updates, and lifecycle management. Pre-built process templates available. Batch-evaluated (not real-time event streaming). One of KX13's genuine platform strengths with years of iteration. Feature-frozen at EOL.

KX13 has a native contact management system tracking activities (page visits, form submissions, email interactions, purchases, custom activities) that functions as a lightweight CDP for segmentation and automation. Contact profiles store demographic data alongside behavioral histories. No external CDP platform integrations (Segment, mParticle, Tealium) — the native system is proprietary and data stays in the KX13 SQL database. Less unified than XbyK's Feb 2026 CDP refresh but functionally adequate for mid-market use.

KX13 has a more extensive legacy ecosystem than XbyK due to years of development: official integrations include Salesforce, Dynamics 365, Zoho, Marketo, SiteImprove, Recombee, Bynder, Intercom, and Visual Studio. Zapier integration with UI-configurable triggers extends reach to 6,000+ apps. Partner integrations add further coverage. However, the ecosystem is frozen — no new official integrations are being developed for KX13 since security-only support began. NuGet package delivery model.

KX13 has a UI-configurable Zapier module (xperience-zapier) that allows administrators to create webhook triggers directly in the Xperience admin UI — fired when global CMS events occur. This is meaningfully better than XbyK's code-only event system. However, it's Zapier-dependent rather than a native general webhook system: no direct outbound webhooks, no signed payloads, no retry logic outside Zapier's infrastructure. The REST API handles inbound integration; the global .NET event system handles developer-coded hooks.

KX13 is primarily a coupled/MVC platform rather than a headless-first architecture. A REST API enables content delivery to external consumers, but it lacks the modern headless preview affordances of purpose-built headless CMS platforms. No per-channel preview links, no shareable draft preview URLs for external stakeholders, no branch/environment concept within a single instance. The 'Staging' service in KX13 is a content synchronization mechanism for deploying between KX13 server instances — not a headless preview feature. Significantly below XbyK which has proper headless channel management.

KX13 has a fully custom RBAC system: roles with granular permissions spanning module-level actions (e.g., which admin applications are accessible), page type-level permissions, and custom table permissions. Roles are assignable per-site or globally. Users can belong to multiple roles with additive permissions. SSO via identity providers is supported. No SCIM for automated user lifecycle management and no field-level content permissions — these gaps prevent a score above 65.

Kentico Xperience 13 provides a CRUD-style REST service at `/rest` (disabled by default) supporting GET/POST/PUT/DELETE for pages and objects, plus a SOAP/WCF Staging Sync Server. No GraphQL — that is exclusive to the successor product. No OpenAPI spec, no interactive playground, limited filtering compared to modern headless APIs. The headless delivery API is the same REST service surfacing page/object data, not a purpose-built content delivery layer.

No CDN-backed content delivery layer — Azure CDN is configurable as a static asset offload (CMSAzureCDNEndpoint web.config key) but not a native API delivery layer. No published rate limits, no response time SLAs, no API performance benchmarks. The Staging Sync Server uses slow SOAP/WCF over HTTP. The REST service has no caching layer documented.

Official .NET NuGet packages exist: Kentico.Xperience.Libraries (external app integration), Kentico.Xperience.AspNet.Mvc5 (MVC integration), Kentico.Xperience.StoreApi (e-commerce REST). The .NET SDK is functional and typed. Zero official JavaScript, TypeScript, Python, Ruby, or mobile SDKs for KX13 — JS consumers must make raw HTTP calls to the REST API. Community modules exist on DevNet but are not official Kentico SDKs.

Approximately 10–15 named connectors documented (Salesforce, Dynamics 365, Zoho, Marketo, SiteImprove, Recombee, SharePoint Online, Bynder DAM, Google Search Console). No formal marketplace with a counted catalog. The Integration Bus framework enables custom bidirectional connectors built as .NET classes, but requires custom development. Significant gaps in AI services, translation, and CDN connectors.

Rich traditional DXP extensibility in .NET: custom modules via CMSModuleLoader, global event handlers for object lifecycle events (Insert/Update/Delete on any Xperience object), custom page types with full field definitions, macro expressions for runtime resolution, custom form controls for admin UI, and standard ASP.NET Core MVC patterns for the live-site layer with DI and middleware. No low-code extension approach and no modern App Framework with sidebar widgets, but deeper than most traditional DXPs of this generation.

SSO supported via WS-Federation (ADFS, Azure AD) and OIDC (documented); Windows Integrated Authentication via IIS for domain environments. Azure AD and Azure AD B2C supported via Microsoft.Identity.Web NuGet packages. SAML 2.0 NOT natively supported — only SAML 1.0 is built-in; SAML 2.0 requires a third-party module (e.g., miniOrange). No native MFA — must be enforced at the identity provider level (Azure AD Conditional Access, ADFS MFA policies). API keys not applicable — REST API uses HTTP Basic/digest auth.

Full RBAC: roles aggregate permissions, users get permissions only through roles. Permissions enforced at module level (admin UI features), page-type level (all pages of a given content type), and per-page/section ACL (configured in Pages > Properties > Security). CheckPermissions() method on DocumentQuery enforces read access on the live site. Page permission inheritance down the tree. No field-level permissions — granularity stops at content item/page.

Kentico Xperience 13 is on-premises software — SOC 2 Type II and ISO 27001 apply to Kentico's SaaS product (Xperience by Kentico), not to KX13 running on customer infrastructure. GDPR compliance tooling is built in (consent management, data protection settings in admin UI). For KX13 deployments, all compliance certifications (HIPAA, FedRAMP, SOC 2, ISO 27001) are entirely the deploying organization's responsibility. The GDPR tools and documentation provide a foundation, but no vendor certification applies.

Three critical/high CVEs disclosed in 2025: CVE-2025-2746 and CVE-2025-2747 (both CVSS 9.8) are authentication bypass flaws in the Staging Sync Server actively exploited in the wild and added to CISA KEV with a November 2025 remediation deadline. CVE-2025-2748 chains stored XSS via ZIP file upload to achieve pre-authentication RCE when combined with the auth bypass CVEs. With EOL approaching December 2026 and the product already in security-only support, this pattern is expected to worsen as researchers continue targeting legacy code.

Self-hosted on IIS + Windows Server is the primary deployment model; Kentico provides Azure App Service deployment documentation with ARM templates and autoscaling guides. Azure VM also supported. No Kentico-managed SaaS option for KX13 — that exists only in the successor product. No Docker or Linux support — Windows-only due to .NET Framework 4.8 admin application requirement (live-site ASP.NET Core layer can run on Linux but without the admin). Flexibility is decent but platform-constrained.

No uptime SLA from Kentico for KX13 — it is self-hosted software and uptime is entirely the customer's or their hosting provider's responsibility. Kentico's only remaining support commitment is security hotfixes through December 2026; after January 1, 2027, no patches, no support, no recourse. Customers on Azure App Service can leverage Azure's own SLA (99.95% Standard tier) but that is independent of Kentico. The per-rubric instruction is explicit: self-hosted means no vendor SLA.

Web farm support is built-in and well-documented: multiple IIS nodes share database and content storage, with session state options (InProc/StateServer/SQLServer) to support or avoid sticky sessions. Azure App Service horizontal autoscaling is documented. Azure CDN integration available for static content offload. Load balancers (IIS ARR, Azure LB) sit in front of web farm nodes. No published scale limits or enterprise-scale benchmarks. The operational complexity of managing IIS web farms is significant compared to SaaS alternatives.

No built-in backup or DR tooling in KX13 — disaster recovery relies entirely on SQL Server backup/restore and file system backups (project folder, assets folder). The Hotfix and Upgrade Utility creates a LocalDB backup before applying hotfixes, and Kentico documents the pre-upgrade backup procedure (SQL database + project folder + ~/assets). Objects Recycle Bin provides soft-delete recovery. No documented RTO/RPO targets, no vendor-provided DR solution, no geo-redundancy from Kentico.

Full local development is possible using IIS Express with SQL LocalDB (auto-installed by the installer) and Visual Studio 2019/2022. The live-site ASP.NET Core MVC project runs locally with hot reload. However, local development is Windows-only — .NET Framework 4.8 admin application requires IIS on Windows. Mac/Linux developers cannot run the admin application locally. No lightweight emulator or containerized dev environment. Compared to modern platforms with `npm start` local dev, the barrier is high.

Built-in Continuous Integration module serializes object and configuration changes to XML files on the file system for source control (Git or TFS). However, the CI module must not run in production — it is a development-environment-only feature, adding operational friction. Content promotion between environments uses the Staging Sync Server (the same WCF service exploited by CVE-2025-2746/2747). No branch-per-PR content environment support. Standard Azure DevOps/GitHub Actions pipelines call MSBuild for deployment. CI serialization works but is cumbersome compared to modern migration CLIs.

docs.kentico.com/13 remains live and comprehensive as of April 2026, covering developer, admin, and deployment scenarios with full feature coverage. API reference at docs.kentico.com/13api with code examples by feature area. DevNet hosts additional developer resources. Documentation is being maintained with migration path guidance to Xperience by Kentico as the primary focus now shifts. C#-only code examples throughout — no JavaScript, TypeScript, or multi-language samples. No interactive playground.

Zero TypeScript or JavaScript support for KX13 content delivery. No official JS/TS SDK, no generated API client, and no OpenAPI spec for the KX13 REST service. The npm packages associated with the Kentico name (kentico-cloud-delivery-typescript-sdk, @kentico/kontent-delivery) belong to Kontent by Kentico — a different SaaS product. Frontend developers consuming KX13 content must make raw HTTP calls with manually crafted request/response types. This is a fundamental architectural limitation of the legacy .NET Framework product.

From January 1, 2026, KX13 enters security-only support — no features, no enhancements, no bug fixes, only security hotfixes until December 31, 2026 EOL. In 2025, release activity was minimal: sporadic security hotfixes via DevNet, no Refresh releases. The product's active development lifecycle effectively ended in 2023-2024 as Kentico shifted all engineering investment to Xperience by Kentico.

A structured historical changelog exists at docs.kentico.com/13/release-notes-xperience-13 covering the full KX13 release history, and hotfix packages with bug fix lists are available on the DevNet portal. The documentation is complete as a historical record. However, 2025–2026 changelog activity is minimal (security hotfixes only), and the docs site marks the product as legacy with no ongoing changelog investment.

Kentico is commendably transparent about KX13's future: the EOL date (Dec 31, 2026) is publicly documented, the support lifecycle page clearly states what support is available in each phase, and roadmap.kentico.com has a dedicated 'Kentico Xperience 13 – Refresh candidates' tab. However, the roadmap is effectively frozen — no new features are planned, and the tab exists only to acknowledge open requests that will not be addressed. Transparency about shutdown is good; future product direction is nil.

In its security-only phase, KX13 introduces no breaking changes — a trivially positive signal driven by inactivity, not discipline. The more meaningful concern is the migration story: moving from KX13 to Xperience by Kentico is a complete rebuild with no automated upgrade path, requiring new content models, widget rebuilds, and architecture decisions. Kentico provides migration guidance and a Migration Tool, but the scope is effectively a greenfield project. Historical breaking change management within KX13's active years was adequate.

KX13 has an existing community concentrated on legacy users who have not yet migrated. The primary legacy hub is devnet.kentico.com, which predates the community.kentico.com portal. Stack Overflow has modest KX13 question history. GitHub Kentico org repositories include some KX13 open-source tools. However, community activity is visibly shifting to XbK, with new community investment (AI Development Hub, MVP program, Slack) directed at the new platform. The KX13 community is in managed decline.

Kentico's community engagement investment is now entirely focused on Xperience by Kentico — MVP programs, Community Leader awards, AI Development Hub, and Slack workspace are all XbK-oriented. KX13-specific engagement is limited to migration support channels and legacy issue resolution. New content creation around KX13 is almost exclusively migration guides from partners. The vendor is actively steering the community away from KX13, which is the right business decision but means KX13 engagement is minimal.

The 500+ Kentico agency partner network still exists, and many partners retain KX13 expertise to service existing client bases. However, partner energy has pivoted almost entirely to XbK migration projects — partners like Americaneagle.com, Cantarus, and i3 Digital are publishing KX13 EOL migration guides, not KX13 implementation case studies. No new partners are certifying on KX13; certification investment is in XbK. The ecosystem is present for support and migrations but not for new builds.

Third-party content around KX13 in 2025–2026 consists almost entirely of EOL warnings and migration planning guides — not tutorials, courses, or implementation content. Historical content (older Pluralsight courses, DevNet tutorials, blog series from 2019–2022) exists but is outdated. YouTube KX13 content is sparse and dated. The content ecosystem has effectively stopped producing KX13 learning material; all new content is migration-oriented or XbK-specific.

KX13 developer talent exists — ZipRecruiter shows Kentico CMS developer roles at $18–$62/hr, Upwork and Toptal list freelance KX13 specialists with versions 5–13 experience. For support and maintenance of existing sites, talent is findable. However, the talent pool is declining as developers transition to XbK or other platforms. Hiring for new KX13 projects is rare; most demand is for legacy support or migration work. The .NET Framework requirement (not modern .NET Core) narrows the pool further.

KX13 has strongly negative customer momentum: the platform is in terminal decline with a fixed EOL of December 31, 2026. No new customers are starting projects on KX13 — every partner conversation is about migrating off it. Kentico's own communications, partner ecosystem, and analyst coverage all frame KX13 through the lens of exit. The question is not 'should we adopt KX13?' but 'when are we leaving KX13?' Revenue figures reported for Kentico reflect XbK growth, not KX13.

Kentico as a company is financially sound — privately held, profitable, $56.7M revenue in 2025 (+35% YoY), operating since 2004. The company will not disappear before the KX13 EOL date, and security hotfixes will be delivered through December 31, 2026 as committed. However, from the KX13 product perspective, the investment is effectively zero and the product is being formally terminated. Scoring reflects vendor stability (positive) offset by the product lifecycle reality (terminal).

KX13 has no competitive positioning for new projects — it is not evaluated against Sitecore XP, Adobe AEM, or any other DXP in new procurement decisions. Analyst coverage (Gartner, Forrester) does not include KX13 in current Wave/MQ evaluations; the Kentico entry in analyst reports refers to Xperience by Kentico. Partners universally recommend against new KX13 deployments. The platform competes only in the 'do we need to migrate this year or can we wait?' conversation, which is not a competitive win scenario.

Gartner Peer Insights shows KX13 Legacy at 4.3/5 with 204 reviews — reflecting genuine satisfaction with the platform's capabilities during its active years but tempered by architectural criticisms. Recurring complaints include: forced application recompilation for code changes causing downtime, limited improvements over Kentico 12 Portal, backend dependency for page type customization. Users who adopted early describe the product positively for mid-market content needs; later reviewers reflect frustration at the dead-end migration situation. Per the scoring formula, 4.3 with 200+ reviews = 60–72, reduced by architectural and lifecycle complaints.

v13 pricing was historically available from partner and third-party sites: Business $12,500/year, Enterprise $22,300/year, annual maintenance renewal ~30% of license fee. As of 2026, kentico.com/platforms/kentico-xperience-13 still exists but the main 'How to Buy' page promotes Xperience by Kentico exclusively. Specific v13 tier pricing requires contacting a partner or sales. Better than fully opaque DXPs (AEM, Sitecore) due to partner-published rates, but official channel no longer surfaces v13 pricing clearly.

Annual subscription model (all customers moved from perpetual to subscription by June 2024). Fixed annual cost — Business ~$12,500/year, Enterprise ~$22,300/year — with no consumption-based metering or per-API-call surprises. Predictable cost structure is a genuine positive. Forced migration from perpetual to subscription in 2024 was disruptive and eliminated the perpetual-license model. Multi-server deployments still require Enterprise tier.

Business tier provides core DXP: full CMS, personalization, marketing automation, eCommerce for single-server deployments. Enterprise tier gates multi-server load balancing, advanced eCommerce tiers, and higher-volume marketing features. Feature set is now frozen — in security-only support mode for 2026, no new features are added to any tier. Gating is moderate but the frozen state and EOL make tier differentiation less meaningful for procurement decisions.

Annual subscription contracts only. No monthly billing option published. No documented startup, nonprofit, or education pricing programs. EOL status makes new long-term contract commitments unusual — buyers should not be signing new multi-year v13 contracts given the December 2026 EOL. Exit terms not publicly documented. Typical mid-market DXP inflexibility, compounded by the EOL situation reducing any vendor motivation to offer flexibility.

30-day evaluation license available via Kentico Client Portal for local testing. No permanent free tier, no community edition, no open-source option. Business starts at $12,500/year, Enterprise at $22,300/year. Developer, staging, and QA installations are included under paid licenses at no extra fee, which limits per-environment costs but does not provide a free production path.

v13 requires Windows Server or Azure Windows VM, IIS with ASP.NET 4.7/4.8 and ISAPI configuration, SQL Server (2012–2022, Express supported), .NET Framework 4.8, plus a license key from Kentico Client Portal. The administration UI is ASP.NET Web Forms. Setup typically takes 1–2 days for an experienced .NET developer from zero. Significantly more complex than cloud-native or headless platforms and more complex than the successor XbK with its .NET CLI templates.

Small-to-medium v13 projects: 3–6 months, $25,000–$50,000. Enterprise with complex integrations or eCommerce: 6–12 months, $50,000–$150,000+. The .NET Framework / Web Forms tech stack and Windows-centric deployment add complexity. New implementations on v13 in 2026 should be exceptional; most activity is migration/exit work. G2 reviews note higher-than-expected development costs versus open-source PHP alternatives.

v13 requires .NET Framework 4.8 and ASP.NET Web Forms knowledge — a legacy skillset that many .NET developers have moved away from in favor of .NET 8+ and ASP.NET Core MVC/Razor Pages. Kentico v13-specific expertise is increasingly scarce as the platform approaches EOL, with experienced consultants focusing on migration work. Premium over generalist .NET development is moderate-to-high; the talent pool is contracting. Lower premium than AEM/Sitecore specialists but higher than modern .NET or headless platforms.

v13 requires Windows Server (on-prem or Azure Windows VM), IIS, and SQL Server — a more expensive hosting stack than Linux-based or cloud-native alternatives. SQL Server licensing adds $3,000–$7,000+/year for Standard Edition on self-hosted. Azure deployment uses Windows App Service (premium tier) plus Azure SQL Database. A SaaS hosting option exists on kentico.com/platforms/kentico-xperience-13/platform/cloud, but self-hosted or Azure-hosted is the typical v13 deployment pattern. Total hosting: $10,000–$50,000/year depending on scale.

Self-hosted or Azure-hosted v13 requires ongoing Windows Server patching, IIS configuration management, SQL Server maintenance (backups, updates, performance tuning), and application-level monitoring. In 2026, the platform receives only security hotfixes — no automated patch management or regular platform updates. This increases the ops burden for proactive vulnerability tracking. Part-time to full-time ops person required depending on deployment scale. Significantly more ops-intensive than cloud-native or SaaS-managed platforms.

High lock-in. Content is accessible via API for export. However, the .NET Framework 4.8 / ASP.NET Web Forms application code is non-portable — widgets, macros, modules, and event handlers are proprietary and must be rewritten for any target platform. Migration to Xperience by Kentico is a 'controlled replatforming', not an upgrade; migration to any competitor platform is a full rebuild. EOL by December 2026 forces all v13 customers to exit, making this an imminent and mandatory exit cost for every current customer. No documented tooling for migrating content to competitor platforms.

KX13 has a genuinely complex mental model: a dual-application architecture (admin on .NET Framework 4.8 + live site on ASP.NET Core/MVC 5), two parallel development paradigms (Portal Engine with Web Parts still used for admin UI customization, alongside MVC/Core), proprietary Page API for content querying, and content tree-based routing with Page Types and transformations. Portal Engine is a Web Forms-era system requiring its own conceptual framework separate from the ASP.NET Core live site. Not as severe as AEM or Sitecore XP but meaningfully more complex than modern DXP platforms.

KX13 has a dedicated tutorial site (docs.kentico.com/13tutorial), the xperience-training-13 GitHub training repository, Kentico University courses specific to KX13 development and online marketing, and full documentation at docs.kentico.com/13. However, with EOL scheduled for Dec 2026, Kentico has ceased active documentation investment — new resources and refreshes are directed exclusively at Xperience by Kentico. Existing resources remain usable but are aging and no longer being expanded.

The administration application runs on .NET Framework 4.8 (Web Forms), a legacy runtime that modern .NET developers increasingly lack familiarity with. Admin UI customization uses Portal Engine (Web Parts, templates) — a proprietary Web Forms-era development model. The live site runs on ASP.NET Core, which is mainstream, but the non-standard two-app deployment sharing a SQL Server database is unusual. Proprietary Page API syntax further adds to the unfamiliarity burden. Only the ASP.NET Core live site component aligns with modern .NET conventions.

The primary starting point is the xperience-training-13 GitHub repository, which is a training reference site rather than a polished production starter. Installation is via Windows installer rather than CLI or NuGet package, requiring IIS and SQL Server pre-configuration. No official starters for Next.js, Nuxt, or Astro exist; the platform predates the headless-first starter ecosystem. Old-style Visual Studio project template approach with limited CI/CD scaffolding.

KX13 has a heavy configuration surface: two separate IIS applications each requiring their own application pools, SQL Server with connection strings in both apps, license key management, CORS configuration for cross-app communication, and the requirement that Maximum Worker Processes must be set to exactly 1 (web garden mode breaks synchronization). Additional module settings managed through the admin database UI add to the burden. Environment management across dev/staging/prod requires careful coordination of all these components.

Page Types are defined in the admin UI and connected to auto-generated C# classes, creating a code-generation workflow that adds friction to schema changes. Removing or renaming fields risks data loss with no automated migration tooling. The CI/CD serialization feature can track some schema changes across environments but is limited in scope. Field count is not strictly limited but the database-backed schema tightly couples content structure to SQL Server, complicating schema evolution. Adding new fields is safe; structural refactoring is risky.

Page Builder provides in-context visual preview within the admin application for MVC/Core sites, with live widget rendering and section layout preview. However, preview is admin-application-side only — the live site app renders within an iframe in the admin, requiring CORS and shared domain setup to function. For headless API consumers, no preview mechanism exists within KX13; custom implementation is required in the target application. The preview setup is more involved than modern SaaS CMS platforms but functional for Page Builder sites once configured.

.NET/C# proficiency is mandatory for all live site and customization work. Kentico-specific API knowledge is required for content querying (DocumentQuery, PageTypeInfoProvider), event handling, and Page Builder widget development. Portal Engine knowledge is needed for admin UI customization (Web Parts, templates, macros). The platform uses a macro expression language for conditional logic and personalization rules. Certification available via Kentico Academy for KX13. Significantly higher specialization barrier than headless CMS or modern DXP platforms.

On-premises or hosted-server deployment requires dedicated infrastructure/ops involvement for IIS configuration, SQL Server administration, and deployment pipelines. Production implementations typically require 4-6 people: one or more .NET developers, a solution architect familiar with Kentico patterns, a DBA or developer with SQL Server experience, and separate content author training. Solo developer can explore the platform but production-grade delivery requires a small team with diverse skills. More demanding than cloud-native or SaaS DXP alternatives.

KX13 includes Page Builder for marketer-driven page composition from pre-built widgets, built-in Marketing Automation for campaign workflows, A/B testing, Contact Management, and email marketing — reducing ongoing developer dependency for marketing operations. However, the older admin interface has a steeper learning curve than modern CMS platforms, and content authors typically need several days of training. Adding new widget types or content types still requires developer work. Meaningful self-service capability exists but operational friction is higher than modern SaaS DXP platforms.

KX13 within-version hotfixes require multi-step manual execution: run the Hotfix Utility, apply SQL scripts against the production database, overwrite CMS/Lib files, rebuild the Visual Studio solution, then restart IIS. The KX13→XbK path is not an upgrade but a full platform rewrite costing $25k–$150k+ depending on implementation complexity. Not lower because the hotfix utility partially automates steps and weekly hotfix cadence is predictable; not higher because every hotfix demands IIS downtime and DB script execution.

From January 1, 2026, KX13 receives only security hotfixes — no other fixes or enhancements. Weekly hotfix cadence delivers patches regularly, but each patch requires the same manual IIS-downtime deployment process. CVE-2025-2746/2747 (CVSS 9.8 auth bypass, CISA KEV listed) and CVE-2025-2748 (XSS-to-RCE) were addressed in hotfixes 13.0.173/13.0.178/13.0.179 — turnaround was reasonable but the severity was exceptional. Not lower because patch cadence is weekly and advisories are clear; not higher because self-hosted deployments must manually apply each patch under downtime.

KX13 EOL December 31, 2026 forces a full platform rewrite — KX13→XbK is not a version upgrade but a ground-up replatforming affecting content models, custom APIs, Page Builder widgets, and all integrations. This continues a historical pattern of major forced transitions (CMS→EMS→XP13→XbK). While 12+ months notice was provided and migration tooling exists, the scope and cost of migration are unusually high for a product marketed as an upgrade path. Not lower because notice timelines were communicated and migration tooling is provided; not higher because the migration cost and scope are exceptional.

KX13 requires Windows Server, .NET Framework 4.8, SQL Server (Express through Enterprise), and IIS — all self-managed on customer infrastructure. No SaaS deployment model exists for KX13. Hotfix version must match DB version or the site will fail to start, coupling application and database deployments. The stack is moderate compared to Sitecore XP (which also requires Solr, Redis), but heavier than headless CMS or cloud-native platforms. Not higher because the entire stack requires customer-managed patching and version coordination.

KX13 has no built-in application performance monitoring or health dashboards. Customers must configure custom APM solutions (Application Insights, New Relic, etc.), SQL Server monitoring, IIS performance counters, and Windows Event Log alerting independently. The Xperience Portal monitoring features referenced in prior scoring belong to XbK SaaS — they do not exist in KX13. Score reflects full self-hosted monitoring burden with no native tooling. Not lower because basic Windows/IIS server monitoring tooling is widely available; not higher because zero built-in observability.

KX13 provides standard CMS content administration but no automated content hygiene tools — no orphan content detection, broken reference alerts, stale content identification, or content expiry workflows. All content governance relies on manual editorial discipline. Not lower because the admin interface is functional for day-to-day operations and the platform is mature; not higher because the absence of automated hygiene tooling is a persistent operational gap.

KX13 is entirely self-hosted, requiring customers to manually configure and tune ASP.NET output caching, SQL Server query plans and indexes, IIS application pools, and optionally integrate a distributed cache (Memcached or Redis) and CDN. No managed infrastructure or auto-scaling. Performance degradation requires manual investigation across the full stack. Score reflects the full self-hosted performance management burden. Not lower because .NET Framework performance tooling (PerfMon, SQL Profiler) is mature; not higher because all optimization is customer-owned.

Kentico's formal support is consistently praised in G2 reviews for fast response from in-house engineers. Both Standard and Premium tiers offer 24/7 support with SLA-based response times. However, from January 1, 2026, KX13 support scope is limited to security hotfixes only — complex customization issues, performance bugs, and feature questions are explicitly out of scope and require paid consultation. Not lower because the security hotfix scope is covered with good SLAs; not higher because the severely limited support scope in 2026 reduces the practical value of formal support.

Kentico DevNet Q&A is the primary community resource for KX13 legacy questions, with historical answers archived on DevNet. The MVP and Community Leaders programs provide some engagement, but the KX13 community is shrinking as EOL approaches and developers migrate to XbK. Stack Overflow coverage is modest. Community activity is declining as new KX13 questions become rarer and partners redirect effort to XbK. Not lower because DevNet archive preserves a large body of historical answers; not higher because the active community is small and declining.

KX13 is in security-only support mode from January 1, 2026 — only security hotfixes will be released; non-security bugs are explicitly excluded from the support scope. Weekly security hotfix cadence continues for security issues and critical CVE patches were delivered promptly (hotfix 13.0.179 for CVSS 9.8 CVEs). Non-security bugs reported after January 2026 will not be fixed under any support tier. Not lower because security issues are still addressed with reasonable turnaround; not higher because the product is effectively feature-frozen and non-security bugs are unaddressed.

Kentico Xperience 13 has a mature Page Builder with drag-and-drop widget placement, section layouts, and reusable page templates — marketers can assemble landing pages from pre-built widget libraries without developer involvement once the library is established. The feature set is complete but frozen: no new capabilities since the platform entered security-only mode in January 2026. Scores 65 rather than 70 because the aging tooling lacks modern UX refinements and the EOL trajectory creates confidence risk for marketing teams planning new campaigns.

Mature campaign management: campaign tracking with content grouping and conversion goals, A/B testing for pages and emails, email marketing with drag-and-drop Email Builder, marketing automation (Contact Management), and web analytics with source/demographic reporting. Campaign features were a primary selling point and are well-integrated across the platform. No multi-channel social orchestration or advanced campaign calendaring, and no new development planned given EOL status.

Standard SEO fields (meta title, meta description) on all page types, configurable URL slugs with vanity URL aliases and canonical URL support, automatic XML sitemap generation via built-in module, and 301 redirect management. These are natively built into the legacy platform — more complete than many legacy DXPs. No built-in SEO scoring, structured data authoring, or real-time optimization suggestions, but fundamentals are solid for a platform of its era.

Built-in Form Builder with conditional visibility rules, field validation, and submission tracking. CTA and conversion tracking integrated with the campaign module. A/B testing for pages and emails with configurable conversion goals. Marketing automation workflows can trigger on form submissions. All core performance marketing primitives are present but the tooling shows its age — no UTM parameter reporting, no native lead scoring, and no conversion optimization recommendations.

KX13 has a mature native personalization engine: rule-based content personalization using contact segments (persona assignment, geo-location, device, traffic source, visited pages), content variants swapped per persona/segment, and dynamic landing pages based on contact activity history. This is genuine rule-based behavioral targeting built into the platform, not a third-party dependency. No AI-driven real-time personalization or predictive segmentation, but the rule-based engine is capable and well-integrated with the contact database.

Native A/B testing for both pages and marketing emails: create test variants, configure conversion goals, run the test, and evaluate results via built-in analytics showing conversion rates and statistical comparisons. Winner selection is manual (the marketer reviews data and selects the winner), not automated. This is a complete A/B testing feature set for a platform of its era. No multivariate testing, no auto-winner, no integration with external experimentation platforms for feature flag testing.

Page Builder with template cloning and reusable widget library accelerates page creation once the initial developer investment is made. Inline editing in the live preview mode, content staging/preview before publish, and simple workflow shortcuts. Bulk operations on content items are supported in the administration. Content reuse via shared content tree items. The bottleneck is that any new page layout or new widget type requires developer involvement — the template library is foundational but static once built.

KX13 delivers to web (primary) and email (built-in email marketing module). Content can be accessed via REST or GraphQL APIs for headless delivery to mobile or other channels, but this requires custom frontend work — it's not a structured content-first authoring model. Social media integration covers scheduling and analytics but not content push via structured content types. Multi-channel capability exists architecturally but the platform is fundamentally web-first and requires developer effort per additional channel.

Built-in web analytics module with visitor tracking, campaign source attribution, page conversion tracking, and flexible dashboards — without requiring GA. Out-of-the-box social analytics (Facebook Insights, LinkedIn Stats, Twitter Analytics) surfaced in the platform UI. Google Analytics integration available via standard tag manager approach. Analytics is visible within the platform rather than purely external. No content decay reporting, no content performance scores, and the built-in analytics are less capable than dedicated tools.

Page Builder widgets provide component-based consistency — marketers choose from an approved widget palette rather than free-form HTML. Developers can lock widget properties or restrict widget availability per page type or page template. However, there are no design token management features, no global style system enforced at the platform level, and no automated brand compliance checks. Consistency is achieved through developer-constrained widget configuration, not system-level enforcement.

KX13 goes beyond basic OG meta management: built-in Facebook Insights, LinkedIn Stats, and Twitter Analytics are surfaced natively within the platform. Social scheduling and publishing is available through the social marketing module, allowing scheduling posts to Facebook and Twitter from within the DXP. OG/Twitter Card meta tag management is built in. This is a notably stronger social integration than typical CMSes. However, no Instagram/TikTok support and no user-generated content moderation.

Built-in media library with folder organization, image resizing/cropping on upload, and basic search. Media files are accessible across sites in a multi-site installation. The media library serves web content production adequately but falls short of DAM capabilities: no usage tracking (cannot see where an asset is used), no rights expiry management, no keyword/taxonomy-based asset search beyond folder browsing, and no video transcoding. For marketing asset volumes, most organizations integrate an external DAM.

Full multilingual content management: create language versions of pages with optional translation workflows, machine translation integration via built-in connector (Microsoft Translator) or custom integration, locale-specific URL management, and per-language campaign variants possible by creating locale-specific pages. Cookie consent and GDPR consent tracking built in at the platform level. The localization engine is mature and supports marketing workflows. Locale-specific campaign calendaring is achievable but requires manual page management per locale.

KX13 has native Salesforce CRM integration (bidirectional contact sync with activity tracking), HubSpot forms integration, and Marketo connector available via partner ecosystem. Zapier integration enables connection to a broader range of MarTech tools. The platform's contact activity data (page visits, form submissions, email opens) feeds CRM systems. This covers CRM and MAP categories with pre-built options. No native CDP integrations and no pre-built ad platform connectors, but the Salesforce + HubSpot + Marketo coverage is solid for a mid-market DXP.

Kentico Xperience 13 has a mature built-in e-commerce module with full product catalog management: standard products, products with options, product variants as independent SKUs, brands/manufacturers/suppliers, inventory tracking by variant, and file/image attachments per product. Product taxonomy via categories. This is a genuinely mature product content system developed over many platform generations — better than early-stage or headless approaches. Not a full PIM and lacks advanced attribute modeling, but coverage is solid for SMB/mid-market commerce.

Legacy e-commerce module includes catalog discounts, order discounts, volume discounts (tiered pricing), Buy X Get Y promotions, product bundles, coupon codes, and free shipping rules — a more complete promotional toolkit than many DXPs of its era. Category management enables basic product organization. No search result merchandising, no AI-driven product recommendations, and no dedicated product spotlight widgets, but the discount/promotions engine covers standard merchandising scenarios.

Kentico Xperience 13 is a self-contained commerce platform — it does not integrate with Shopify, commercetools, BigCommerce, or Salesforce Commerce Cloud natively. The k13ecommerce GitHub package exists specifically to bridge legacy commerce data into Xperience by Kentico for migration purposes, not as a live integration. Any external commerce platform integration requires fully custom development. Scores 30 (webhook-only custom) because the platform's model is standalone commerce, not commerce synergy.

KX13's tightly coupled content + commerce architecture allows product listing pages and product detail pages to be managed as content pages, blending editorial copy with product data. Page Builder widgets can embed product listings or individual product cards within editorial pages. However, shoppable content is not a first-class authoring pattern — there is no built-in 'shop the look' template, no inline add-to-cart within editorial articles, and no lookbook page type. Buying guides and editorial commerce pages are achievable but require developer-built templates.

KX13's configurable checkout is part of the native commerce module — checkout steps are configurable and can be extended with custom .NET widgets. Trust badges, upsell banners, and cart messaging are achievable within the platform's checkout pages, which can reference Page Builder or custom templates. This is better than pure-commerce platforms because the checkout templates live in the CMS. However, it requires developer work to add CMS-managed promotional content to checkout flows rather than being marketer self-service.

Email marketing module can trigger transactional and promotional emails based on order events — order confirmations, shipping notifications, and follow-up sequences are achievable using the marketing automation and email marketing features. Order confirmation pages are CMS-templated and configurable. Post-purchase review solicitation requires marketing automation workflow configuration. All post-purchase content is technically manageable from the CMS but not as no-code functionality for marketers.

KX13 supports customer-specific pricing via customer discount groups and volume discount tiers. Registered user accounts with customer-specific catalogs can be scoped using the existing access control model. Quote request flows can be built using the Form Builder tied to product pages. Gated product documentation is achievable via page-level ACLs. These B2B primitives exist but they are not packaged as first-class B2B content features — they require assembly from generic platform capabilities rather than purpose-built B2B tooling.

Built-in Smart Search (Lucene-based) supports full-text search across content and products, with configurable search results pages and basic faceted filtering using search indexes. Product search within the e-commerce module. Content-product blended search results are achievable by configuring combined search indexes. No AI-powered relevance ranking, no synonym management UI, and no search analytics beyond basic query logging. Adequate for mid-market sites but not competitive with modern search platforms.

Time-based promotional content is achievable: page publishing/unpublishing can be scheduled for campaign start/end dates, discount codes with date ranges, and promotional banners managed via Page Builder widgets with scheduled visibility. The campaign module can group promotional pages with start/end dates. No countdown timer widget out of the box, no channel-specific promotional targeting, and tiered pricing tables require developer implementation, but scheduled promotional content management is a viable core capability.

Multi-site installation can serve multiple storefronts from a single KX13 instance, with shared product catalog data and site-specific editorial content managed in separate site content trees. Product types and catalog structure are shared across sites, but each site can have its own pages, promotional content, and design. Some content duplication is necessary for storefront-specific messaging, and the shared database constraint means absolute data isolation between storefronts is not achievable. Adequate for related brands sharing product data.

Product pages support multiple images per product, video embed widgets (YouTube/Vimeo iFrame), and basic image gallery widgets via Page Builder. Image transformations (resize, crop) are built into the media library. No 360-degree product views, no AR/3D model support, no image hotspot tooling, and no native zoom widget — these require third-party JavaScript integrations or custom widget development. KX13's visual commerce is basic image+video, typical of a platform from its era.

KX13 has no marketplace or multi-vendor content management capabilities. The commerce module is designed for a single-seller model — there is no seller profile management, no seller-contributed product descriptions, no multi-vendor content moderation, and no review aggregation by seller. Building marketplace functionality would require extensive custom development on a platform approaching EOL, making it an inadvisable investment.

KX13's multilingual engine applies to product content: product names, descriptions, and page-level editorial can have language versions. Currency management is native to the commerce module with multi-currency pricing. Locale-specific URL management for product pages. Translation workflow can be applied to product pages. Regional regulatory content (EU product labels) can be managed as locale-specific content variants. No structured data localization for attributes/specifications without custom development.

Campaign conversion goals can be linked to product page visits, add-to-cart actions, and order completions — providing some content-to-revenue attribution within the KX13 analytics module. The 30+ built-in store reports include sales by source and campaign performance. This is better than platforms with no commerce analytics, but revenue attribution at the content-item level requires custom configuration, and there is no out-of-the-box content-assisted conversion tracking across full customer journeys.

Page-level ACLs allow read/write/create/delete/destroy permissions per role or user on individual content tree nodes and their children, enabling genuine department-level content scoping. SSO via SAML 2.0 and claims-based authentication with role synchronization from identity providers. RBAC with multi-role users across multiple sites. Audience-based content display rules via the personalization engine enable content visibility based on user segments. More mature than many peers — the legacy platform had years to harden this feature set.

Document versioning with comparison and rollback, workflow with approval states and email notifications, content taxonomy via categories and tags, and media library organization. These form a basic knowledge management foundation. No dedicated knowledge base templates, no content freshness/expiry tracking, no expertise mapping, and internal search requires Lucene-based configuration to be effective. Adequate for structured intranets but not purpose-built for knowledge management.

Community features (forums, groups, social interactions) were removed from Kentico Xperience 13 — they existed in KX8/KX9/KX12 but are explicitly absent in KX13. Intranet capabilities in KX13 are limited to basic content publishing, document libraries managed as media libraries, and workflow approval. No purpose-built employee portal module, no employee directory, no push notifications, no mobile app. Investing in employee experience on a platform in security-only support through Dec 2026 is inadvisable, and partners actively steer clients away from new KX13 intranet builds.

Basic internal communications are achievable via KX13's content management: news pages can be published to authenticated intranet users, personalization rules can target department-specific audience segments with relevant news content, and email marketing can send department announcements. However, there is no acknowledgment tracking, no mandatory-read workflow, and no notification/alert system for new content. Internal comms is a workaround use of general marketing features, not purpose-built tooling.

KX13 has no native people directory, org chart, or HR integration capabilities. An employee directory could technically be built using custom page types and content items, but this requires significant developer effort on a platform approaching EOL. The contact database (used for marketing) stores external contacts, not internal employee profiles with skills/expertise. There is no Workday, BambooHR, or Active Directory org chart integration.

Basic document publishing with version control and workflow approval is achievable using KX13's standard content management: file attachments, content versioning, workflow states for review/approval, and role-based access control for policy documents. However, there is no mandatory acknowledgment tracking, no automated review-date reminder, no policy expiry enforcement, and no audit trail specific to policy compliance. The platform offers document publishing primitives but not a policy management system.

KX13 has no structured onboarding journey features. Basic onboarding pages could be built as content pages with role-based access for new hires, but there is no progressive disclosure mechanism, no task checklist widget, no HR system trigger for new-hire portal provisioning, and no 30/60/90-day content path tooling. With community features removed and EOL approaching, any onboarding content delivery on KX13 would require substantial custom development.

Lucene-based Smart Search indexes all KX13 content — page content, document metadata, and media library — with full-text search and configurable faceted filtering. A dedicated search results page type is available. No federated search across external systems (SharePoint, Confluence, network drives), no AI-powered relevance ranking, and no search analytics dashboard. Search quality within the platform is adequate for a moderate content volume but falls behind modern enterprise search solutions significantly.

KX13 delivers responsive web content optimized for mobile browsers but has no native mobile application, no push notification capability, and no offline content access. The content management administration interface is desktop-focused and not mobile-optimized for on-the-go publishing. Frontline and deskless workers would access an intranet via mobile browser only with no app store presence. No kiosk mode or shared-device management.

KX13 has no native learning management features and no pre-built LMS integrations. Training content can be published as HTML pages with access control, but there is no course structure, no completion tracking, no certification management, and no integration with Cornerstone, Workday Learning, or other LMS platforms. Any learning functionality would require custom development against the KX13 API on a platform heading to EOL.

Community features — forums, groups, social interactions — were explicitly removed from Kentico Xperience 13 compared to KX12. KX13 has no commenting, no reactions, no discussion threads, no peer recognition, no polls, and no idea submission. This is a deliberate product decision to focus KX13 on web, marketing, and commerce rather than community/social. Score 15 reflects near-absence of any social features.

KX13 has no pre-built integration with Microsoft 365/Teams, Google Workspace, or Slack. Email marketing and notification emails use the platform's own SMTP integration. No embedded Teams/Slack content cards, no bot notifications, and no single-pane integration with workplace productivity suites. Custom webhooks via the API could theoretically trigger external system notifications, but there are no marketplace connectors for workplace tools.

Content versioning with comparison and rollback provides a basic archival history. Workflow states can include an 'archived' state for inactivating content. Content publishing schedule allows setting publish/unpublish dates — the unpublish date serves as a de facto expiry mechanism. However, there is no automated review-date reminder, no stale content flagging, no ownership assignment per content item for accountability, and no formal archival workflow distinct from deletion.

KX13's built-in web analytics provides page view counts and visitor session data, which can be filtered per site. Campaign-level analytics shows content engagement by source. However, there are no department-level analytics dashboards for intranet ROI, no failed internal search term reporting surfaced in the UI, no adoption/engagement heatmaps, and no intranet-specific content performance metrics. Analytics is oriented toward external marketing, not internal comms measurement.

Kentico Xperience 13 supports multi-site from a single installation (true multi-tenancy in vendor terminology), but all sites share a single database and application instance. Personal data cannot be completely isolated between sites in a shared installation — explicitly documented as a known limitation. Organizations requiring strict data isolation between brands must run separate installations. Silo-based via site permissions, not genuine tenant isolation. Scores 50 (low end of silo-based range) due to the shared-database data leakage risk.

Multi-site installation shares Page Builder widgets, page templates, media library, and content document types across all sites in the instance. Global shared content is achievable by placing documents in a shared site content tree. However, there is no brand-override system for shared widgets, no design token management, and no centralized governance over which sites can access shared components. The sharing model works for organizations that trust all sites to share the same asset pool.

Central admin interface manages all sites with per-site role assignments and content tree ACLs. Workflow with configurable states enables content approval at the page level across sites. Global administrator can manage all sites while site-specific admins are scoped to their site. No cross-brand approval hierarchies, no global content policy enforcement dashboard, and no automated compliance checks. The governance model is standard for a platform of this generation — functional but manual.

On-premises perpetual license model: additional sites within a single installation do not require additional licenses beyond server infrastructure costs. This is economically favorable for multi-brand scenarios compared to per-site or per-channel SaaS pricing. However, operational costs scale with infrastructure (servers, DBAs, patching) and brand-specific customization still requires developer investment. Full EOL on Jan 1, 2027 (security-only through Dec 31, 2026) means organizations must plan for migration — amortized migration cost increases effective per-brand cost.

KX13 supports per-site CSS stylesheets and page template assignments, allowing each site in a multi-site installation to have distinct visual identity: separate CSS, separate page layouts, separate header/footer templates. This is standard CSS/config theming. There are no design token management systems, no theme inheritance (brand A extends global theme), no per-brand typography/color palette management outside of raw CSS files. Developers implement brand differentiation; marketers cannot manage brand themes independently.

Multilingual content management applies per-site with locale-specific content versions and translation workflows. Per-brand translation approvals are achievable by scoping translator roles to specific site content trees. Cookie consent and GDPR compliance settings are configurable per site. The combination of per-site permissions + multilingual workflow provides a workable brand-locale governance model, but it is managed through general permissions rather than a purpose-built brand-locale governance framework. No per-brand translation vendor routing.

Analytics in KX13 is per-site: each site has its own web analytics dashboard showing traffic, conversions, and campaign performance. There is no cross-site portfolio analytics dashboard comparing performance across brands. A global administrator can switch between site analytics, but no aggregated portfolio view exists. Cross-brand analytics requires exporting data to an external BI tool (Power BI, Google Looker Studio) via GA4 or custom export.

Workflow in KX13 is configurable per content type or per site, allowing different approval chains for different brand sites. Global administrators can audit workflow activity across all sites. Workflow steps, approvers, and email notifications are independently configurable per workflow scope. This provides genuine per-brand workflow independence. No central workflow audit dashboard showing cross-brand publishing SLA adherence, but individual workflow configurations are flexible and independently maintainable.

Shared content tree in multi-site installation allows a 'global' or 'corporate' site to hold content items that other brand sites can reference or display via widgets. Corporate-level press releases, legal disclaimers, and product announcements can be placed in a shared content area accessible to all sites. However, there is no controlled override model — child brands cannot adapt corporate content with local variants; they either use it as-is or duplicate it. Content syndication is push-only with no override governance.

Per-site GDPR consent management with cookie consent banners configurable per site. Data subject request handling is configurable per site. Accessibility settings and compliance-related page metadata can be managed per site. However, there are no publishing guardrails that prevent non-compliant content from going live, no automated accessibility checking, and no per-brand data residency controls (all data is in the shared SQL Server instance). Compliance is administered per-site but not enforced systemically.

KX13 has no centralized design system management capabilities. Shared Page Builder widgets constitute a de facto component library, but there is no versioning of the component library, no centralized change management for propagating widget updates to all brand sites, and no brand-extension model for customizing shared widgets. When a shared widget is updated in the codebase, all sites consuming it are affected with no staged rollout or per-brand override.

A Global Administrator role has visibility and control over all sites in the KX13 installation, enabling central user management across brands. Per-site administrator roles allow autonomous brand team management within their site scope. SSO via SAML 2.0 works across the single installation. Users can hold roles across multiple sites. The model is functionally adequate for multi-brand teams. No per-brand user provisioning automation or cross-brand contributor role hierarchy beyond manual assignment.

Shared page types (content types) in KX13 multi-site installations provide a global model inherited by all sites. Brand-specific field extensions require creating separate page type variants or adding optional fields to the global type — there is no formal per-brand extension model that preserves the base type cleanly. In practice, organizations using KX13 for multi-brand often create brand-specific page type copies, resulting in forked models. Shared models work when brands share identical content structure.

KX13 provides per-site analytics and reporting — each site has individual dashboards for web traffic, campaign performance, and e-commerce metrics. There is no portfolio-level executive dashboard aggregating content freshness, publishing SLA adherence, or capacity metrics across brands. The Global Administrator can switch between per-site reports, but there is no cross-brand roll-up view. Portfolio reporting requires data export to external BI tools.

Kentico Xperience 13 has built-in GDPR tooling: consent management, personal data collection/erasure APIs, and right-to-be-forgotten workflows — but these require the Enterprise license edition and developer implementation. As an on-premises product, Kentico does not process customer data, so no vendor DPA is needed; the customer is data controller and processor. EU HQ (Brno, Czech Republic) gives organizational GDPR credibility. EOL Dec 2026 means no new compliance features will be added — only security hotfixes through year-end.

Kentico does not offer a BAA and Kentico Xperience 13 is not HIPAA-certified. As an on-premises product, HIPAA compliance is entirely the customer's responsibility — the customer controls the hosting infrastructure and must implement appropriate safeguards. No healthcare-specific implementation guidance exists in v13 documentation. The devnet.kentico.com Q&A explicitly states HIPAA compliance is implementation-dependent, not platform-provided.

GDPR tooling is built into v13 (Enterprise). CCPA can be addressed through the same consent management framework. On-premises deployment gives customers flexibility to implement regional requirements (PIPEDA, UK GDPR, LGPD) but Kentico provides no specific guidance or pre-built tooling for these. No FedRAMP, IRAP, C5, or HITRUST. EOL status means no new regulatory framework coverage will be added. Coverage is limited to GDPR tooling with no structured additional regional support.

Kentico's SOC 2 Type 2 attestation covers 'Xperience by Kentico' (the SaaS rewrite), not Kentico Xperience 13 (the legacy on-premises product). For an on-prem deployment, no SOC 2 audit exists because Kentico does not operate the customer's hosting environment. The company's SOC 2-certified development culture provides indirect assurance of development security practices, but the attestation cannot be cited for regulatory procurement of v13 on-prem. Score reflects no applicable SOC 2 for this product.

Kentico holds ISO 27001 certification covering their ISMS and development organization. This provides assurance that Kentico Xperience 13 was developed under ISO 27001-governed secure development practices. However, for on-premises deployments, the ISO 27001 scope does not extend to customer hosting environments — the certification covers Kentico's operations, not the customer's deployment. No ISO 27018. Scores mid-range: more than 'no ISO 27001' since development practices are covered, less than infrastructure-scope coverage.

At the company level, Kentico has a CAIQ Lite (CSA STAR Level 1 self-assessment) and an active HackerOne bug bounty program. These are company/SaaS-level attributes that provide partial relevance to v13's security posture. Not PA-DSS certified — the PCI compliance documentation explicitly states Xperience is not a certified PA-DSS application. No CSA STAR Level 2, FedRAMP, Cyber Essentials Plus, or HITRUST. CAIQ Lite plus HackerOne is a minimal additional cert portfolio.

On-premises deployment gives customers complete, contractual-free data sovereignty — data never leaves customer-controlled infrastructure. Customers can deploy to any datacenter, cloud region, or private environment. This is strong for data residency but lacks the structured vendor-managed multi-region SaaS options (the 19 Azure regions in previous scoring are features of the new SaaS product, not v13). No CDN residency leakage concerns inherent to the product. Score reflects high sovereignty capability without vendor-managed regional SaaS flexibility.

Built-in GDPR data erasure APIs and consent management with configurable retention exist in v13 (Enterprise). Customers manage backup policies and retention schedules in their own infrastructure — no vendor-managed backup SLAs apply. Content staging and database export tools provide data export capability. Right-to-erasure is API-based requiring developer implementation, not self-service for end users. Previous scoring credited vendor backup retention policies that apply only to the SaaS product.

Kentico Xperience 13 has a system event log recording user actions, content changes, and system events stored in the SQL database. Events can be forwarded to Windows Event Viewer via trace listeners. Custom IEventLogWriter implementations allow routing to external SIEM systems but require developer effort — not a native connector. No native push-based SIEM integration exists. Adequate basic audit capability for an on-prem product but not enterprise compliance-grade without custom integration.

Kentico Xperience 13's administration interface is built on older ASP.NET WebForms technology — not the modern React-based admin of the new SaaS product. The third-party page accessibility validation feature was deprecated and removed in May 2021 due to termination of the validation service. No formal WCAG 2.1 AA conformance report exists for the v13 authoring UI. No ATAG 2.0 assessment. EOL product status means no accessibility improvements are forthcoming.

No VPAT or ACR exists for Kentico Xperience 13. No Section 508 conformance statement applies to the current product. The only accessibility-related documentation is a 2009 DevNet article for CMS 4.1 (irrelevant) and the removal notice for the deprecated accessibility validation service. With EOL in December 2026 and security-only support, no VPAT will be produced. Score reflects complete absence of accessibility documentation for procurement purposes.

Kentico Xperience 13 has no native AI text generation. AIRA (text generation, rewriting, summarization, tone controls) is exclusive to Xperience by Kentico and was never backported to v13. No dedicated third-party AI text generation modules are documented for the v13 ecosystem, which is in security-only support heading to Dec 2026 EOL.

No native AI image generation, smart focal-point AI, or AI alt-text automation is documented for Kentico Xperience 13. All documented Kentico AI media features (image tagging, focal-point suggestion, alt-text generation) are in Xperience by Kentico via AIRA. Media management in K13 relies on manual DAM workflows.

Kentico Xperience 13 supports multilingual content and traditional TMS export/import workflows but has no native AI or machine translation capability. AI-powered bulk translation with tone-of-voice preservation is exclusive to Xperience by Kentico via AIRA. Score reflects manual localization only.

K13 provides manual SEO metadata fields (title, description, OG tags) and XML sitemaps but no AI-automated generation. Smart Search handles keyword indexing. AIRA's SEO-description generation and auto-tagging are XbyK-exclusive and were not backported to v13.

The official Recombee integration module provides ML-driven content recommendation routing — automatically surfacing relevant content to visitors based on real-time behavioral signals. Persona-based content delivery provides rule-assisted routing. No auto-tagging, smart scheduling, or duplicate detection AI features are documented for K13.

No agentic workflow capability exists in Kentico Xperience 13. The AIRA Agentic Marketing Suite (Content Strategist agent, multi-step orchestration, human-in-the-loop approval gates) is exclusive to Xperience by Kentico. K13 has workflow states and approval steps but no AI agent execution.

K13 provides a marketing analytics dashboard covering contact activity, campaign funnels, A/B test results, and persona distribution. Contact scoring is entirely rule-based, not ML-driven. No AI content gap analysis, topic clustering, or editorial priority recommendations are available.

No AI-powered content auditing capability is documented for Kentico Xperience 13. There is no brand voice compliance checking, quality scoring, or accessibility scanning AI. AIRA's Content Strategist agent (style compliance, tone profiling, severity-graded issues) is exclusive to Xperience by Kentico.

K13 ships native Azure Cognitive Search integration with scoring profiles for relevance tuning, autocomplete suggestions, and combined page+widget indexing (added in Refresh 1). Algolia integration is also available. However, Azure AI Search's semantic queryType is not supported by the K13 NuGet integration — search remains keyword-ranked, not vector or semantic.

The official Recombee integration provides a genuine ML-based recommendation engine — real-time machine learning generating content-based and user-based recommendations that automatically adapt to visitor behavior without manual rule configuration. This is authentic ML personalization, not rule-based segments. However, it requires a separate Recombee account and custom implementation, making it an external service rather than native.

No MCP server exists for Kentico Xperience 13. All official Kentico MCP servers (Content Types MCP, Documentation MCP, Management API MCP) are built for Xperience by Kentico only. Context7 can surface K13 legacy docs to AI agents for migration assistance but this is not a K13 content MCP server.

K13 has no built-in AI requiring vendor keys, but as a fully self-hosted .NET Framework platform, developers can integrate any AI provider (Azure OpenAI, OpenAI, etc.) via custom .NET modules using their own API keys. There is no native BYOK UI or documented AI provider configuration screen — all AI integration requires custom development.

K13 exposes a REST API, .NET SDK, and Integration Bus usable for AI agent consumption — pages and content types are accessible via structured API calls. No dedicated AI SDK, agent-optimized endpoints, or LangChain/LlamaIndex integration guides are documented for K13. All KentiCopilot developer AI tooling (MCP servers, Semantic Kernel integration) targets Xperience by Kentico exclusively.

K13 has no AI features requiring governance — no AI content generation, no AI agent workflows, no AI-generated content requiring audit trails or brand safety controls. Standard CMS role-based permissions and workflow approval steps exist but are unrelated to AI governance. Score reflects absence of any AI to govern.

No AI usage dashboards, AI credit tracking, or model performance analytics exist in K13. No AI features are built into the platform to observe. Marketing analytics provides traditional visitor and contact metrics only.