Sample report
- 01Custom codeAct now
- 02IntegrationsWatch
- 03Hosting and front endOn track
- 04Content move through Optimizely GraphWatch
- 05Team skillsOn track
- 06Recommended path and timelineOn track
Optimizely CMS 13 (PaaS) or SaaS: which fits your site?
A free technical audit for teams on Optimizely. We check your custom code, integrations, hosting, the content move through Optimizely Graph and your team's skills, then recommend PaaS with CMS 13 or SaaS, with a 3-year cost view.
- Certified partner
- DXP
- Certified partner
- Typical turnaround
- 5 days
- Typical turnaround
- Cost view
- 3 years
- Cost view
Support deadline · Nov 10, 2026
.NET 8 loses support November 10, 2026: move CMS 12 to .NET 10 or upgrade to CMS 13
Optimizely confirmed in May 2026 that CMS 12 supports .NET 10, so the deadline forces a framework move, not a new version. CMS 13, available since March 31, 2026, requires .NET 10 and Optimizely Graph, and drops Search & Navigation (Find).
Why Choose Sengo
As an official Optimizely Partner, Sengo helps organizations unlock the full potential of Optimizely’s DXP by combining deep technical expertise with a business-driven approach. We work closely with your teams to deliver faster, smarter, and more scalable digital experiences.
PaaS or SaaS: what changes for your site
Optimizely sells the same CMS two ways. CMS 13 is the PaaS version, where your .NET application, your custom code and your deployments stay under your control. CMS SaaS is run and upgraded by Optimizely, and your front end is hosted separately. Optimizely says both share one code base and will keep getting new features (Optimizely CMS SaaS).
The right choice depends on how much custom code and how many integrations your site carries, and on the skills of the team that runs it. That is what this audit checks.
What your report contains
A technical review of your Optimizely build that ends in one recommendation, PaaS with CMS 13 or SaaS, and what each costs.
Custom code
Every piece of code that runs inside the CMS today, such as scheduled jobs, initialization modules and event handlers. CMS 13 keeps it in your application. CMS SaaS does not run custom code in the CMS process, so each piece has to move or be rebuilt.
Integrations
Search, CRM, DAM, analytics, forms and commerce connections, with what each one needs on the target. CMS 13 does not support Search & Navigation (Find), so search moves to Optimizely Graph on either path.
Hosting and front end
On PaaS, your .NET application runs on Optimizely's cloud and your team deploys it. On SaaS, Optimizely runs and upgrades the CMS, and your front end runs on Vercel, Netlify or Optimizely's front-end hosting.
Content move through Optimizely Graph
Optimizely says PaaS customers can move their data to SaaS through Optimizely Graph, but not their .NET code or customizations. We map your content types to the SaaS model and list what has to be re-implemented.
Team skills
PaaS work and upgrades depend on .NET developers. SaaS moves most of the work to front-end developers who build on Optimizely Graph. We compare that with the team you have.
Recommended path and timeline
The option we would pick in your place, the order of work, the dates to hit and a one-page summary you can forward.
A 3-year cost view your leadership can approve
Every platform audit ends with the numbers a budget owner asks for, not only a list of technical findings.
01
What you spend today
Licence, hosting, support contracts and the internal time your team puts into the platform.
02
Each option over 3 years
Stay, upgrade or move, with build effort and running costs shown as ranges side by side.
03
Risk of waiting
What changes if you do nothing for 12 months: support status, security exposure and rising upgrade effort.
04
One-page summary
The recommendation, the cost and the timeline on one page you can forward to finance or your board.
How it works and who does it
A Sengo consultant who works on your platform runs the review and walks you through it. No sales script, and you keep the report.
- 1
Day 0
You send the form
A short form. We reply by email to book a 30-minute kickoff.
- 2
Days 1 to 2
Kickoff and access
We confirm your goals and get read-only access, or review what is public if access is not possible.
- 3
Days 2 to 4
Review
Custom code, integrations, hosting and the Graph content move, then the PaaS or SaaS cost comparison.
- 4
Day 5
Report and walkthrough
You get the report and a call to go through it. Implementation is a separate decision.
Typical timeline for most sites. Large multi-site platforms can take longer; we tell you at kickoff.
Get Your Free Audit
Submit the form. Get clarity and momentum.
Frequently Asked Questions
Is Optimizely CMS 13 PaaS or SaaS?
CMS 13 is the PaaS version of Optimizely's CMS, generally available since March 31, 2026. With PaaS you control the application and can run custom code in process. Optimizely calls its SaaS offering CMS SaaS. There, Optimizely runs the application and custom code cannot run in process (Optimizely CMS 13 FAQ).
Can we move from Optimizely PaaS to SaaS without rebuilding?
Not entirely. Optimizely says PaaS customers can move their data to CMS SaaS through Optimizely Graph, but .NET code and customizations do not move, and it calls the switch a re-implementation exercise with no easy migration method (Optimizely CMS SaaS). The audit lists what moves as data and what your team would rebuild.
What happens to our custom code and integrations on SaaS?
Code that runs inside the CMS today, such as scheduled jobs, initialization modules or event handlers, cannot run inside CMS SaaS (Optimizely CMS 13 FAQ). It has to move to your front end or to a separate service. On CMS 13 it stays in your application, but CMS 13 requires .NET 10 and replaces Search & Navigation with Optimizely Graph.
Who handles upgrades on Optimizely PaaS and SaaS?
On PaaS, your .NET developers apply each upgrade and fix any customizations it affects. CMS SaaS is versionless. Optimizely upgrades it automatically, and your front end runs on Vercel, Netlify or Optimizely's front-end hosting (Optimizely CMS SaaS).
What does the Optimizely Free Audit include?
A technical review of your Optimizely build: custom code, integrations, hosting, the content move through Optimizely Graph and your team's skills. It ends with a recommendation, PaaS with CMS 13 or SaaS, and a 3-year cost view for each option.
Do I need to provide access to my Optimizely account?
Yes, limited read-only access allows our experts to perform a thorough evaluation. We guide you through secure access sharing and follow strict privacy practices.
How long does the audit take?
Most Optimizely audits are completed within 5 business days, depending on your platform’s complexity and integrations. Large multi-site platforms can take longer; we tell you at kickoff.
Will you make changes to my Optimizely setup during the audit?
No, the audit is non-intrusive. We analyze your setup, test configurations, and provide a detailed set of recommendations without altering your production environment.
What happens after I receive my audit report?
Once the audit is complete, we’ll schedule a walkthrough session to explain our findings and answer your questions. You can choose to implement the recommendations internally or work with Sengo’s Optimizely-certified experts for ongoing optimization.
