Optimizely PaaS DXP

Code-first content modeling via C# PageType/BlockType attributes with full .NET type system support. CMS 13 adds Custom Elements definable directly in Admin UI without code deployment, addressing the previous redeployment requirement for schema changes. Content Type Contracts (interfaces inheriting IContentData) enable flexible cross-type modeling and polymorphic references without package dependencies. Not higher because Custom Elements still rely on existing editor primitives rather than fully arbitrary schema design.

Strongly-typed ContentReference and ContentReference<T> for compile-time validated references; ContentArea for composition. Optimizely Graph provides full relationship traversal in GraphQL with Content Type Contracts enabling unified cross-type queries against all implementing types. Reverse lookups still require search/Graph integration rather than being natively bidirectional, which prevents a higher score.

BlockType system provides genuine structured content with SharedBlocks and LocalBlocks. CMS 13 adds Experiences and Sections — layout structures separate from content that editors can build, copy, and paste between sections with grid-based layouts. Templates and Blueprints allow predefined content structures with central management and export/import. Optimizely Graph exposes all blocks as typed structured data. Still HTML-rendering-oriented for rich text rather than fully portable like Portable Text.

Leverages standard .NET DataAnnotations (Required, StringLength, RegularExpression, Range) with inline UI enforcement. Cross-field validation via IValidate<T> supports complex business rules. Benefits from entire .NET validation ecosystem and is independently testable without CMS runtime. No CMS 13 paradigm changes but the foundation remains strong.

Every content change creates a new version with full history, diff comparison, and rollback. CMS 13 introduces Content Variations — multiple published variations of the same content item in the same language with delta-based storage and independent publishing lifecycles, effectively providing content branching. Variations are indexed to Optimizely Graph with unique identifiers. This directly addresses the previous gap of no content branching and brings PaaS parity with best-in-class versioning.

CMS 13 brings Visual Builder to PaaS as the default editing interface, replacing On-Page Edit (now disabled by default). Visual Builder provides a unified interface for creating and editing pages, blocks, experiences, and media with drag-and-drop shared blocks, interactive property highlighting, real-time responsive preview, autosave, and grid-based layouts. Experiences and Sections enable editor-driven layout composition without developer involvement. Not higher because data-bound content loading and advanced personalization flows still require developer setup.

XhtmlString property type with per-content-type toolbar configuration, custom plugins, internal link picker, and paste-from-Word. Output is stored as HTML (not portable AST), limiting multi-channel reuse without custom rendering. CMS 13 does not introduce a new rich text paradigm — HTML-only output remains the primary limitation versus headless platforms with Portable Text equivalents.

Media assets are typed content items with code-defined metadata schemas. URL-based image resizing via ImageSharp.Web or Cloudflare, plus focal point support. CMS 13 adds Content Manager with Graph-powered search across all content types, customizable grid views with orientation-aiding backgrounds for images and PDFs, and details panels for assets. Embedded Optimizely DAM integration NuGet package enables asset browsing, search, and selection from the DAM within the CMS. Still lacks AI-based smart cropping natively in CMS itself (that lives in CMP).

Pessimistic locking prevents concurrent edits — only one editor can work on a content item at a time. No real-time presence indicators, cursor sharing, or CRDT-based collaboration. CMS 13 release notes do not mention any real-time co-editing improvements; inline comments and project management for multi-page changes are async, not real-time. Typical of traditional DXP architecture.

Built-in multi-step Content Approval Workflow with per-content-type/path configuration, role-based approver steps, email notifications, and reject-with-comments. CMS 13 adds Templates & Blueprints for creating, exporting, and importing content templates with predefined values and layouts, plus auto-translation preserving hierarchy and structure. Draft translation allows translating unpublished content without prior publication. Scheduled jobs are fully configurable for automated or manual execution.

Two first-class headless APIs: Content Delivery API (REST) and Optimizely Graph (GraphQL, now mandatory) with auto-generated schemas. CMS 13 adds a C# (.NET) SDK for Graph with fluent API, strongly-typed results, caching, and authentication support. REST API is now included by default with OAuth configuration via appsettings.json and consistency with SaaS. An experimental REST API for managing websites and headless applications was introduced. Content Type Contracts enable unified cross-type queries.

DXP hosting includes Cloudflare CDN with automatic cache purge on content publish and built-in WAF. Optimizely Graph has its own CDN-accelerated delivery layer. Cloudflare page rules configurable via DXP portal. CMS 13 does not introduce edge compute, sub-second purge guarantees, or edge-side personalization — limiting the score.

CMS webhooks support publish, unpublish, move, and delete events with HMAC signing and basic retry. Optimizely Graph webhooks add reactive content workflow support. CMS 13 improves event indexing performance with a background worker queue and updates Opal webhook triggers with default authentication headers. Still lacks dead letter queues, event replay, and comprehensive filtering.

Content Delivery API and Optimizely Graph serve all content to any channel; Graph is now the mandatory primary content delivery layer in CMS 13. Code-first model means single content type definition drives both CMS editing and API schema. Content Variations are indexed to Graph with unique identifiers enabling variation-aware multi-channel delivery. External content from DAMs, PIMs, and CRMs can be integrated via Optimizely Connect Platform. Rich text output remains HTML-only (not portable AST) and SDK coverage remains .NET-focused.

Optimizely Visitor Groups is the rule-based personalization engine included in CMS 13 PaaS. Built-in criteria cover geographic location, referring URL, time of day, landing URL, number of visits, browser/device type, campaign (UTM), and form submission; criteria combine with AND/OR logic. ODP integration (separately licensed) adds ML-based real-time segment evaluation with <90s latency, and the 2026 Lytics Audience Sync enables importing external audiences into ODP for use in CMS Visitor Groups. Strong for rule-based segmentation; lacks behavioral depth of Sitecore xDB without ODP.

CMS 13 PaaS natively supports content variants per Visitor Group with in-editor preview per audience — editors assign different content blocks to different groups directly in Visual Builder. CMS 13 Content Variations add multiple published versions of the same content with delta-based storage, independent version history, and variation-specific preview URLs for experimentation and personalization. ML-driven personalization still requires ODP (separately licensed). Without ODP, personalization is limited to rule-based Visitor Groups — genuine native capability but not ML-driven.

Optimizely Experimentation is the gold standard in A/B and multivariate testing — the company was founded on this capability. The platform provides Bayesian and frequentist significance testing, sequential testing, CUPED variance reduction, multi-metric experiments with guardrail metrics, mutual exclusion groups, feature flags for gradual rollouts, and full-stack server-side experimentation. CMS 13 Content Variations further enhance CMS-native experimentation by enabling multiple published content versions with independent workflows for testing scenarios.

No native content recommendation engine in the CMS. Product recommendations available through Optimizely Recommendations (Commerce-only module) using collaborative filtering. Content recommendations require ODP (separately licensed CDP) or custom implementation. CMS 13 adds no recommendation engine. No purpose-built recommendation engine exists in PaaS CMS without additional licensed products.

CMS 13 (GA March 31, 2026) replaces Optimizely Find (Search & Navigation) with Optimizely Graph as the mandatory search engine. Graph SDK (Optimizely.Graph.Cms.Query) provides Boolean facets, decay/factor scoring, pinned results, IAsyncEnumerable streaming, cursor-based pagination, and field-level search with boosting. Content Manager in CMS 13 is a search-first interface powered by Graph with filtering across all content types. Graph is included in the CMS 13 license.

CMS 13 Graph SDK provides a strongly-typed fluent C# API compiling to GraphQL with .ToGraphQL() for debugging, custom cache eviction policies, single-key and Basic authentication modes, and support for IPrincipal-based access filtering. The SDK supports POCO deserialization and strongly-typed content models. Marketplace connectors for Algolia and Coveo remain available. Content Delivery API enables external search platform integration. The Graph SDK's extensibility surpasses Find's LINQ API with better debugging and caching controls.

Optimizely Commerce Cloud is a full-featured B2B/B2C commerce platform deeply integrated with CMS PaaS: product catalog, cart/checkout, order management, pricing engine, warehouse inventory, and promotions. Commerce is separately licensed but shares the CMS content model and editorial experience. Commerce Search v3 (Google Vertex AI Search) is GA as of September 2025; Commerce Search v1 EOL was February 2026.

Optimizely's native Commerce Cloud handles most commerce needs directly. For headless commerce patterns, integration with Shopify, commercetools, or BigCommerce is achievable via Content Delivery API and standard .NET HTTP clients. A 2025 commercetools partnership was announced. No pre-built product picker UI for external commerce platforms — integration requires custom development.

Optimizely Commerce Cloud provides purpose-built product content modeling: catalog structure with CatalogContentBase/ProductContent/VariationContent type hierarchy, product/variant/SKU hierarchies, rich product descriptions via CMS content blocks, product media management, and attribute-based product information. The content model natively handles product-specific data patterns with strong typing.

CMS 13 PaaS includes basic traffic analytics (page views, sessions, content performance) and search analytics. Optimizely Experimentation (separate license) provides sophisticated experiment analytics. CMS 13 does not add new analytics dashboards beyond what Graph-powered Content Manager provides for content discovery. No built-in behavioral path analysis, goal conversion funnels, or author productivity metrics. Most implementations integrate GA4 or Adobe Analytics.

Optimizely CMS integrates with GA4 and Adobe Analytics via standard tag injection. Optimizely Experimentation provides native analytics hooks for experiment metrics. ODP (separately licensed) enables cross-platform event tracking. No native GA4 connector with deep bi-directional data flow, but standard tag management patterns are well-documented. CMS 13 does not add new analytics integration capabilities.

Optimizely CMS supports multiple sites within a single instance. CMS 13 replaces SiteDefinition with Applications (with automatic migration), each with its own domain, start page, language configuration, and access controls. Content can be shared across sites via shared blocks and content areas. Per-application configuration enables different design systems while maintaining centralized content governance.

Multilingual content management is a core strength inherited from Episerver's Scandinavian enterprise roots. Every content item supports multiple language branches with independent publish status. Configurable language fallback chains. CMS 13 adds auto-translation that preserves original structure including page hierarchies, draft content translation support, global language context switching, and a redesigned Language Selector with branch/non-branch separation. Content Management API supports any valid language code without OS culture restriction.

Translation Integration Framework (TIF) abstracts TMS connectors with XLIFF export/import, translation status tracking, and automatic content import to language branches. Certified connectors on Optimizely Marketplace: Translations.com GlobalLink, Lionbridge, Phrase (Memsource), Smartling. Machine translation pre-fill (DeepL, Google Translate) available at connector level. CMS 13 auto-translation feature complements but does not replace TMS workflows.

Basic multi-brand support through Applications (CMS 13, replacing site definitions) with per-application access controls and content hierarchies. Content sharing across brands uses shared content folders. Centralized governance is possible but requires custom role configuration — no purpose-built brand management UI or cross-brand policy enforcement exists. Score limited to 45 given the absence of native multi-brand governance tooling.

CMS 13 introduces embedded DAM integration (EPiServer.Cms.DamIntegration.UI NuGet) built on External Sources via Optimizely Graph, with multiple access methods: embedded in editor, Content Manager picker, and dedicated picker. Graph and Opti ID are now included in the CMS 13 license, removing infrastructure barriers. However, CMP DAM itself still requires separate licensing and CMP API client credentials. The native CMS media library remains basic blob storage. The tighter integration and license-included Graph improve accessibility but the full DAM remains separately licensed.

Without CMP DAM, there is no native CDN or image transformation pipeline. With CMP DAM (separately licensed), CDN-based dynamic image resizing is available with asset renditions optimized for different platforms. CMS 13 DAM integration delivers assets via Graph-indexed External Sources. Focal point, WebP/AVIF conversion, and smart cropping are not documented as native capabilities — the CDN delivery is functional but not feature-rich by modern standards.

No native video hosting, transcoding, adaptive streaming, thumbnail generation, or caption management in CMS PaaS. The media library stores video files as blobs only. CMP DAM can attach metadata to video assets but provides no transcoding pipeline or player. CMS 13 release notes add no video pipeline. All video delivery requires external services (YouTube, Vimeo, Azure Media Services, AWS Elemental).

CMS 13 (GA March 31, 2026) makes Visual Builder the default editorial interface for PaaS, replacing On-Page Editing. Visual Builder provides unified editing for pages, blocks, experiences, and media with autosave, interactive property highlighting, and synchronized preview. Experiences use outline layout (flat ordered list of sections/components); sections use grid layout (hierarchical rows, columns, elements). Editors drag-and-drop shared blocks into experiences with automatic inline indexing to Graph. Custom elements definable in Admin UI. Server-side ASP.NET MVC rendering supported without requiring Graph.

CMS PaaS has mature multi-step approval sequences: configurable steps with one or more reviewers (user or role), deadlines per approval item, four-eyes principle enforcement (prevents authors approving own content), email + in-UI notifications, and database audit trail. CMS 13 Content Variations extend approval workflows to individual variations with independent version history. Gaps: no auto-escalation, no visual workflow designer for complex branching, no inline @mention commenting on content.

CMS PaaS has solid scheduled publishing with start/stop dates, automatic unpublish on expiry, and scheduled rollback to a previous version after a limited-duration publish. Projects provide atomic multi-item publish (bundle pages, blocks, products and publish simultaneously, either manually or scheduled). CMS 13 Content Variations add independent publishing lifecycles per variation. No native calendar view of scheduled content — the Projects list is a task-board, not a timeline visualization.

CMS 13 adds autosave in Visual Builder but no real-time simultaneous editing, no presence indicators, and no inline comments on content. The Projects feature provides the closest analog: project-level @mentions, comments, and scheduling coordination. Last-save-wins conflict behavior persists. This remains a genuine and persistent gap for enterprise co-authoring workflows.

Optimizely Forms (EPiServer.Forms NuGet) ships with CMS PaaS and provides conditional field display logic (AND/OR, equals/not-equals/contains/regex), multi-step forms with conditional step routing, progressive profiling, hidden visitor profiling, file upload, CAPTCHA, and database submission storage. Native connectors route submissions to Marketo, HubSpot, Salesforce, Pardot, Eloqua, Dynamics CRM, Acoustic, and Delivra. CMS 13 release notes list Forms app as 'coming next' — not yet updated for CMS 13 but existing Forms package remains available.

No native email sending in CMS PaaS — all email delivery routes through connected MA/ESP tools. Eight official first-party MA/ESP connectors are documented (Marketo, HubSpot, Salesforce MC, Pardot, Eloqua, Dynamics CRM, Acoustic, Delivra), all NuGet-based with field mapping. The integration depth is form-submission-to-ESP sync rather than full CMS-event-triggered sends or email preview in CMS. Breadth of connectors is above average for the dataset; depth scores it below the 70+ threshold.

CMS PaaS is a data capture and trigger source for external MA tools, not a native MA orchestration engine. Form submissions routed via MA connectors trigger nurture sequences in the connected platform; ODP behavioral events support audience building for personalization. No native drip campaign, lead scoring, or lifecycle stage management within the CMS itself. CMS 13 adds no marketing automation capabilities. Optimizely Campaign (separate product) provides these capabilities but is not included in PaaS.

Optimizely Data Platform (ODP) integrates with CMS PaaS bidirectionally: ODP JavaScript SDK tracks page views, form submissions, and custom behavioral events; ODP resolves identity across multiple identifiers and builds real-time audiences synced to CMS Visitor Groups (<90s latency). The 2026 Lytics Audience Sync extends ODP with external audience imports. ODP is separately licensed — the integration is real and documented but gated by additional cost.

Optimizely has a broad integration ecosystem across two channels: the official App Marketplace and the legacy Episerver Add-ons registry with hundreds of community NuGet packages. CMS 13 mandates Graph and Opti ID, establishing the Optimizely One composability foundation. Key first-party integrations span DAM, Graph search, Experimentation, ODP, Commerce, MA connectors, and Opti Connect Platform for event-driven connectors. The ecosystem is fragmented across old and new registries.

CMS 13 makes Graph mandatory (included in license), ensuring all CMS 13 deployments have access to Graph webhooks (doc.created/updated/deleted with wildcard filtering and content-status filtering). CMS PaaS retains the robust internal event system (IContentEvents, INotificationHandler<T>). OptiGraphExtensions community package adds webhook management UI. Gaps remain: no native webhook management UI in core, no signed payloads, no delivery logs in admin panel.

CMS 13 (GA March 31, 2026) introduces configurable preview routing with predefined tokens (Context, Host, Key, Locale, Path, Segment, Version), per-application and per-content-type routing in admin UI, and fallback route configuration. Content Variations provide variation-specific preview URLs with real-time synchronized preview ensuring accurate rendering of the variation being edited. Graph draft mode with AllowSyncDraftContent for headless draft preview. Gaps remain: no public shareable unauthenticated preview links, no branch/environment-per-PR preview.

Opti ID (mandatory in CMS 13) provides unified identity across all Optimizely products with custom role definition, content-tree ACLs (Read/Create/Change/Delete/Publish/Administer per node or subtree with inheritance), language-branch permissions, SSO via SAML/OIDC (up to 5 SSO connections), and SCIM provisioning with Entra ID, Okta, and PingOne. CMS 13 adds cloud license management interface. Gap: no field-level property permissions within a content type.

CMS 13 ships the Graph C# SDK with fluent API, strongly-typed POCO result deserialization, and query tracking for analytics, alongside the REST API for content modeling registered via AddCms(). The Content Delivery API (REST with Swagger/OpenAPI) and Optimizely Graph's GraphiQL playground round out a comprehensive API surface on .NET 10. Ongoing EPiServer to Optimizely namespace migration and remaining legacy inconsistencies cap the score.

CMS 13's Graph SDK adds client-side query result caching with custom eviction policies, single-key authentication by default (reducing auth overhead), and strongly-typed deserialization. These supplement Cloudflare CDN edge caching, IAsyncEnumerable streaming, cursor-based pagination, and named queries for server-side caching. Per-tier throughput limits remain undocumented publicly, preventing a higher score.

CMS 13's official Graph C# SDK is a significant addition with fluent querying, caching, and strongly-typed results, strengthening the mature .NET ecosystem (EPiServer.CMS.*, Optimizely.* NuGet, dotnet-episerver CLI). However, official SDK coverage remains .NET-first with only partial JS support via the Content Delivery API client; no official Python, Go, Ruby, PHP, Swift, or Android SDKs exist. Community @remkoj/optimizely-dxp-clients covers TypeScript Graph access but is not officially maintained.

CMS 13 introduces embedded DAM integration via the EPiServer.Cms.DamIntegration.UI package (requires Opti ID + active Graph), bringing native digital asset management into the CMS interface. The Optimizely Marketplace lists 100+ certified add-ons across CRM, DAM, translation, search, analytics, and commerce, with the commercetools partnership adding composable-commerce depth. The ecosystem is smaller than Adobe's or Sitecore's but benefits from certified partner vetting.

CMS 13 strengthens an already strong extensibility model: Visual Builder custom elements can be defined in the Admin UI without code deployment, Application Management replaces SiteDefinition with auto-migration and expanded host types, and content-type contracts are defined via .NET interfaces inheriting from IContentData. These supplement full ASP.NET Core DI, middleware, IContentEvents hooks, IConfigurableModule/IInitializableModule startup extensibility, and MVC tag helpers for Visual Builder.

CMS 13 retains ASP.NET Core Identity as its auth foundation with OIDC support for Azure AD, Okta, and other IdPs, and the Graph SDK defaults to single-key authentication with optional per-query Basic auth. SSO is available on all DXP tiers (not enterprise-gated), MFA is configurable via middleware, and OAuth client configuration is exposed through appsettings.json or DXP environment variables. Opti ID provides unified identity across the platform.

CMS 13 strengthens permission enforcement during user-deletion operations and adds file-extension whitelisting during import. The RBAC model remains built on IAccessControlList (read/create/edit/delete/publish per role per content path), custom roles, and claims-based authorization via ASP.NET Core. It still lacks field-level permissions and content-instance ownership scoping, holding the score to the custom-roles-with-content-type-scoping band.

Optimizely DXP holds SOC 2 Type II, ISO 27001:2022, ISO 27017:2015, ISO 27018:2019, PCI DSS v4.0.1, and TISAX, all verified by independent third-party auditors. A GDPR DPA is available for all DXP customers with EU data residency on Azure. PCI DSS v4.0.1 is notable for commerce use cases. Lack of HIPAA BAA and FedRAMP prevents a higher score.

CMS 13 adds explicit hardening: file-extension filtering during import, restricted file uploads by extension, and permission enforcement during user deletion. The .NET 10 runtime brings current security patches on top of a clean track record with no major public CVEs, regular third-party penetration testing, and Cloudflare WAF protection. Lack of a public bug bounty program remains the primary gap.

Optimizely PaaS offers both managed DXP hosting on Azure (Integration / PreProduction / Production App Service environments) and self-hosted deployment on any ASP.NET Core compatible infrastructure. CMS 13's .NET 10 upgrade ensures compatibility with modern container runtimes and Docker, and Application Management expands supported host types (Primary, Preview, Media, Edit, Redirect). Per rubric, both available = 70-80.

Optimizely DXP provides a documented 99.9% uptime SLA for production delivery environments on Azure, with status.optimizely.com currently showing All Systems Operational and only a small number of minor, promptly-resolved incidents in late March 2026. CMS 13's scheduled-job hang-detection logging improves operational visibility. 99.9% (not 99.95%+) keeps this in the 60-75 rubric band.

DXP manages horizontal scaling on Azure App Service with CPU/memory-based autoscale, CM/CD separation at the infrastructure level, and Cloudflare CDN edge caching. CMS 13's Graph SDK adds client-side query caching with custom eviction policies that improves delivery performance at scale. DXP tiers (Performance, Optimized, Premium) offer different scale envelopes, but specific published scale limits (entries, concurrent users, RPS) remain thin, preventing a score above 75.

DXP provides automated backups via Azure SQL geo-restore and Azure Blob geo-redundant storage, with multi-region failover only as a paid DR add-on. CMS 13 adds JSON content export for translations and Application Management auto-migration, improving data portability. RTO/RPO specifics remain non-public; per rubric, automated backups with export but no documented RTO/RPO scores 50-65.

CMS 13 runs on .NET 10 with standard developer tooling (.NET SDK, Visual Studio or VS Code, SQL Server LocalDB, Kestrel for local) and the Alloy sample project provides a working CMS within minutes. .NET 10 brings improved hot-reload for faster inner loops, and CMS 13 aligns default upload sizes between Kestrel and Azure. The SQL Server dependency (vs a containerized or lighter local alternative) still prevents a higher score.

DXP exposes a REST Deployment API and the dotnet-episerver CLI for programmatic deployments across Integration / PreProduction / Production with slot swapping. CMS 13's Application Management automates SiteDefinition migration and OAuth client configuration is now available via DXP environment variables, simplifying CI/CD secret management. GitHub Actions and Azure DevOps templates are available, but branch-per-PR content environments are still not natively supported.

CMS 13 release notes and overview at docs.developers.optimizely.com are comprehensive, covering each feature with migration guidance from CMS 12, and the Graph SDK docs include Search & Navigation API migration mapping. Swagger UI and GraphiQL provide interactive exploration, and Visual Builder tag-helper documentation is available. Docs remain .NET-only for framework guides, and PaaS content competes with SaaS CMS for visibility in the docs portal.

CMS 13 PaaS is firmly .NET-focused — the Graph C# SDK, Visual Builder tag helpers, and content-type contracts are all C#. Content Delivery API and Optimizely Graph can be consumed from TypeScript via the community @remkoj/optimizely-dxp-clients, but the official @optimizely/cms-sdk with TS type generation remains SaaS-only. There is no auto-generated TypeScript type generation from PaaS .NET content models.

CMS 13 PaaS reached GA on March 31, 2026, delivering on the Q1 2026 target — a major version introducing .NET 10, Visual Builder, mandatory Optimizely Graph, and Content Variations. Post-GA velocity continues: Opal Chat and AI tools for CMS 13 shipped April 7, 2026 — one week after GA. CMS 12 PaaS continues monthly minor releases with dedicated 2026 release notes. Strong cadence for an enterprise PaaS platform.

CMS 13 GA release notes (updated April 2026) are structured and comprehensive — covering Visual Builder, Content Manager, Content Variations, Translation enhancements, C# SDK, DAM integration, and Applications Management with clear descriptions of each feature. Separate breaking changes documentation exists with migration guidance. The Graph SDK blog provides detailed API migration reference tables. Confidence is HIGH given the GA documentation quality.

CMS 13 GA delivery validates the public roadmap communicated at Opticon 2025. Opticon 2026 is announced with Diamond (Huge) and Platinum (Valtech, commercetools, Siteimprove, Velir) sponsors. The CMS 13 release notes list planned additions (Opal tools, JS SDK, Content Delivery API support), showing continued forward transparency. Community voting via Optimizely Forum continues. PaaS vs SaaS investment distinction remains clear.

CMS 13 GA ships with comprehensive migration tooling: the Graph C# SDK mirrors Search & Navigation patterns exactly, a complete API migration reference maps every S&N call to its Graph equivalent, and .ToGraphQL() enables debugging. Upgrade guide from CMS 12 to 13 is publicly available. However, the breaking changes remain significant — mandatory S&N removal, .NET 10 upgrade, namespace changes (EPiServer→Optimizely), PageReference→ContentReference, SiteDefinition replaced by Application Model, and on-page editing disabled. Proactive tooling for a known breaking change, but migration scope is substantial.

Optimizely Slack community has 5,000+ members. GitHub maintains 280 repositories across optimizely and episerver organizations. Stack Overflow has 3,000+ tagged questions. Optimizely World forum remains the primary community hub. G2 shows 909+ reviews across all products. The community is enterprise-focused and concentrated — not a mass-market open-source community, which limits raw numbers, but engaged within its niche.

Optimizely World forum has active team member participation alongside community contributors. The OMVP program recognizes active community members. CMS 13 pre-release and GA generated notable community blog activity — Robert Svallin's upgrade guide, Gosso's technical Q&A, David's multi-site migration guide, Epinova upgrade walkthroughs. The Opal Slack app integration (verified Slack Marketplace app) enhances daily engagement. GitHub repos receive responses but volume is moderate compared to open-source communities.

Optimizely has 592 partners (301 technology, 291 channel) with tiered program. Opticon 2026 partner lineup confirms ecosystem strength: Diamond (Huge), Platinum (commercetools, Siteimprove, Valtech, Velir), Gold (Google Cloud, Horizontal Digital, Icreon, Perficient, Verndale). Named enterprise SIs include Rightpoint (1 of 5 Premier Platinum globally). Active partner awards and 2026 UK Partner Day demonstrate ongoing investment.

CMS 13 GA has generated a wave of community content — partner blogs covering migration (matthewdamon.com, msqdx.com, gulla.net, optimizely.blog, davidhome.net, epinova.se, firstlinesoftware.com, avantibit.com), developer upgrade guides on Optimizely World, and Opticon 2025 on-demand sessions. FeaturedCustomers lists 363 case studies. Content is current and technically deep but limited in breadth compared to WordPress or Drupal ecosystems.

Optimizely developer talent concentrates in Nordic/Western European and North American markets within the .NET ecosystem. The 1,638-employee company maintains a certification program. CMS 13's .NET 10 foundation means general .NET developers can ramp up, reducing hiring friction. The 592-partner network provides an implementation talent pool. Platform-specific expertise remains niche compared to broader CMS platforms.

Optimizely welcomed 300+ new logos in 2025 across retail, manufacturing, financial services, and B2B tech. Named customers include Salesforce, Zoom, New Era, and Mazda. Opticon 2025 had record-breaking attendance. CMS won 2025 MarTech Breakthrough Award for Best Content Management Platform. Opal has 900+ active users with 28+ AI agents. CMS 13 GA plus Opal Chat (April 7, 2026) generate forward momentum for the PaaS installed base.

Optimizely remains majority-owned by Insight Partners. Employee count grew to 1,638 as of March 31, 2026 (up from 1,626 in Feb 2026), with no reported layoffs in 2025-2026. Active product investment across CMS 13, Opal AI platform, and SaaS CMS. Private company with no public financials, but sustained R&D investment (major version release, Opal Chat, 28+ AI agents, new analytics platform) and growing customer count signal stability.

Optimizely is a Gartner Magic Quadrant Leader for DXPs for the 6th consecutive year (2025), positioned highest for Ability to Execute and furthest for Completeness of Vision. Leader in Gartner MQ for Content Marketing Platforms for the 9th consecutive year (2026) and Personalization Engines (2026, 2nd year). CMS 13 GA strengthens the .NET enterprise DXP position against declining Sitecore XP. MarTech Breakthrough Award 2025 adds independent validation.

G2 rates Optimizely CMS at 4.0/5 with ~196 CMS-specific reviews; overall Optimizely products rated 4.2/5 across 909+ reviews. Per scoring guide, G2 4.0 with ~200 reviews maps to the 45-60 range. Spring 2026 G2 reports praise user-friendly interface, multi-language/block-based content model, AI integration, and collaboration. Common complaints include steep learning curve, complexity, and developer support friction. CMS 13 mandatory migration adds near-term uncertainty for PaaS customers.

Optimizely pricing remains entirely sales-gated in 2026. The /plans/ page lists 9 products each with a 'Request pricing' button — no dollar amounts, no tier breakdowns. Third-party trackers (Vendr, Kirro, Stellar) still estimate $40K–$500K+/year depending on modules and traffic, but no official pricing is published. CMS 13's bundling of Graph and Opti ID does not improve transparency since those components were never publicly priced. Not higher because complete opacity persists across all products.

CMS 13 bundling Graph and Opti ID into the base license simplifies the modular cost structure slightly — two previously separate line items are now included. However, the fundamental model remains hybrid: annual platform fees plus usage-based components (MTUs for Intelligence Cloud, GMV for Commerce, page views/content items for Content Cloud) plus separate module licensing for Commerce, Campaign, and ODP. Impression-based components still create unpredictable scaling costs. Slightly better than pre-CMS-13 because Graph/Opti ID consolidation reduces the number of separate cost centers.

CMS 13 meaningfully reduces feature gating by bundling Optimizely Graph (search/content delivery) and Opti ID (identity management) into the base CMS license. Previously Graph was a separate add-on and Search & Navigation was the bundled option — now S&N is deprecated and Graph replaces it at no additional cost. However, Commerce Cloud, Campaign, Experimentation, ODP, and DAM remain separately licensed. The consolidation is a genuine improvement but the full DXP still requires multiple add-on purchases.

No changes to contract structure in 2026. Optimizely still requires upfront annual commitments with no monthly options. Auto-renewal complaints persist across review platforms. Multi-year terms (2–3 years) remain standard with multi-year discounts being the primary negotiation lever. No self-service upgrade/downgrade paths. CMS 13 release does not address billing or contract flexibility. Not higher because annual-only billing with aggressive auto-renewal is confirmed.

Optimizely PaaS has no free tier, no community edition, and no open-source path in 2026. CMS 13 does not introduce any self-service developer access. Developer instances remain gated behind Partner Center or support requests. Certification still costs $300/exam. This remains a strictly enterprise-licensed product with no entry path for individuals.

CMS 13 requires .NET 10, which is current and well-supported. Alloy/Foundation template patterns continue for quick local setup. Visual Builder consolidation may streamline first content creation for editors. However, the fundamental gating issue remains: DXP cloud provisioning takes days, and sales engagement is required before any access. For developers already in a licensed org, time-to-first-value is reasonable with CLI templates; for new evaluators it remains procurement-gated.

CMS 13 introduces migration complexity for existing customers: .NET 10 upgrade, Search & Navigation to Graph migration, on-page edit to Visual Builder transition, and site definition to Applications migration. For new implementations, timelines are similar to CMS 12: 6–10 weeks small, 12–20 weeks mid-market, 4–9 months enterprise. Implementation services continue to run $50K–$200K+, with enterprise multi-site projects exceeding $500K. The forced S&N-to-Graph migration adds effort for existing customers specifically.

CMS 13's move to .NET 10 keeps the platform on current mainstream .NET, which helps talent availability. The new C# SDK for Optimizely Graph provides familiar fluent API patterns, reducing the Graph-specific learning curve. However, the CMS 13 talent pool is still developing — existing Optimizely .NET devs require re-skilling on Graph/Visual Builder/.NET 10. Premium over general .NET developers remains 15–25% due to platform-specific knowledge requirements. Glassdoor shows Optimizely engineers at $113K–$157K vs generalist .NET at $87K–$112K.

CMS 13 PaaS hosting model remains fundamentally unchanged — bundled Azure infrastructure with compute, CDN (Cloudflare), SQL, and Blob Storage included in the subscription. Three environments (Integration, Preproduction, Production) included. Graph is now bundled in the license rather than a separate infrastructure cost, which is marginally positive. No separate infrastructure billing. The bundled model provides predictability but costs are embedded in high license fees.

CMS 13 introduces several operational improvements: scheduled job hang detection for proactive monitoring, cloud license management dashboard for server visibility, and redesigned Application management replacing site definitions. These reduce manual administration overhead. Content Manager's search-first interface and auto-translation also reduce editor support burden. The improvement is incremental — Optimizely still manages Azure infrastructure while customers handle CI/CD, Application Insights, and portal admin — but the new tooling meaningfully reduces troubleshooting time.

CMS 13 increases lock-in slightly. Search & Navigation deprecation forces adoption of Optimizely Graph, a proprietary service with deeper platform integration than S&N. Mandatory Opti ID integration adds another proprietary dependency. While Graph provides Content Delivery API for JSON export and Content Management API provides full CRUD, the mandatory coupling to Graph/Opti ID means exit requires replacing both search/delivery and identity layers. Epinova Content Migration Engine remains available. DAM migration path is still 'upcoming, not yet available.'

CMS 13 retains the ~9 core conceptual domains (PageType/BlockType/MediaData, ContentArea/ContentReference, publishing/versioning, Visitor Groups) while adding Visual Builder concepts (Experiences, Content Variations) and replacing OPE as the default editing paradigm. Content type contracts via IContentData interfaces simplify the model layer, but the shift from Site-based to Application-based architecture adds a migration concept. Not higher because the domain count grew; not lower because abstractions are cleaner — a senior .NET developer still needs 4–6 weeks to ramp up.

Optimizely Academy continues the CMS Development Fundamentals and headless masterclass paths, but CMS 13 is newly GA (March 31 2026) and the documentation catalog is still catching up — migration guides, breaking-changes docs, and CMS 13-specific tutorials are being published progressively. The Alloy and Foundation starters still need CMS 13 updates, and PaaS CMS Developer Certification coverage for CMS 13 is pending. Not higher because of the transition-period gap; not lower because docs.developers.optimizely.com already hosts the v13 overview and upgrade guidance.

CMS 13 upgrades to .NET 10 — still mainstream ASP.NET Core with familiar MVC patterns. The Graph C# SDK provides a fluent, strongly-typed query API that feels natural to .NET developers, and the REST API is included by default via AddCms(), making headless consumption more accessible. Visual Builder supports ASP.NET MVC rendering without requiring Graph dependency, keeping the coupled MVC path familiar. Not higher because the .NET requirement still narrows the talent pool versus JS-native headless platforms; not lower because the headless story is incrementally more accessible.

CMS 13 is newly released and starters are in transition — Alloy and Foundation samples will need updates for .NET 10, Application-based architecture, and Visual Builder patterns, and dotnet new templates may lag the CMS 13 release. Optimizely's track record with starters is strong, but during the CMS 12→13 transition the starter ecosystem has a temporary quality dip. Not higher because of that transition gap; not lower because custom elements definable in the Admin UI without code deployment reduces boilerplate demand.

CMS 13 includes Optimizely Graph and Opti ID as mandatory components in licensing, which adds service configuration (Graph endpoint, Opti ID authentication). REST API is included by default via AddCms(), reducing config for headless, and module URLs shifted from EPiServer to the Optimizely namespace, requiring config updates during migration. Not higher because mandatory Graph + Opti ID expand the base config surface; not lower because cleaner defaults and default REST inclusion offset part of the added setup.

CMS 13 improves data modeling with content type contracts via .NET interfaces inheriting IContentData, enabling cleaner composition patterns. Content Variations allow multiple published versions of the same content item in the same language using delta-based storage — a significant modeling advancement — and the code-first model still auto-detects schema changes at startup. Not higher because property removal still orphans data and there's no explicit migration/rollback tooling; not lower because Graph's strongly-typed query results reduce a class of runtime schema bugs.

The biggest CMS 13 improvement for PaaS: Visual Builder is now available on PaaS, replacing On-Page Edit as the default, with a unified interface for pages, blocks, experiences, and media with autosave and synchronized preview. It supports ASP.NET MVC rendering without requiring Graph dependency, making adoption straightforward for existing MVC implementations. Not higher because headless preview for Next.js still requires draft-mode wiring through Graph; not lower because this closes the major gap that previously held PaaS back versus SaaS for visual editing.

CMS 13 maintains similar specialization requirements — .NET expertise remains mandatory, and the mandatory Graph component means developers must understand Optimizely Graph for content querying (previously optional). The shift from OPE to Visual Builder and from site-based to application-based architecture requires retraining for existing Optimizely developers. Not higher because Graph + the new paradigm add proprietary knowledge above the .NET baseline; not lower because .NET 10 is mainstream and cleaner abstractions slightly reduce the curve for new hires.

Team size requirements remain largely unchanged with CMS 13 — production implementation still needs 5–7 people for CMS-only (Technical Lead, 2–3 .NET Developers, Frontend Developer, DevOps, PM). Mandatory Graph reduces the need for separate search infrastructure expertise, and Visual Builder reduces custom preview development effort. Not higher because PaaS still demands DevOps/hosting ownership on top of the dev team; not lower because greenfield CMS 13 team sizing is comparable to CMS 12 with Graph slightly compressing specialist headcount.

CMS 13 meaningfully improves the editorial experience: Visual Builder provides a unified, modern interface for content creation across pages/blocks/experiences/media, Content Manager introduces search-first navigation powered by Graph, and Content Variations let editors manage multi-variant content without developer involvement. Custom elements definable in the Admin UI further reduce code-deployment dependency. Not higher because template creation and new content types still require .NET deploys; not lower because day-to-day content operations are now notably closer to SaaS-class self-service.

CMS 13 is the scoring target; the upgrade FROM CMS 12 (the only path to CMS 13) carries substantial breaking changes now that GA shipped March 31, 2026. Search & Navigation removed (Graph SDK replacement), EPiServer→Optimizely namespace migration across module URLs and DAM packages, Plugin Manager removed, On-Page Edit disabled by default (Visual Builder is replacement), and .NET 8→10 framework target. Not higher because the aggregate breaking-change scope is large even with automatic SiteDefinition→Application migration easing one path; not lower because Graph SDK tooling and documented migration steps reduce friction versus fully manual rewrites.

CMS 13 introduces proactive security controls: file-extension whitelist filtering on all blob upload methods, and permission enforcement during user deletion to prevent custom UIUserProvider bypass. CMS 13 application patches will still ship as NuGet updates requiring customer redeploy (same delivery model as CMS 12), though DXP infrastructure layer is Optimizely-managed. The CMS 13 patch-history track record is thin at 3 weeks post-GA, so the scoring leans on the established monthly NuGet cadence and vendor-managed Azure layer. Not higher because application-tier patches still require customer deploy; not lower because proactive security features are stronger than CMS 12 and infrastructure patches are vendor-managed.

CMS 13 itself is the forced migration: to stay on the supported major version, customers must absorb four concurrent forced changes — Search & Navigation removed, Opti ID mandatory, Plugin Manager removed, and On-Page Edit disabled by default in favor of Visual Builder. Because the scoring context mandates CMS 13 only and all new development targets CMS 13 exclusively per Optimizely's major-version policy, the forced-migration scope is realized rather than hypothetical. Not higher because four distinct forced migrations land simultaneously with GA 3 weeks ago; not lower because automatic SiteDefinition→Application migration and documented Graph SDK tooling reduce the effective window.

CMS 13 mandates Optimizely Graph and Opti ID as non-optional cloud-service dependencies, shifting the dependency posture from self-contained NuGet stack toward mandatory SaaS ties. Removal of Find/Elasticsearch simplifies the search subsystem but replaces it with a SaaS coupling; DAM packages renamespaced from EPiServer to Optimizely add a one-time codebase-wide update. .NET 10 is the required runtime and is a standard, well-supported ecosystem. Not higher because mandatory cloud dependencies and namespace migration add coupling versus pure self-hosted; not lower because the total NuGet surface stays manageable and .NET 10 ecosystem compatibility is strong.

CMS 13 strengthens built-in operational visibility: scheduled-job hang detection flags stalled jobs via log indicators, Cloud License Management adds a Settings view showing active server names per URL with tooltips, and a third-party license page surfaces npm package licenses in edit mode. These sit on top of the existing DXP portal (environment health, deployment logs, Azure Log Analytics), Application Insights integration, Cloudflare analytics, and 24/7 infrastructure monitoring. Not higher because Application Insights configuration and application-layer telemetry still require customer setup; not lower because hang detection addresses a real operational pain point and the cumulative toolset now exceeds most Traditional DXP peers.

CMS 13 replaces SiteDefinition with redesigned Application Management — create/edit/delete applications with validation, editable names and API IDs, default-application designation, and application-specific assets for editors. Expanded host types (Primary, Preview, Media for headless; Default/Primary/Media/Edit/RedirectPermanent/RedirectTemporary for in-process) simplify multi-site configuration. Legacy CMS strengths carry forward: Graph auto-indexing, content version pruning, ContentReference link database, and built-in approval workflow. Not higher because search reindex after schema changes and periodic version pruning on large trees still need attention; not lower because improved application management plus automation keeps day-to-day burden light.

DXP-managed infrastructure handles scaling automatically via Azure App Service autoscale, Cloudflare CDN, and HTTP/3, but CMS 13 does not introduce notable performance-management tooling — the release centers on operational visibility and application management. Application-layer performance remains a customer responsibility: Graph query optimization (replacing Find tuning), output caching configuration, Application Insights query analysis, and ContentArea optimization. Not higher because application-level performance tuning is a recurring responsibility; not lower because managed infrastructure and CDN eliminate most infrastructure-level performance concerns.

G2 rating 4.2/5 for Optimizely CMS with mixed qualitative feedback — some customers describe support as 'fantastic' with fast response, others as 'falls short of expectations.' Tiered support: Standard (4hr P1 SLA, business hours), Premium (1hr P1, 24/7), Premier Success (named CSM). Good support is gated behind Premium/Enterprise tiers. CMS 13 GA has likely increased support volume as customers plan upgrades, but the tier model itself has not changed. Not higher because mixed reviews persist and best-tier support requires Enterprise spend; not lower because Standard SLAs are reasonable and DXP subscription bundles infrastructure-level support.

Optimizely forums remain 'not actively managed or monitored by Optimizely employees,' but the practitioner community is visibly active around CMS 13 — third-party developers publishing CMS 13 compatibility packages (Stott Robots Handler v7, Apr 2, 2026), Commerce 14→15 upgrade guides (Mar 31, 2026), and integration tools (OptiPowerTools.Hangfire). Stack Overflow [episerver] tag holds 3,000+ questions as general reference. The Aug 2025 DevRel maturity survey acknowledged official investment gaps that have not yet materially changed. Not higher because the official forum is unmonitored and vendor DevRel is still maturing; not lower because practitioner blogs are actively producing CMS 13 migration content and the .NET ecosystem supplies strong general resources.

Monthly NuGet release cadence for non-critical fixes continues into CMS 13. The Preview 1 (Jan 2026) → GA (Mar 31, 2026) development arc demonstrates active investment and rapid iteration. Historical binary-breaking changes have been restored in follow-up releases, and 2025 security patch turnaround was reasonable. CMS 13 release notes do not signal a faster bug-fix cadence or changed issue-resolution process. Not higher because monthly cadence means non-critical bugs may wait up to 4 weeks; not lower because CMS 13 development pace and patch velocity demonstrate ongoing investment.

Optimizely CMS 13 ships Visual Builder as the default editing experience with drag-and-drop authoring across pages, blocks, experiences, and media. Blueprints let editors save page compositions as reusable templates for brand consistency. CMS 13 adds custom elements definable directly in the Admin UI without code deployment, allowing administrators to create reusable element types through the interface rather than developer code — this expands self-service page building. Content Manager provides Graph-powered search-first content navigation. Gap: no out-of-box 50+ component library; custom block library still required for full self-service.

Optimizely Campaign (separately licensed) provides campaign workflow: content management, scheduling across email and web channels, UTM tracking, A/B testing on campaign emails, and campaign analytics. The CMP (Content Marketing Platform) adds cross-channel campaign calendaring, editorial planning, and team workflows before pushing content to CMS. CMS scheduled publishing (publish/unpublish at specific date/time) handles web campaign scheduling. Audiences enable UTM-based campaign personalization. No native visual campaign calendar built into PaaS CMS itself. For full-suite deployments (CMS + Campaign + CMP + Experimentation + ODP) the campaign story is compelling; CMS-only deployments have more basic capabilities.

Optimizely CMS provides solid SEO fundamentals via base page type properties (MetaTitle, MetaDescription, CanonicalUrl). Sitemap.xml via EPiServer.SEO.Sitemap NuGet package; redirects via EPiServer.SEO.Redirects. URL management flexible via IPartialRouter. CMS 13 release notes list Opal SEO Metadata Optimization Agent and GEO Schema Optimization Agent as 'Coming next' — not yet shipped in CMS 13 GA. Without Opal agents, SEO tooling relies on manual property management and community packages. Structured data (JSON-LD) requires custom Razor implementation; no unified SEO management UI.

Optimizely Forms (included in CMS) provides drag-and-drop form builder with multi-step forms, conditional logic, file upload, and submission storage. Headless forms capability with React SDK expands rendering flexibility. CTA management via CMS blocks — no dedicated CTA interface. Conversion tracking integrates with Experimentation goals. Lead capture connects to CRM via custom SubmitActors or webhooks; LinkedIn Lead Gen Ads integration routes form data into ODP for nurturing. The combination of Forms + Audiences + Experimentation provides strong performance marketing when the full stack is deployed; CMS-only deployments are more limited.

CMS 13 renames Visitor Groups to Audiences and integrates them directly into the Visual Builder UI — editors show/hide individual blocks based on audience membership without developer work. Contextual Bandits personalization (GA Q4 2024) uses ML to dynamically select the best experience per visitor from real-time signals, adapting automatically without manual rule maintenance. ODP Real-Time Segments extend audience definitions to CDP-level behavioral and transactional data. Experimentation integration enables A/B within personalized campaigns. This is genuine native behavioral targeting, not rule-based-only.

Optimizely is the experimentation market leader. CMS 13 ships Content Variations — multiple independently versioned published variants of the same content item with delta-based storage and independent lifecycles, enabling editorial A/B directly in the CMS without requiring the Experimentation product separately. Tight native integration with Optimizely Web Experimentation and Feature Experimentation adds full statistical significance reporting, auto-winner selection, and multivariate testing. Contextual Bandits takes testing beyond binary A/B to adaptive ML optimization.

CMS 13 ships genuine velocity improvements: Visual Builder with Blueprints enables template cloning for fast page assembly, autosave reduces friction, custom elements can be defined in Admin UI without code deployment. Auto-translation with structure preservation (page hierarchies, content areas, blocks) is shipped and reduces localization cycle time. Content Manager provides search-first navigation for faster content discovery. However, Opal AI agents (28+ purpose-built agents for content tasks) are listed as 'Coming next for CMS 13' and are not yet GA — the previous score's claim of 50%+ campaign time reduction via Opal is not yet realizable. Gap: approval workflow steps still add latency.

CMS 13 serves both traditional rendered web pages and headless delivery via Optimizely Graph API, supporting native mobile app channels and third-party frontends. CMS REST API for content modeling and management is included by default in CMS 13. Email channel covered by Optimizely Campaign (separate product). CMP manages cross-channel editorial planning and can push content to social channels. Four+ channels accessible (web, headless/app, email, social via CMP). However, each additional channel beyond web requires a separate licensed product or custom integration — not a unified single-product multi-channel CMS.

Optimizely CMS does not have a native web analytics dashboard. ODP serves as the unified data hub aggregating behavioral data across web, email, and commerce channels. Standard GA4/Adobe Analytics integration via tag manager. GEO Analytics dashboard was referenced in previous scoring but Opal tools/agents (including GEO Analytics) are listed as 'Coming next for CMS 13' — not yet shipped. Search & Navigation admin analytics are also impacted by S&N deprecation. Primary metrics still live in external analytics tools rather than within the CMS UI.

VB Blueprints are the primary brand guardrail mechanism in CMS 13: developers define the approved style system and component library upfront, and editors compose pages by choosing from those approved layouts and styles. This prevents editors from creating off-brand layouts without design review. Template descriptor system allows brand-specific view rendering for shared block types. Restriction of which block types appear in which content areas enforces component palette compliance. Still convention-based rather than a managed design token system with enforcement at the platform level.

Open Graph and Twitter Card meta tags are manageable via CMS page type properties, giving basic social preview card control. CMP (Content Marketing Platform) provides push-to-social workflows and scheduling for Facebook, Twitter/X, LinkedIn from the editorial calendar — but CMP is a separate licensed product, not built into CMS. No native social scheduling or UGC embed management within CMS itself. Social proof widgets (follower counts, social feeds) require custom block development or third-party embed. Adequate for OG meta management; needs CMP for actual social publishing.

CMS 13 ships native DAM integration via EPiServer.Cms.DamIntegration.UI NuGet package (confirmed in release notes) — editors browse, search, and select DAM assets directly within the CMS authoring interface without context switching. Requires Opti ID and active Optimizely Graph service. The DAM integration adds metadata handling, version control, renditions, and asset usage tracking. Standard CMS media library handles basic image/file management with manual folder organization. CMS 13 adds file upload restrictions by extension whitelist for security. Rights management for marketing volumes still requires a dedicated DAM system connected via the integration.

CMS 13 ships significant translation improvements: auto-translation via machine translation preserving original structure including page hierarchies, content areas, and blocks. Draft translation capability without prior publication enables faster localization workflows. Translatable content export in JSON format for external translation providers. Enhanced translation workflows with multiple initiation points. Global language context switching with dynamic UI adjustment. Multi-Language Management (MLM) provides translation workflow governance with per-locale approval chains. Market-level scheduling via Campaign product handles locale-specific campaigns. Transcreation (adapting beyond translation) still requires custom editorial process or external TMS.

Optimizely ODP serves as the central MarTech hub with 100+ native integrations. Pre-built connectors include: Salesforce CRM (bi-directional), Salesforce Marketing Cloud, Microsoft Dynamics CRM (bi-directional form field mapping), Marketo (bi-directional ODP sync), HubSpot (bi-directional ODP sync), LinkedIn Lead Gen Ads, and Tealium. ODP's unified audience builder routes segments into CMS personalization, Experimentation, Campaign, and external activation channels. Form submit actors enable custom webhook/API delivery to CRM on form submission. Covers CRM, MAP, CDP, and ad platform categories with event-based triggers.

Optimizely Commerce Connect provides full product information management natively integrated with CMS. CatalogContentType is a strongly-typed .NET class defining product/variant/catalog node schemas. Variant/SKU modeling is native with per-variant properties. Customizable catalog views with filters save merchandiser-specific filtered views. Commerce 15 (CMS 13 upgrade path) is in preview. B2B features include customer-org-specific pricing, negotiated price lists, and per-market product availability. EU Omnibus Directive compliance: lowest-price display for the last 30 days.

Optimizely Commerce includes a scalable promotions engine with complex discount rules (percentage, fixed, bundle, threshold). Customizable catalog screen views allow merchandisers to save filtered product views. Dynamic Packages enable bundles where end customers choose variants. However, CMS 13 deprecates Search & Navigation, which means Best Bets (editorial product pinning in search results) is no longer available — a significant merchandising capability loss. Migration to Optimizely Graph for search does not yet have confirmed equivalent editorial merchandising controls. The Opal Product Promotion Agent is listed as 'Coming next' — not yet shipped.

Optimizely Commerce Connect's integration with CMS PaaS remains the deepest content-commerce integration in this scorecard — a native extension of the same CMS framework. CMS PageType and CatalogContentType both derive from IContentData, sharing the content repository, versioning, workflow, media management, and Content Delivery API. Commerce catalog pages embed CMS content blocks via ContentArea. Commerce 15 upgrade path for CMS 13 is in preview. Additionally, the Optimizely-commercetools partnership provides a composable alternative for MACH-aligned deployments.

The shared CMS+Commerce architecture in Commerce Connect enables content-driven commerce natively — editorial teams embed product references, promotions, and commerce CTAs inside editorial content (buying guides, lookbooks, campaign pages) without external API integration. Commerce data (pricing, availability, promotions) is accessible within CMS blocks. CMS 13 Visual Builder allows drag-and-drop placement of product blocks alongside editorial content on the same page. ContentArea in Commerce pages allows CMS editorial blocks directly on product pages. This is a first-class authoring pattern for shoppable editorial.

CMS blocks can be placed on checkout and cart pages in Commerce Connect implementations, allowing CMS-managed trust badges, shipping callouts, and promotional banners within transactional flows without requiring separate commerce template changes. One Page Checkout (consolidated checkout reducing cart abandonment) was on the Commerce Connect roadmap. CMS-managed checkout content is achievable but requires deliberate implementation pattern; it is not a zero-configuration capability.

Order confirmation pages in Commerce Connect can embed CMS content blocks (cross-sell recommendations, loyalty program CTAs, review solicitation). CMS scheduled content can deliver onboarding sequences via email (Optimizely Campaign). Post-purchase email automation (order confirmation, shipping updates, review requests) are available via Optimizely Campaign integration with order events. Commerce data (order status, purchased products) can trigger ODP audiences that feed CMS personalization on return visits. Not a native order-event-triggered CMS content delivery system; requires deliberate integration configuration.

Optimizely Commerce Connect has strong B2B pricing capabilities (customer-org-specific pricing, negotiated price lists, quantity breaks). ODP added a B2B schema in 2025 (previously B2C-only) enabling account-level segmentation, activation, and reporting. Audiences can gate catalog sections and landing pages by authenticated user role or organization membership. Gated product documentation and spec sheets achievable via content-path ACLs. Quote-request workflows require custom development (the dedicated B2B product, Optimizely Configured Commerce, has native quote management — but is a separate product line).

CMS 13 deprecates Optimizely Search & Navigation (Find), which was the primary commerce search integration via EPiServer.Find.Commerce. Best Bets (editorial product pinning), faceted content-product blending, and synonyms management are all lost with this deprecation. The migration path is Optimizely Graph, which provides GraphQL-based search with filtering and faceting capabilities, but does not yet have confirmed equivalent editorial merchandising controls (Best Bets, query rules). Commerce Search v3 (Vertex AI) applies to Configured Commerce, not Commerce Connect. Content search landing pages remain manageable from CMS. This is a significant regression in commerce search capabilities during the transition period.

The core promotion engine supports time-based activation, channel-specific targeting, and complex discount rule combinations. Dynamic Packages allow end-customer-configurable bundles. Scheduled publishing controls time-based banner and landing page activation. EU Omnibus Directive lowest-price display (last 30 days) is native. Promotional content can be audience-targeted. However, the Opal Product Promotion Agent (natural language promotion configuration) is listed as 'Coming next for CMS 13' — not yet shipped. Countdown timers require custom block development.

Commerce Connect supports unlimited storefronts on a shared codebase — sites share the product catalog, promotions engine, and order management while having storefront-specific editorial content, templates, and access control. CMS 13 Applications model replaces Site Definitions with a streamlined interface — each Application has a unique URL, start page, internal identity, and application-specific asset folders. Per-market pricing, availability, and language-specific product descriptions are native. ODP supports multi-site, multi-region customer data management.

CMS 13 DAM integration provides rich product media management: asset tagging, version control, renditions, and usage tracking allow merchandisers to maintain organized product image libraries. Image transforms (resize, format conversion) via EPiServer.ImageLibrary handle standard product photography requirements. Video embeds on product detail pages are achievable via CMS media or third-party video provider blocks. However, 360-degree product views, AR/3D model references, image hotspots, and zoom require third-party integrations — none are native Commerce Connect capabilities.

Optimizely Commerce Connect has no native marketplace or multi-vendor content capabilities. Multi-author content is achievable via CMS roles (multiple editors can manage different product categories) but there is no seller profile, seller-specific product description workflow, review aggregation, or content quality moderation tooling. Custom development could build seller portals using the CMS forms and content model, but these would be bespoke implementations with no platform support.

CMS 13 ships auto-translation with structure preservation covering page hierarchies, content areas, and blocks — this applies to product content pages and category descriptions. Draft translation without prior publication speeds up product content localization. JSON export for external translation providers improves enterprise TMS integration. Multi-Language Management (MLM) governs translation workflows for product catalog content alongside CMS editorial content. Per-market product descriptions, currency-aware pricing display, and market-specific promotional calendars are all native in Commerce Connect. EU Omnibus lowest-price display for regulatory compliance.

ODP aggregates content engagement and commerce transaction data, enabling content-to-revenue attribution through custom ODP dashboard configuration. Experimentation links content variants to commerce conversion goals (add-to-cart, purchase) with statistical significance reporting. Standard e-commerce analytics integration (GA4 Enhanced Ecommerce, Adobe Analytics) captures conversion funnel data. This is achievable but requires deliberate ODP configuration and custom reporting — not an out-of-box CMS attribution dashboard.

Opti ID provides centralized identity management with SAML and OIDC for SSO, and SCIM provisioning with Entra ID, Okta, and PingOne for automated user lifecycle management (up to 5 SSO connections per organization). Custom roles created in Opti ID sync to CMS as user groups. CMS provides content-path-level access control with read, write, create, and publish permissions assigned to roles. Audiences target content by authenticated user properties (role, department claims from OIDC). CMS 13 adds permission checking on user deletion enforcing custom UIUserProvider restrictions. Permission granularity is at the subtree level rather than per-item.

Optimizely CMS supports knowledge management through flexible content types (Article, FAQ, HowTo PageTypes), hierarchical content organization via content tree, and content lifecycle management (draft, review, publish, archive, expire). Content Manager (CMS 13) provides search-first navigation via Optimizely Graph. However, Search & Navigation deprecation means the previous Find-based full-text search with faceting must be migrated to Graph or third-party — Graph provides search but the transition may impact intranet search quality during migration. Main gaps vs dedicated KM platforms: no native comment threading, no expert suggestion system, no knowledge graph.

Optimizely PaaS can host employee portal content using the standard CMS rendering model — intranet pages, news feeds, policy documents are all buildable with audience-targeted delivery. Audiences via OIDC claims enable department/role-targeted intranet content. Visual Builder improves authoring ergonomics for HR and communications teams. Weaknesses remain: no native social/collaboration features (comments, reactions, @mentions), no org chart, no employee directory schema, no notification/alert system, no native employee mobile app. These require custom development or integration with SharePoint/Viva Connections.

Audience targeting via OIDC claims enables department/role/location-specific announcement delivery — editors can target news and announcements to specific employee segments. Scheduled publishing manages communications calendars. CMP-Teams integration sends real-time alerts for CMP content activity into Microsoft Teams channels. However, read receipts, acknowledgment tracking, mandatory-read workflows, and formal internal comms reporting are not native CMS capabilities — they require custom development or dedicated intranet products.

Optimizely CMS has no native people directory, employee profile schema, org chart visualization, or HR system integration features. Employee profile pages can be built as custom content types, and OIDC user properties can be displayed from Azure AD, but this is a full custom development effort with no platform support. The SharePoint Connect (which enabled SharePoint People directory integration) was available for CMS 11 but is not available for CMS 12/13. Organizations requiring a people directory must build custom or use SharePoint/Microsoft Viva alongside.

CMS content versioning applies to policy documents — each published version is preserved with author and timestamp metadata. Content approval workflows can enforce review steps before policy publication. ExpiredDate enables automatic archival of outdated policies. Mandatory acknowledgment tracking is not native — requires custom implementation. CMS 13 adds file upload restrictions by extension whitelist for security, improving document management governance. CMS can serve as a document repository, but dedicated policy management is beyond its scope without significant custom work.

Audience-based content targeting can deliver role-specific onboarding content (new hire sees department-specific content based on OIDC role claim). Custom content types can structure 30/60/90-day content paths hierarchically. However, structured onboarding journeys with progressive disclosure, completion tracking, task checklists, and HR-triggered new-hire portals are not native CMS capabilities. Campaign (email) can send time-based onboarding sequences triggered by new hire date. These features require considerable custom development.

CMS 13 deprecates Search & Navigation (Find), requiring migration to Optimizely Graph or third-party search providers. Find's full-text search with faceted filtering, relevance tuning admin, and synonyms management are all discontinued. Optimizely Graph provides GraphQL-based content search with filtering capabilities but lacks the editorial search admin (Best Bets, synonyms, relevance tuning) that Find provided. Federated search across external systems (SharePoint, Confluence) was already unavailable — now the primary internal search also transitions. Content Manager uses Graph for search-first navigation, which is functional but different from Find's enterprise search features.

Optimizely CMS delivers responsive web content via ASP.NET MVC rendering — mobile browsers receive responsive intranet pages without a dedicated native app. Content Delivery API and Graph API enable custom native mobile apps consuming CMS content. However, there is no Optimizely-provided native mobile app for intranet employees, no offline content sync, no push notification system, and no kiosk/shared-device mode. Deskless and frontline workers are not a primary design consideration.

Optimizely CMS has no native LMS integration, course management, completion tracking, or certification features. Training materials (videos, PDFs, documents) can be hosted as CMS content, and OIDC-based access control can gate training content by role. Completion tracking requires integration with an external LMS via custom API connector. There are no pre-built connectors to common LMS platforms.

Optimizely CMS has no native social layer for employee engagement — no comments, reactions, discussion forums, peer recognition, polls/surveys, idea submission, or community spaces. The platform is document-first; social features are entirely absent from the product. Organizations requiring social intranet features must integrate dedicated employee experience platforms (Staffbase, Simpplr, Workvivo) or build custom social modules.

CMP + Microsoft Teams integration provides real-time alert notifications for CMP content activity (mentions, asset shares, task assignments) delivered into Teams channels, with click-through links to CMP tasks. The platform runs on Azure infrastructure, which simplifies SSO/identity alignment with Microsoft 365. However, deep Microsoft 365 integration (SharePoint document sync, Teams wiki embedding, embedded CMS content cards in Teams) is limited. The SharePoint connector was discontinued after CMS 11. No Google Workspace or Slack native integration.

CMS content expiry (ExpiredDate) enables automatic archival of outdated content. Content approval workflows enforce review steps before publication. Content versioning records all changes with author, date, and version history. CMS 13 adds Content Variations with independent lifecycles — multiple published versions of the same content can have separate expiry and management independent of each other, improving lifecycle granularity. Scheduled publish dates now visible in Version gadget (CMS 13). However, automated review-date prompts, stale content flagging, and formal archival workflows with notifications are not native CMS features.

ODP aggregates employee digital interaction data across the intranet, enabling custom audience segments and activity reports. Search & Navigation analytics (search term frequency, zero-result searches) are discontinued with the S&N deprecation in CMS 13. GEO Analytics and Opal-related analytics features are listed as 'Coming next' — not yet shipped. Department-level analytics dashboards, adoption rate tracking, and formal intranet ROI reporting require custom ODP dashboard configuration or external BI integration.

CMS 13 replaces Site Definitions with Applications — each Application has a unique URL, start page, internal/normalized identity, and application-specific asset folders with expanded host types (Primary, Preview, Media, Edit, redirect). Multiple Applications share the same SQL database (logical separation) with independent content trees, site-specific templates, and separate access control. Automatic migration from SiteDefinition to Application settings eases the transition. For strict regulatory data isolation, separate DXP environments per client are required. Isolation is logical not physical — adequate for multi-brand but not true multi-tenant with hard data boundaries.

Optimizely CMS provides strong shared content for multi-brand implementations. SharedBlock items in the Global Assets folder are referenceable across any Application without duplication. VB Blueprints define the approved layout and component library centrally. CMS 13 adds custom elements definable directly in the Admin UI without code deployment — administrators can create reusable element types centrally and make them available across all brand Applications. Site-specific block rendering via multiple Razor view templates selected by ITemplateSelector. Global content shared via ContentReference to Global tree items.

Optimizely CMS provides multi-level governance for multi-brand deployments. Central administrators access all Applications and global settings. Brand editors restricted to their Application's content tree via ACLs. Approval workflows configurable per Application with site-specific reviewer pools. Content approval requirements enforced per content type and path. CMP Workflow Actions provide step-level permission control for fixed workflows including external agency contributor access. Handles central oversight with brand autonomy, though less granular than Sitecore XP's per-item permissions.

Adding Applications to an Optimizely PaaS DXP has moderate marginal cost — new Applications require site definition, content tree, access control, and templates, primarily developer time with no incremental subscription cost (unlimited sites per DXP subscription). Traffic scaling handled by DXP Azure autoscaling within the capacity tier; growth may require tier upgrade. Implementation cost per additional brand decreases as shared components, VB Blueprints, and governance patterns mature. The shared-codebase model provides genuine economies of scale vs. N separate installations.

Per-brand visual identity is achieved through site-specific CSS, Razor view templates, and VB Blueprint style configurations — each brand Application can have its own stylesheet, typography, color tokens (as CSS variables), and logo rendering. ITemplateSelector enables brand-specific component rendering from shared block types. VB Blueprints lock the layout and style selection to brand-specific approved options. This is convention-based CSS theming, not a managed design token system with enforcement, versioning, or propagation — but it is effective for multi-brand deployments.

CMS 13 ships enhanced translation capabilities that improve multi-brand localization governance: auto-translation preserving page structure, draft translation without prior publication, JSON export for external providers, global language context switching, and redesigned Language Selector. MLM enables per-brand translation workflows with per-locale approval chains — Brand A's French team is isolated from Brand B's French approval process. Role-based access scoped to Application + language branch combinations allows language-level editorial autonomy within brand boundaries. No fully automated per-brand-locale compliance guardrails.

No native cross-brand analytics dashboard in Optimizely CMS. Analytics are per-Application by default. ODP can aggregate data across Applications into unified segments and reports, but this requires deliberate custom configuration. Content Intelligence provides per-site analytics but not portfolio-level aggregation. Executives requiring portfolio-level comparison across brands must build custom ODP dashboards or integrate external BI tools.

CMS approval definitions can be configured independently per content type and content tree path — each brand Application can have its own approval chain, review stages, and reviewer pools. Different brands can have separate approval chains, editorial teams, and publishing permissions within the same CMS instance. CMP supports brand-specific workflow configurations with step-level access control. Central administrators can audit publishing history and approval logs across all brands.

Content can be shared across brand Applications by referencing shared blocks and media from the Global Assets folder — a legal disclaimer or global nav element is authored once and referenced across all brands without duplication. However, there is no native 'push content from Brand A to Brand B' syndication workflow — when corporate publishes a press release, there is no mechanism to automatically distribute it to child brand sites with local adaptation points. This requires custom development (e.g., a scheduled job or content event handler). Graph API could power a custom syndication solution.

Per-brand/region compliance settings are achievable through role-based publishing permissions (only approved publishers can publish to a locale), content approval workflows (compliance reviewer step per region), and locale-specific content variants (per-region legal content, cookie consent, GDPR disclaimers). However, there are no native automated publishing guardrails that prevent non-compliant content from reaching a specific region — compliance enforcement relies on workflow configuration and human review.

VB Blueprints provide the closest native approximation of design system management — developers define the approved component library and style options centrally. CMS 13 adds custom elements definable in Admin UI without code deployment, which allows central teams to extend the element library without developer intervention — a small improvement in design system agility. Shared Razor component libraries maintained centrally and consumed per-brand via ITemplateSelector. CSS variables serve as brand-level design tokens. However, there is no centralized design token management UI, no versioning/changelog for the design system, and no update propagation mechanism.

Opti ID provides centralized identity management across all brands/Applications — a central admin can manage all users, roles, and SSO configurations across the entire portfolio from a single interface. SCIM provisioning with Entra ID, Okta, and PingOne automates user lifecycle management including brand team onboarding. Brand-scoped editor roles via ACLs give brand teams autonomous self-management. Cross-brand contributor roles configurable. SSO via SAML/OIDC provides unified authentication across brands.

Shared CMS content types (PageTypes, BlockTypes) are defined once in the .NET codebase and shared across all brand Applications. Brand-specific view rendering is applied via ITemplateSelector. CMS 13 adds custom elements definable in Admin UI without code deployment — administrators can extend the element type library without developer code changes, which slightly improves the ability to adapt content models per-brand use case. Brand-specific property extensions still require class inheritance. There is no visual model inheritance or per-brand content type extension via the CMS admin UI beyond custom elements.

Optimizely has no native executive portfolio reporting across brand Applications. Reporting is per-Application, not cross-Application. ODP can aggregate data across all brand sites into custom dashboards, but this requires deliberate data pipeline configuration and dashboard development. Content freshness by brand, publishing SLA adherence, cost allocation per Application, and capacity planning reports all require custom implementation. Executives managing a brand portfolio have no native single-pane view.

Optimizely publishes a DPA (v2026-01) available to all customers with SCCs and UK/Swiss addendums, EU-US Data Privacy Framework certification, EU data hosting with geofencing and customer-controlled break-the-glass, and a published sub-processor list. BCRs are in development with the Swedish DPA. PaaS customers still implement DSR workflows in application code, which caps the score below the top anchor.

Optimizely's HIPAA-ready program (announced Nov 2024, effective Jan 1 2025) explicitly covers CMS PaaS & SaaS and Web/Feature Experimentation as ePHI-enabled Software Services, with an Optimizely-approved BAA required for new subscriptions and healthcare/life sciences documented as a vertical. PaaS customers retain implementation responsibility for HIPAA-compliant application code, keeping the score below fully managed healthcare-specialized platforms.

Coverage spans GDPR, CCPA, UK GDPR (DPA addendum), EU-US DPF, TISAX (automotive — Campaign scope), HECVAT/HECVAT-Lite (US higher education), FSQS/Hellios Stage 3 (financial services), and TTDSG/TKG (German telecom) — broader than most DXPs. No FedRAMP, IRAP, or C5 authorization keeps this below enterprise federal-grade platforms.

SOC 2 Type 2 attestation covers a broad product scope — CMS (PaaS & SaaS), Commerce Connect, Web & Feature Experimentation, Configured Commerce, ODP, CMP, and Analytics — with annual third-party audit cadence and reports available under NDA via CSM. Wide product coverage is stronger than most competitors; self-hosted deployments remain out of scope.

Optimizely holds ISO 27001:2022 (updated to latest standard), ISO 27017:2015 (cloud security controls), and ISO 27018:2019 (cloud PII protection) — a triple-ISO stack for platform-scope operations rather than just underlying infrastructure. ISO 27001 covers CMS, Commerce Connect, Experimentation, and Campaign; ISO 27017/27018 cover CMS, Commerce Connect, and Experimentation. Active maintenance to the 2022 standard demonstrates sustained program investment.

Portfolio is above average for a commercial DXP: PCI DSS v4.0.1 (QSA-audited for Experimentation; SAQ for Commerce Connect + Configured Commerce), TISAX, CSA STAR Level 1 with CAIQ 4.0, CyberGRX Tier 2 validated assessment, HECVAT, and FSQS/Hellios Stage 3. Absence of FedRAMP and CSA STAR Level 2 third-party audit keeps this below top-tier federal-authorized platforms.

EU and US data hosting with contractual guarantees, EU geofencing restricting support access to EU-based staff with customer-controlled break-the-glass procedures, and EU-US DPF certification. Self-hosted PaaS customers have full Azure region control; BCRs are in progress with the Swedish DPA. Residency remains an EU/US binary with no documented APAC region option, and adjacent products (ODP, Campaign) may have different residency profiles requiring procurement review.

DPA v2026-01 documents retention and post-termination deletion; content export via .NET APIs and Optimizely export tooling; DXP Cloud provides infrastructure-level deletion at termination. Right-to-erasure within the CMS layer requires custom .NET implementation (standard PaaS pattern) and there is no self-service DSR portal — fulfillment is API- and support-driven.

CMS 13 adds scheduled job hang detection logging and improved admin monitoring, while Opti ID (required in CMS 13) brings SSO/MFA/SCIM with stronger authentication audit trails. Activity logging tracks content edits, publish events, and admin actions with configurable archive retention (default 12 months). DXP Cloud exposes Azure Monitor + Log Analytics for SIEM integration; CyberGRX Tier 2 and CREST-accredited pen testing provide third-party security reporting.

CMS 13 makes Visual Builder the default editing experience across pages, blocks, experiences, and media, and the AI-Assistant emits WCAG-compatible HTML in the RTE; Optimizely states a WCAG 2.1 A and AA target driven in part by the Accessibility Strengthening Act. No formal WCAG 2.1 AA conformance report for the new Visual Builder was found publicly, which prevents a 70+ score.

Support articles cover accessibility basics, accessible HTML, and formatting guidance, but focus on delivered site output rather than authoring UI conformance. No public VPAT/ACR for the CMS authoring interface was found despite CMS 13 launch, and no Section 508 formal conformance statement or ATAG 2.0 documented assessment is available — below enterprise leaders like Adobe and Salesforce who publish current VPATs.

Opal Chat is GA on CMS 12 PaaS via NuGet (optimizely.cms.opalchat), supporting text generation, rewriting, brainstorming, translation, and URL analysis. CMS 13 PaaS release notes list 'Opal tools and agents' as 'Coming next' — not yet available on CMS 13. The Epicweb AI-Assistant plugin adds a BYOAI path (Azure OpenAI, OpenAI, Gemini, Llama, Claude). Advanced Opal features — Instructions-based brand voice guardrails and the full 28+ agent suite — remain SaaS-first. Not higher because CMS 13 users currently lack Opal Chat and brand governance depth is limited on PaaS.

Opal Chat on CMS 12 PaaS includes image generation with customizable aspect ratios (1:1, 4:3, 16:9, 9:16), image editing by URL with style modifications, and up to four image variations per request. Smart Image Analyzer plugin provides auto alt-text. DAM auto-tagging is native. CMS 13 does not yet have Opal Chat, so image generation is unavailable on the newest PaaS version. Not higher because no dedicated native image generation pipeline exists independent of Opal Chat, and CMS 13 lacks these features entirely.

CMS 13 PaaS ships enhanced auto-translation that preserves original structure including page hierarchies, content areas, and blocks — a meaningful improvement over CMS 12's Google Translate AI integration. Draft content can now be translated directly. The Languages add-on integrates Microsoft Translator (Azure Cognitive Services). Opal Chat (CMS 12) surfaces translation capabilities. Third-party TMS connectors (Phrase, Smartling) extend to 30+ MT engines. Not higher because brand voice preservation across locales is not documented as a built-in control.

GEO Analytics dashboard is available for CMS 12+ PaaS (covering CMS 13), tracking Crawl-to-Refer Ratio for top 6 AI platforms, AI-Agent Analysis (top 12 agents by request volume), and top pages by AI traffic. The SEO Metadata Optimization Agent audits pages and recommends metadata updates; GA status on PaaS unconfirmed. llms.txt support exists via Stott Robots Handler v7 for CMS 13 (managing llms.txt by Application and Host URL). Not higher because GEO-specific metadata generation features are SaaS-first and the SEO agent is not confirmed GA on PaaS.

Opal agent workflows (GA September 2025) are available to PaaS customers with Opal licensing on CMS 12, enabling AI-triggered content scheduling, bulk enrichment, and editorial automation. ML-based auto-tagging on DAM ingestion is native. CMS 13 introduces Content Variations with delta-based storage and Content Manager with Graph-powered search-first content discovery, but Opal tools/agents are listed as 'Coming next' for CMS 13. Not higher because workflow agents remain in private GA and the full agent suite is not yet available on CMS 13.

Optimizely Opal launched as a production-grade agent orchestration platform (GA September 2025) with 28+ purpose-built agents, drag-and-drop workflow canvas with triggers, logic (loops/conditionals), and specialized agents. PaaS customers can access Opal agents via Opal licensing + NuGet on CMS 12. However, workflow agents remain in private GA — 'not available in all Opal instances' per support docs. CMS 13 lists Opal tools/agents as 'Coming next', meaning no agentic capability on the newest PaaS version yet. Human-in-the-loop approval gates exist but fully autonomous workflows are not confirmed GA.

Optimizely Content Intelligence is a named add-on product (NLP topic analysis, content gap identification, performance scoring) available to PaaS customers via Optimizely One licensing, independent of SaaS/PaaS split. ODP integration provides behavioral signals and content-affinity predictions. Content Recommendations surfaces next-best-content per visitor. CMS 13's Content Manager provides Graph-powered content discovery with filtering, but this is navigation rather than intelligence. Not higher because Content Intelligence is separately licensed and a dedicated content health or ROI attribution dashboard specific to PaaS is not confirmed.

The Content Refresh Agent audits pages against brand guidelines, last-modified date, and keywords at scale — available to PaaS via Opal licensing on CMS 12. Siteimprove's AI agent-to-agent integration with Opal (September 2025) handles accessibility detection and remediation. Opal Instructions enforce brand voice guardrails. CMP compliance workflows log approvals for regulated industries. Not higher because Siteimprove integration is primarily demonstrated for SaaS, workflow agents remain in private GA, Opal tools are not yet on CMS 13, and thin/duplicate content detection at scale is not documented as a PaaS-native feature.

Optimizely Graph is now the default search engine in CMS 13 (Search & Navigation deprecated), with a new Graph C# SDK providing fluent API, field-level search with boosting, and facets. Semantic search (_ranking: SEMANTIC, hybrid keyword+vector, 23 languages) remains available via Graph API but still flagged as 'experimental' in developer documentation. CMS 13's Content Manager uses Graph-powered search natively. Azure AI Search integration documented by Perficient as a production-ready path. Not higher because semantic search experimental status is unchanged and Graph is a separate add-on for licensing purposes.

Optimizely was named a Leader in the 2025 Gartner Magic Quadrant for Personalization Engines (February 2025), covering the full platform including PaaS deployments. ODP with contextual multi-armed bandits (GA), real-time AI segments, and Content Recommendations is available to PaaS customers. CMS 13 introduces Content Variations with delta-based storage and independent lifecycle per variation, strengthening the experimentation foundation for personalization. The ML personalization engine is identical for PaaS and SaaS, though it requires separate ODP + experimentation licensing.

CMS 13 PaaS release notes list 'Web MCP — access to Optimizely tools and instructions from anywhere' as a 'Coming next' feature, signaling official MCP investment. The first3things/optimizely-cms-mcp community server (v2.0.0-beta, 14 tools with discovery-first architecture) continues to mature. JaxonDigital's optimizely-dxp-mcp targets PaaS infrastructure. No official Optimizely-published MCP server is in GA — the official Experimentation MCP server was in closed beta as of August 2025. Not higher because Web MCP is announced but not shipped, and community servers remain pre-release.

The Epicweb BYOAI plugin is documented specifically for CMS 12 PaaS and SaaS, supporting Azure OpenAI, OpenAI, Google Gemini, Meta Llama, and Anthropic Claude via custom model endpoints. This is the practical BYOM path for PaaS. Native Opal is locked to Google Gemini following the December 2025 partnership — no platform-native BYOK toggle in core Opal. CMS 13 does not introduce any new BYOK capabilities. The Optimizely CMP BYOAI feature is invite-only and applies to CMP, not CMS PaaS.

CMS 13 significantly improves developer AI extensibility: full REST API included by default (via AddCms()), Graph C# SDK with fluent API for strongly-typed content queries, and OAuth client configuration via appsettings. These lower the barrier for AI agent integration. Opal Agent SDK enables custom agent development. Optimizely Graph (GraphQL) is RAG-ready. The open-source Optimizely Agent microservice (Go) wraps SDKs behind REST. Web MCP is announced as 'Coming next'. Not higher because no official LangChain/LlamaIndex guides exist and Opal tools haven't shipped on CMS 13 yet.

Opal Instructions enforce brand voice and compliance rules per-agent. Human-in-the-loop approval workflows are built into key agents (SEO Metadata Implementation Agent requires explicit approval). CMP compliance workflows log final approvals for regulated industries. Optimizely holds ISO 27001:2022, ISO 27017, ISO 27018, SOC 2 Type 2, and PCI DSS v4.0.1 certifications. Opti ID Admin Center allows administrators to disable generative AI features organization-wide. Not higher because hallucination/confidence scoring is not a visible feature, IP indemnification is not publicly documented, and Opal governance features are not yet on CMS 13.

The Opal Usage Dashboard provides credits allocated/remaining/consumed, 30-day daily usage and balance history charts, per-user consumption (Opal User Usage), per-product consumption (Opal Product Usage), and per-agent credit consumption via Opal Agent Usage reporting. Monthly billing notifications and overage alerts are automatic. GEO Analytics (CMS 12+) tracks AI platform crawl traffic and agent request volumes. Not higher because per-team cost attribution, model performance dashboards, and prompt effectiveness analytics are not documented.