--- title: Managing site license keys related: - https://docs.kentico.com/13/configuring-xperience/managing-sites.md - https://docs.kentico.com/13/configuring-xperience/managing-sites/setting-domain-names-for-sites.md --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). Xperience requires a license key for every [domain](https://docs.kentico.com/13/configuring-xperience/managing-sites/setting-domain-names-for-sites.md) that your sites use. You cannot view or edit sites running on domains that do not have a matching license in the system. If you do not have a valid license for the current administration domain, only global applications are available in the administration interface. To manage your system's licenses, open the **License keys** application in the Xperience administration interface. ![Managing licenses in the system](https://docs.kentico.com/docsassets/13/managing-site-license-keys/Licenses.png "Managing licenses in the system") When you obtain a license key (full or trial) for a domain: 1. Click **New license**. 2. Copy the full license key into the field. 3. Click **Save**. The License keys page displays a list of all licenses added to your system, including the domain names, expiration dates and license editions. A domain can only have one attached license. If you are replacing an expired license or upgrading the license to a higher version, you first need to delete the current license by clicking the delete button (). Deleting a license does not in any way affect the content or settings of the site running on the given domain. > **Note:** **License expiration** > > Most licenses have a specified expiration date, and become invalid midnight (0 hours) at the **start** of the given date. For example, if a license has an expiration date of December 31, the last day it remains functional is December 30. ## Obtaining licenses You can generate your license keys on the [Kentico Client Portal](https://client.kentico.com/). On the Client Portal, you need to register your license (Serial Number) which you obtained after buying Kentico Xperience. You can then generate new license keys based on the registered license. If you cannot sign in to the Client Portal, please contact the person in your company who has the credentials and the license. ## How licensing works > **Note:** **Site licensing** > > If your live site and Kentico Xperience administration applications run on different domains, you need to have valid licenses for both domains. To learn more, see: [Licensing for Xperience applications](https://docs.kentico.com/13/configuring-xperience/managing-sites/managing-site-license-keys/licensing-for-xperience-applications.md) License keys support all protocol and www prefix combinations for the specified domain. Every valid license key also allows you to use the local server's hostname (_localhost_ and loopback IP addresses – _127.X.Y.Z_). For example, if you add a license key for the _**example.com**_ domain, you can use all of the following domains: - _http://example.com_ - _https://example.com_ - _http://www.example.com_ - _https://www.example.com_ - _http://localhost_ - _http://127.X.Y.Z_ (where X, Y and Z are in the range 0–255) If your site uses a **Presentation URL** with a different domain or [domain aliases](https://docs.kentico.com/13/configuring-xperience/managing-sites/setting-domain-names-for-sites.md) (alternative domain names for the same website), you need to add extra license keys for these domains. You can generate the domain alias license keys on the [Kentico Client Portal](https://client.kentico.com/). Domain alias licenses are free of charge if you already own a license for the main domain. ### Web farm count checks Each license key supports a certain number of [web farms](https://docs.kentico.com/13/configuring-xperience/setting-up-web-farms.md), ranging from one to unlimited. The system distinguishes between web farms for the administration interface and the live site. Each key can increase the total number of administration or live site web farms, based on the domain for which the license key is generated. This is based on the **Administration domain name** and **Presentation URL** properties configurable for each site in the **Sites** application. The number of allowed web farms is cumulative and not tied to individual sites (license key domains). For example, if you have the following live site license keys registered in the system (keys generated for domains that match a _Presentation URL_ in the _Sites_ application): - livesiteA.com; AllowedWebFarms:2 - livesiteB.com; AllowedWebFarms:3 You can have a total of five live site web farms distributed arbitrarily across _livesiteA.com_ and _livesiteB.com_. > **Note:** **Domain alias license keys** > > License keys generated for the purpose of enabling [site domain aliases](https://docs.kentico.com/13/configuring-xperience/managing-sites/setting-domain-names-for-sites.md) **do not** contribute to the total number of web farm servers allowed for either application. The system **completely disregards** such keys during validation. The following table summarizes common hosting configurations and resulting web farm limitations: | Environment | Hosting domains | Web Farms | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 administration
1 live site | Different domain for each site, for example:
livesite.com
admin.livesite.com | The number of administration and live site web farms is controlled by each license key separately. | | 1 administration
1 live site | Same domain for both the live site and the administration interface (e.g., running in a virtual directory):
livesite.com
livesite.com/admin | The maximum number of web farms is controlled by the license key for _livesite.com_. The key's web farm limit applies to both applications separately.
For example, if the limit is four, you can have up to _four_ administration web farms and up to _four_ live site web farms. | | 1 administration
_n_ live sites | Different domain for each live site, shared administration (each live site as a separate site in the _Sites_ application). For example:
livesite1.com
admin.livesite1.com
livesite2.com
admin.livesite2.com
... | The maximum number of live site web farms is the sum of all web farms allowed by license keys generated for live site domains. That is:
_livesite1.com + livesite2.com + ... + livesiteN.com_
The maximum number of administration web farms is the sum all web farms allowed by license keys generated for all administration domains minus the number of sites managed by the administration application. That is:
_admin.livesite1.com + admin.livesite2.com + ... + admin.livesiteN.com - NumberOfManagedSites_
The final subtraction is required due to the way Xperience license are designed. |