Licenses
Activate your Xperience by Kentico application by following the steps described below for each subscription type:
- Xperience by Kentico subscription providing an Xperience Portal project for deploying to the SaaS environment.
- License-only subscription – for self-managed Xperience deployments.
- Evaluation license – a 30-day evaluation license.
Subscription expiration and renewal
Contact Kentico sales to renew your subscription.
Subscriptions expire at midnight (0 hours) at the start of the expiration date. For example, if a subscription expires on December 31, the last day it remains valid is December 30.
Self-managed Xperience deployments and Xperience Portal projects (SaaS deployment) expiration dates include a 30-day grace period. The grace period does not apply to evaluation licenses.
Evaluate Xperience by Kentico
Create an account in Kentico Client Portal to receive a 30-day evaluation license key. For more information, see License keys.
Licensing Xperience by Kentico
When you purchase an Xperience by Kentico SaaS subscription, you receive access to an Xperience Portal project. The purchased service plan defines the set of available features in the Xperience Portal. You can see your current service plan on the Dashboard in the Xperience Portal.
To help you decide which service plan best fits your needs, check the overview of the individual plans and their differences:
Feature | Level 1 | Level 2 | Level 3 |
Xperience Portal (Service Management) | |||
Included portal users | 20 | 20 | 20 |
User invitation management | |||
Role-based access control with pre-defined roles | |||
Multi-factor authentication using One Time Passwords | |||
One-Click Automated Deployments to/between environments | |||
Deployment API – programmatic and direct package upload options | |||
Deployment history and troubleshooting logs | |||
Performance Insights, Monitoring & Analytics | |||
Individual Services Status – available per customer tenant within the Xperience Portal | |||
Domain management – custom website domains and email sending domains | |||
Handsfree automated license token management – channel licenses, renewals, etc. | |||
License key generator – for localhost developer license keys | |||
On-demand backups for all environments – full and partial backups | |||
Self-service restore from backup | |||
Environment services | |||
Environments Includes separation of duties and dedicated resources for a single tenant | 1 Non-Production (QA) 1 Production | 1 Non-Production (QA) 1 Production | 2 Non-Production (QA and UAT) 1 Production |
Standard Performance for web channel marketing (P1V2 for Production, S1 for QA) | High Performance for omnichannel marketing (P2V2 for Production, S1 for QA) | Premium Performance for advanced omnichannel marketing (P3V2 for Production, S1 for QA / UAT) | |
Temporary auto-scaling and load balancing for production – in case of a rare peak in workload | On by default | On by default | On by default |
Database | Standard Performance | High Performance | Premium Performance |
Media file storage (blob) | 50GB | 250GB | 500GB |
Email delivery service (supports transactional and marketing) | 10,000 emails / month | 50,000 emails / month | 100,000 emails / month |
Bandwidth | 100 GB / month | 500 GB / month | 1000 GB / month |
CDN with dynamic routing – total for all environments | 100 GB | 500 GB | 1000 GB |
Backups – for application service, database and storage | |||
Security | |||
Personal access token generator – for secure access to the deployment API | |||
Transport layer security, secure communications, database encryption and anti-CSRF | |||
Web Application Firewall (WAF), DDoS, bot mitigation and SQL injection protection | |||
Key Vault for storing sensitive data | |||
Business continuity | |||
Weekly Backup Retention Schedule | 30 days | 30 days | 30 days |
Daily Backup Retention Schedule | 3 days | 3 days | 7 days |
Geo-redundant database, storage and backups for production | |||
Uptime Service Level Availability | Designed for 99.9% | Designed for 99.9% | Designed for 99.9% |
Support | |||
Kentico Managed Service | |||
Technical Support – ticketing system, email or live chat | Standard or Premium options available | Standard or Premium options available | Standard or Premium options available |
Availability Management and Health Monitoring | 24/7/365 | 24/7/365 | 24/7/365 |
Public Status Page – opt-in notification subscription | |||
Root Cause Analysis | |||
Updates, patches and fixes to Xperience Portal and cloud services | |||
7 day bug fixing policy – for non-third party issues | |||
Service plan change
Over time, your requirements for the service plan you use may change. When they do, contact Kentico sales and renegotiate with them your subscription plan and agree on a time for a scheduled Xperience Portal project maintenance. Your new service plan will be active once the scheduled maintenance finishes.
Licensing for applications in the SaaS deployment environments (QA, UAT, Production) is automatically handled by the Xperience Portal, except for local development environments.
License keys for SaaS local development
Activate your local development instance by generating a license key in Xperience Portal:
Open the License key generator application in Xperience Portal.
Select your Xperience by Kentico version.
Select Generate license key.
Store the license key in a text file before you leave the license key generator.
Lost license keys cannot be recovered. If you lose the license key, you will need to generate a new one.Register the license key in the Xperience administration to activate your local Xperience instance. See Register license keys in Xperience.
The local development instance is activated. The license key expires with your subscription, but its expiration date is automatically extended with every subscription renewal when your local Xperience instance is connected to the Internet.
Licensing self-managed Xperience deployments
Activate self-managed Xperience projects by registering your license keys in the Xperience administration. For more information, see Register license keys in Xperience.
Obtain license keys by registering the serial number you received with your Xperience by Kentico purchase in the Kentico Client Portal.
Contact Kentico support if you cannot sign in to the Kentico Client Portal.
License keys
Each Xperience by Kentico instance must be activated using a license key tied to a license in the Kentico Client Portal. You can generate the following types of license keys:
- Evaluation – provides full access to all features of the product for 30 days.
- Production – for live deployments. See Production license keys.
- Non-production – for local development and pre-production environments (deployment pipelines, QA). See Non-production license keys.
License keys must be registered via the Xperience administration or during project database installation.
All license keys support unlimited auto-scaling, allowing sites to accommodate increased traffic and performance demands.
License server communication
To ensure fair product use, Xperience instances communicate with the Kentico license server on a daily basis. As a result, a working Internet connection is mandatory for all instances. License server communication uses the following endpoint: https://api.kentico.com/licensing/licenses/instanceverification. Ensure this URL is whitelisted and accessible from your network.
When an Xperience instance cannot reach the Kentico license server for longer than five days, the administration interface starts notifying users via information popups and the event log. If you keep encountering issues after verifying that your instance is connected to the internet and the communication endpoint is accessible, contact our support department at support@kentico.com.
Register license keys in Xperience
Product license keys are managed via the Settings application under System -> Licenses.
To register a license key:
- Open the Settings application.
- Navigate to System -> Licenses.
- Insert your license key into the License key setting.
- (Optional) Set a friendly name for your instance. This value will be used in the license overview section of the Kentico Client Portal. You can use friendly names to identify instances under a single license.
- Save the changes.
The product is now activated using the provided key.
Production license keys
Production license keys are intended for final, live product deployments.
Xperience by Kentico instances activated using production license keys perform daily checks that monitor product feature use (the number of active website channels, for example).
If the instance detects feature use that is outside the scope of the corresponding license, the administration interface displays a warning banner detailing the violation. Product use is not limited in these cases. However, note that such actions are monitored and you may be contacted by a Kentico representative should they persist for a prolonged period of time.
After addressing any reported issues, you need to wait for the next daily check before the warning banner disappears from the administration interface.
Non-production license keys
Non-production licenses are intended for local development and pre-production environments (deployment pipelines, QA).
Xperience by Kentico instances activated using non-production license keys do not monitor product feature use. Avoiding license overreach when using non-production license keys is the user’s responsibility.
License violation reporting
When the system detects a license violation, such as instances exceeding the number of allowed channels, it notifies users via the event log and a warning banner displayed atop the administration interface workspace. The banner and event log entries provide details related to the violation and steps necessary to correct it.
License violation notifications are displayed across all instance registered under the same license.
For example, assume an environment with three instances (A, B, and C) registered using three separate production license keys generated from a single license. If instance A violates the license, instances B and C start displaying license violation notifications as well. However, instances B and C only know that a license violation occurred, they aren’t provided any specific details. They will only highlight the type of violation, not the instance responsible (A in this example). After correcting the violation, all instances return to normal.