search
AI OnAI Off
CMS 13.2.0 on-prem: what happens when Opal and Opti ID are built in but not supported?
Scott Reed
workspace_premium
workspace_premium 
Vote:
It looks self-explanatory. At least, it works on my local setup.
(1 attachment from the Slack thread was not included.)
Sep 28, 2026 14:06
Vote:
The FAQ is a snapshot for GA, not for after it, so the release notes are the most accurate source.
(1 attachment from the Slack thread was not included.)
Sep 28, 2026 17:02
Scott Reed
workspace_premium
workspace_premium
Vote:
Yes, but the FAQ reflects the CMS 13 direction: on-prem solutions have limited functionality and don't support Opti ID and Opal. I checked recently with an Optimizely product owner and this is not going to change. It is an architectural point about on-prem hosting, so unless the release notes specifically say otherwise, it is still unsupported. I was asking specifically about on-prem hosting, where Opti ID and Opal would be disabled in production. It will likely behave like local development, where it simply doesn't work without a key set up. I have several on-prem clients going through upgrades. Previously we didn't include the Opal or Opti ID packages, but now they are built into the core solution, so I wanted to be certain there was nothing to be aware of.
Sep 29, 2026 8:25
Scott Reed
workspace_premium
workspace_premium
Vote:
Since everything runs locally without Opti ID and Opal, it will likely work on-prem too, and I don't think it will be an issue. The question was just to see if there was anything to be aware of.
Sep 29, 2026 9:24
Vote:
As mentioned on the other thread, it should not be an issue. If you don't enable it in the startup.cs file, the chat should not show up. Feel free to raise support tickets if you face any issues.
Sep 29, 2026 10:03
Vote:
I've been told that "...CMS 13 / 15 will run without OptiID but you'd be limited in what you could make use of..." (for on-prem), and "...OptiID is not currently supported for on-prem (it is in the roadmap) ... It would mean that you lose out on a few features like Content Manager, External Content & (of course) Opal..."
Sep 29, 2026 18:56
Vote:
I'm working on an on-prem upgrade from CMS 12, and 13.2 is working locally. I have an issue with the visual builder, though, so I need to wait for 13.3 for that bug to be fixed.
Oct 05, 2026 16:45
The latest CMS 13 package has Opal built in (see the 2026 Optimizely CMS 13 release notes: https://support.optimizely.com/hc/en-us/articles/44937048830221-2026-Optimizely-CMS-13-release-notes#h_01KX79GE2YN91SGMG7KZCCKCM9). However, the CMS 13 FAQ (https://docs.developers.optimizely.com/content-management-system/v13.0.0-CMS/docs/faqs-for-cms-13) says that on-prem does not support Opti ID + Opal.
What happens with the on-prem version 13.2.0? Has it been tested so that, when Opti ID and Opal can't work, the project still runs?
Originally asked in the Optimizely Community Slack: #content-management.