# OEM / Unlimited Runtime > Deploy to unlimited servers with the OEM license of TX Text Control .NET Server: no instance tracking when AWS Fargate, Azure or Kubernetes scale out. - **Product:** TX Text Control .NET Server - **Section:** Documentation - **Kind:** Topic - **Path:** TX Text Control .NET Server > Installation Guide > License Configuration > OEM / Unlimited Runtime - **889 words** - **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/oem/ - **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/oem/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/oem/llms-full.txt --- Applications that run on many servers, or on a cloud platform that adds and removes instances automatically, are the case for the unlimited runtime (OEM) license of TX Text Control .NET Server. Learn what it allows, how it differs from individual runtime licenses and in which deployments it makes sense. ### What the OEM License Allows The optional unlimited runtime (OEM) license lets you deploy your application to an unlimited number of servers. - **Unlimited instances.** You can deploy TX Text Control in your application without counting the instances or pods that run it. Whether your application runs one instance or hundreds, a single OEM license covers them. - **No instance tracking.** Cloud platforms create and shut down instances unpredictably. With an OEM license, you do not need to track individual instances for licensing purposes. - **Deployment only.** The OEM license is a runtime license, so it covers the deployment instead of individual [runtime licenses](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/runtime/llms-full.txt) per server. It does not replace developer licenses: each developer who compiles your application still needs an assigned [development license](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/development/llms-full.txt). ### Runtime Licenses and the OEM License Compared | | Runtime licenses | Unlimited runtime (OEM) license | |---|---|---| | Servers covered | One production server or virtual machine (per operating system) per license | Unlimited | | Applications and users per server | Not limited | Not limited | | Scaling out to new instances | Each new instance or pod requires a valid license | Covered | | Tracking instances | Required to stay compliant | Not required | | Developer licenses | Required for each developer | Required for each developer | ### When the OEM License Makes Sense The standard runtime licensing is applied per instance, which works well for static deployments with a known number of servers. It becomes harder to manage when your platform scales your application dynamically: - **AWS Fargate** creates new container instances of your application as demand increases, and each of them runs its own instance of TX Text Control. - **Azure App Services** adds application instances with horizontal scaling to handle traffic spikes. - **Kubernetes** creates pods that run your application based on the workload, and each pod that hosts TX Text Control needs a license under the per-instance model. In all of these cases, the number of runtime licenses grows with the number of instances. The OEM license covers any number of instances, so you can scale without adding licenses. If you distribute your application to customers who install it on their own servers, these installations need runtime licenses or OEM deployment rights as well. Confirm with the sales team that your distribution model is covered. For the technical side of scaled deployments, see [Scaling Containers](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/docker/scaling/llms-full.txt), [Kubernetes](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/kubernetes/llms-full.txt), [AWS](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/aws/llms-full.txt) and [Azure](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/azure/llms-full.txt). ### Contact Sales The license agreement is binding, and the OEM license is an optional license that you purchase in addition to your developer licenses. Text Control's sales engineers help you define your licensing needs and determine whether the unlimited runtime license fits your deployment scenario. Contact the [Text Control sales team](https://www.textcontrol.com/contact/) for details and a quote. The blog post [Why an Unlimited Runtime License (OEM) for TX Text Control is Perfect for Cloud Deployments](https://www.textcontrol.com/blog/2025/01/08/why-an-unlimited-runtime-license-oem-for-tx-text-control-is-perfect-for-cloud-deployments/) describes the cloud scenarios in more detail. ### Related Pages - [Runtime Licenses](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/runtime/llms-full.txt) — what one runtime license covers and how cloud instances count. - [Development Licenses](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/development/llms-full.txt) — license developers and get the license into your projects. - [Licensing Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/overview/licensing/llms-full.txt) — the licensing model in plain words. - [Deployment Guide](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/llms-full.txt) — run your application on Windows, Linux, Docker and in the cloud. --- ## Nearby - **Previous:** [Runtime Licenses](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/licensing/runtime/llms-full.txt) - **Next:** [Upgrade Guide](https://docs.textcontrol.com/tx-text-control-dotnet-server/installation/upgrading/llms-full.txt)