Optional vs Required

In the context of Optimizely CMS 13, the role of Optimizely Graph is categorized as both mandatory and foundational. For technical stakeholders, distinguishing between Graph as a licensing requirement and its functional use for specific features—particularly search—is critical for architectural planning.

1. The Foundation

From a platform perspective, Optimizely Graph is a mandatory component of the CMS 13 ecosystem. It is included in the base license and serves as the underlying infrastructure for next-generation authoring and delivery tools.

While a CMS 13 solution can technically be compiled and executed without activating Graph (for example, during the initial phases of a migration from CMS 12), this approach severely limits platform capabilities. Operating CMS 13 without Graph effectively reduces the system to a subset of CMS 12 features, as core innovations in the new version are built directly upon the Graph indexing engine.

2. Functional Requirements: When Graph is Non-Negotiable

Several primary features in CMS 13 exhibit a hard dependency on Optimizely Graph. Attempting to implement these without active Graph synchronization will result in functional failure:

• Content Manager: The revamped editorial interface utilizes Graph for superior indexing and discovery. Without Graph, enhanced grid views, filtering, and search within the management UI are unavailable.
• External Content Integration: A primary value proposition of CMS 13 is the ability to treat external data (from PIMs, DAMs, or other legacy systems) as "Shadow Content." This integration relies entirely on the Graph’s ability to ingest and normalize multi-source data.
• Optimizely Opal (AI Orchestration): The RAG (Retrieval-Augmented Generation) capabilities that allow Opal to interpret a brand's specific content context depend on Graph as the data source for AI agents.
• Preview for Decoupled Architectures: Managed preview routing and the token bypass mechanism for headless frontends are architected specifically for Graph-backed delivery.

3. Search Implementation Paradox

Confusion often arises regarding the "optional" nature of search implementation.

Deprecation of Search & Navigation

It is important to note that Optimizely Search & Navigation is deprecated in CMS 13 and future releases. It is no longer a supported option for indexing and searching CMS 13 content. Consequently, all CMS 13 projects must implement a new search strategy.

Search Decision Matrix

While Graph remains mandatory for internal platform health, developers possess a choice regarding the frontend search provider:

1. Optimizely Graph as Search Provider (Recommended): Developers utilize the services.AddContentGraph() extension to leverage Graph for full-text search, fuzzy matching, facets, and semantic relevance. This is the most efficient path, as content is indexed automatically.
2. Third-Party Search Provider (Optional): Because CMS 13 is built with a composable mindset, developers may choose to utilize a third-party search provider (e.g., Algolia, Coveo, or Elasticsearch). In this scenario, while Graph remain active for internal CMS functions (like Content Manager), the frontend search results are powered by the external provider.

4. Technical Scenarios for "Optional" Usage

There are limited technical scenarios where Graph might be treated as optional for a transient period:

• Legacy Codebase Maintenance: During an upgrade from CMS 12 where the project is compiled for .NET 10 but has not yet transitioned to modern delivery patterns.
• Local Development: While local development does not strictly require a cloud-connected Graph instance for basic UI testing, the synchronization agents must be accounted for to prevent background service exceptions.
• On-Prem / Data Residency Constraints: In cases where strict on-premises requirements prevent the use of managed cloud services, Graph indexing might be bypassed, which explicitly forfeits the use of Content Manager and newer editorial features.

Conclusion

Optimizely Graph functions as the foundational state of CMS 13 rather than a peripheral service. While the choice to utilize Graph for frontend search delivery remains technically optional due to the platform’s composable architecture, using Graph as the primary content engine is a requirement to utilize the product's full potential. Architectural decisions should prioritize Graph-native implementations to ensure future-proofing and compatibility with the broader Optimizely One ecosystem.