Runtime Licenses
An application built with TX Text Control .NET Server needs runtime licenses when you deploy it. Before you plan a deployment to servers, virtual machines, containers or cloud services, find out how many runtime licenses the deployment requires.
What a Production Server Is
TX Text Control .NET Server requires runtime licenses for the deployment to production servers. These are the servers where your application, built with TX Text Control .NET Server, is running.
Runtime licenses are separate deployment licenses. They do not replace developer licenses: each developer who compiles your application still needs a development license.
The license agreement (section 4a) describes the same rule for server-based programs. They may only be installed on a single server or virtual machine, but may be accessed by an unlimited number of clients. Additional licenses are required when you install TX Text Control on more than one server or virtual machine (per operating system).
What One Runtime License Covers
A single runtime license lets you install your application on a single production server (per operating system):
- One server or virtual machine. Each additional server or virtual machine needs its own runtime license.
- Any number of applications on that server. More than one TX Text Control .NET Server based application can run on a single server and is covered by one license.
- Any number of users and clients. The number of users who access the applications on the server is not limited.
The following examples show how the number of servers, not the number of applications, determines the number of runtime licenses:
| Deployment | Runtime licenses required |
|---|---|
| Four TX Text Control .NET Server based applications running on one server | 1 |
| Four TX Text Control .NET Server based applications installed on three servers | 3 |
Cloud and Container Deployments
In the cloud, the standard deployment licensing is applied per instance: each running instance of your application requires a separate license. This matters when a platform scales your application horizontally:
| Platform | What counts |
|---|---|
| AWS Fargate | Each container instance that is created as demand increases runs its own instance of TX Text Control. |
| Azure App Services | Each additional instance added by horizontal scaling requires a separate license. |
| Kubernetes | Each pod that hosts TX Text Control requires its own license. |
As your application scales out, the number of runtime licenses grows with the number of instances, and you need to track the instances to stay compliant. If the number of instances changes dynamically or is not predictable, consider the unlimited runtime (OEM) license.
For the technical side of these deployments, see the Deployment Guide.
Development, Test and Staging Machines
- Development machines. Developer licenses are assigned to developers and are not licensed per machine.
- Build servers. For development purposes, the product is not licensed per build server. See Build Servers and CI/CD.
- Trial version. The trial version must not be installed on a production server.
- Test and staging servers. The license agreement and the Text Control pricing information do not describe test or staging servers separately. Before you install your application on such servers, ask the Text Control sales team whether they need runtime licenses.
What Happens on the Server
The license is compiled into your application from the NuGet package when you build it, so you deploy the application with its files as usual. You do not need a developer license on the production server. TX Text Control does not require a cloud-based licensing service, periodic online validation or an external activation server to keep your applications running.
Make sure that you have a runtime license for every production server, virtual machine or instance before you deploy.
Getting Runtime Licenses
A standard TX Text Control .NET Server package includes two runtime licenses, and you can purchase additional runtime licenses if needed. To find out how many runtime licenses your deployment needs, or to request a quote, contact the Text Control sales team.
The license agreement is binding. If you are unsure whether a deployment is covered, for example because instances are created and removed automatically, ask the sales team before you deploy.