Optimizely Cloud Technology Stack
CMS:
Optimizely Content Cloud
Overview
Section titled “Overview”Optimizely Content Cloud (CMS) plus Experimentation, in a headless-only configuration — Optimizely Graph as the delivery layer in front of a decoupled frontend. Other Optimizely products (Commerce, CMP) and non-headless, server-rendered delivery are out of scope.
Stack by layer
Section titled “Stack by layer”| Layer | Technology / Tool | Notes |
|---|---|---|
| Backend/Platform | Optimizely Content Cloud SDKs | Content Types defined in C# |
| Backend/Platform | Optimizely Graph (GraphQL) | Headless content delivery layer |
| Frontend | React / Next.js (or equivalent) | Consumes Optimizely Graph; headless delivery only, no server-rendered templating engine in scope |
| Experimentation | Optimizely Web/Feature Experimentation SDKs | A/B testing & personalization |
| Experimentation | Optimizely Feature Flags | Feature flagging |
| Testing & QA | xUnit / NUnit | Backend unit testing |
| Testing & QA | Playwright | Frontend/E2E testing |
| CI/CD & tooling | Azure DevOps | Common pairing with Optimizely DXP |
| CI/CD & tooling | Optimizely DXP deployment CLI/API | Platform-specific deployment tooling |
| Infrastructure & hosting | Optimizely DXP | Managed PaaS, runs on Azure |
Scope is headless implementations only for now — if a project needs a
non-headless, server-rendered delivery model, that stack isn’t
documented here yet. See also shared-stack.md for
cross-cutting tools (version control, generic CI/CD, testing, design
handoff) that apply here too.