Licenses one application, developed for internal use, to embed AG Grid Enterprise and / or AG Charts Enterprise in perpetuity.

• Includes a 1-year subscription to new versions, support and maintenance.
• For customer-facing applications you will also need a Deployment License add-on.
• All concurrent, front-end, JavaScript developers working on the Application would need to be added to the license count, not just the ones working with AG Grid and / or AG Charts.
• Developers within the Single Application Development License count are unnamed, so long as the total licensed count isn’t exceeded.
• Single Application Development Licenses are bound to an application name and can’t be reused on other applications.

Licenses unlimited number of applications, developed for internal use, to embed AG Grid Enterprise and / or AG Charts Enterprise in perpetuity.

• Includes a 1-year subscription to new versions, support and maintenance.
• For customer-facing applications you will also need a Deployment License add-on.
• All concurrent, front-end, JavaScript developers working across the licensed Applications would need to be added to the license count, not just the ones working with AG Grid and / or AG Charts.
• Developers within the Multiple Application Development License count are unnamed, so long as the total licensed count isn’t exceeded.

Allows licensed developers to sub-license AG Grid and / or AG Charts for one application on one production environment in perpetuity. Includes a 1-year subscription to new versions, support and maintenance. Only available with a Developer License.

• A Deployment License Add-on allows making a project available to individuals (eg your customers) outside of your organisation (sub-license).
• One Deployment License Add-on covers one production environment for one project.
• Only production environments require licensing. All other environments (eg development, test, pre-production) do not require a license.
• We do not charge per server. A cluster of many servers part of one application installation is considered one deployment and requires one Deployment License. This is true so long as the application instances within the cluster are replicas of each other and server provides load balancing and fail over only.
• Production failover deployments do not need to be licensed separately. They are considered part of the overall application production deployment.
• Multi-tenant deployments, where one application instance is serving many customers over different URLs, is considered one deployment, as each tenant is getting serviced by the same application instance.
• Different instances of the same application, where the instances are not part of a cluster for fail over or load balancing, are considered independent deployments and need a Deployment License for each individual application instance.
• Deploying an application to a cloud service (eg AWS or Docker) requires one Deployment License, regardless of how many virtual containers or servers the cloud application spawns for that one single instance of the application.