Oct 15, 2010
visibility 10394
star star star star star
(2 votes)

New license model in EPiServer CMS

Since the release of new license model (earlier this year) a lot has already been written in the form blog(s), article(s) etc but still we are getting questions regarding it and seems that our developers are still struggling with it.

First thing, in new license model, multisite limit has been taken away from the license file which means that if you are using CMS-6, you can only run one license with one site (enterprise). If you want to extend your solution by adding another site to your enterprise solution then you need to have another license file for that site. However there are couples of scenarios (Multiple Enterprise Sites with & without common code base) which are already described in this article.

2ndly, even in partner developer licenses there is no multisite limit anymore meaning that you have to install a new license file for every new site in your development environment. We encourage our developers to use new license model especially when using CMS-6 and above. Since partner developer licenses are for free to our partners and you can get the license file within couple of minutes so add a separate license file for every site in your project.

However if you still think that it’s a bit hectic (which isn’t I would say :)) to add more license files to your development environment than add a comment with your requirements while placing order for developer license or send request to sales at episerver dot com.

Oct 15, 2010

Comments

error Please login to comment.
Latest blogs
Finding Thomas Part 3 - The Moment of Recognition

Remember Thomas? In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard...

Ritu Madan | Jun 26, 2026

Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |