Hello Sitecorian Community,
If you’ve been working on Sitecore projects over the last few years, you’ve probably hit this situation at some point:
“We have XM Cloud for content, CDP for customer data, Personalize for targeting, and Content Hub for assets — but our team spends half the day switching between four different portals.”
And honestly, that was the reality. Different logins. Different APIs. Different billing conversations. Developers writing glue code between products that were supposed to talk to each other.
At Sitecore Symposium 2025 (November 3–5, Walt Disney World Dolphin Resort, Orlando), Sitecore announced SitecoreAI — and on November 10, 2025, every XM Cloud tenant was automatically upgraded. No migration. No new contract required.
What Is SitecoreAI, Really?
The simplest description:
SitecoreAI = XM Cloud + CDP + Personalize + Search + DAM — unified into one platform, one login, one data model, with AI built into every layer.
Sitecore calls this going from “composable” to “composed.” Sitecore COO Dave Tilbury on stage at Symposium: “no addons, no upsells, no tokens, no games.” Buy one module, get production-scale access to the entire suite. (Source: Velir Symposium 2025 recap, sitecore.com/platform/ai-and-agents)
❌ Before (XM Cloud era)
- 4 separate portals, 4 logins
- Token-based AI billing surprises
- Separate contracts per product
- Sitecore Stream = separate add-on
- “You can’t customise SaaS”
✅ After (SitecoreAI)
- One unified workspace, one login
- No tokens, no upsells — one metric
- Buy one, access the full suite
- Brand-aware AI copilot baked in
- Sitecore Studio — governed extensibility
What Stays the Same for Developers
Most important for teams mid-project: your toolchain is unchanged.
- Your Sitecore CLI and serialization workflows carry over
- The Deploy App pipeline works exactly the same
- All existing SDK integrations continue without breaking changes
⚠️ Content SDK update (September 2026): JSS 22.x reached end of life in June 2026. JSS 23.x does not support SitecoreAI. The Content SDK 2.x is now the only supported path for SitecoreAI development. Content SDK 2.0 requires Next.js 16 minimum and delivers up to 49% lighter client bundles and 89% smaller application footprint versus JSS starter kits. If you are still on JSS for SitecoreAI, migrate now. Source: developers.sitecore.com/learn/getting-started/sitecoreai/content-sdk
✅ Content Hub update (September 2026): The native SitecoreAI DAM launched February 2026 and full-page editing in Content Hub went GA June 2026. The “phased integration” framing is now outdated — both products share the same unified platform environment. Check the Sitecore Developer Portal changelog for updated integration patterns.
Platform Architecture — SitecoreAI at a Glance
Sitecore Studio — The Four Parts
- Agentic Studio — build and run AI agents and multi-step flows. 20+ pre-built agents included out of the box
- App Studio — build and package custom extensions and apps (the new Helix for SaaS)
- Sitecore Connect — pre-built connectors: Salesforce, OpenAI, Gemini, and more
- Marketplace — discover and publish community-built agents and apps
Agentic Studio — Four Concepts Before You Build
🤖 Agents — one helper, one job
An agent has one clear, narrow purpose — “generate SEO metadata for a content item”. Keep scope tight. One agent = one job = consistent, predictable output. Sitecore ships 20+ pre-built agents (Content Generator, Blog Writer, Translation Assistant, Bulk Content Generator, Account Data Enricher, and more).
🔗 Flows — chain agents into a workflow
A visual canvas to chain multiple agents step by step. Example: Generate → Human review in Spaces → Publish. This is where single agents become business automation. Always include a review step before any publish action.
🗂 Spaces — shared review board
The team workspace where AI-generated output lands for human review before going anywhere. When a stakeholder asks “who approved that AI-written content?” — the answer is in Spaces: named reviewer, timestamp, edits made.
⚡ Signals — event-based triggers
Signals fire a flow automatically when a condition is met. Example: content performance drops below a threshold → fire the optimization flow. This is where reactive automation lives without custom polling scripts.
A Real Example: Bulk SEO Metadata — 600 Pages, Monday Deadline
A client had 600 product pages needing SEO titles, descriptions, and keywords before a Monday go-live. Previously: custom PowerShell, manual effort, a Saturday. With Agentic Studio:
Agentic Studio — flow structure
Bulk content trigger (content tree query)
↓
[Agent: Generate SEO Metadata + brand RAG context]
↓
[Spaces: Author Review Board] ← Human approval required
↓ (on approval)
[Publish to Experience Edge]600 pages queue through the agent overnight. Monday morning: authors open Spaces, approve or edit, publish. The weekend is saved.
App Studio — The Developer Extensibility Layer
App Studio is where developers build underlying extensions — custom connectors, UI plugins, packaged apps. Think of it as the modern replacement for custom pipelines and processor chains, deployed as versioned, shareable, Marketplace-distributable apps. For Helix veterans: same bounded module discipline, SaaS-native deployment instead of server-side.
Why This Matters for Our Teams
Before SitecoreAI
- Bulk ops = custom PowerShell scripts
- AI generation = external tooling
- No governed way to build reusable AI workflows
- Pricing complexity = slow procurement
After SitecoreAI
- Agents handle bulk ops with an audit trail
- Brand-aware generation in the authoring UI
- App Studio = governed, versioned extensions
- One metric per module — demo anything on day 1
Final Thoughts
SitecoreAI is a genuine platform shift, not a rebrand. Your toolchain carries over. Start exploring Agentic Studio with one simple agent in a sprint spike - prove value on a single use case before scaling. If your team is still on JSS for SitecoreAI, plan the Content SDK 2.x migration now. JSS is already end of life for this platform.
Stay tuned for more Sitecore-related articles, tips, and tricks to enhance your Sitecore experience.
Till then, happy Sitecoring! 😊