What Is Runtime-Based Licensing in COBOL?
Runtime-based licensing is a software licensing model where organizations are charged each time an application executes. Fees may be based on metrics such as transaction volume, CPU usage, or number of executions. In COBOL environments, this means costs can increase as workloads scale or as applications run more frequently across modern infrastructure.
In COBOL environments, runtime-based licensing imposes recurring costs each time an application is executed—costs that persist well beyond the initial compiler purchase. While initially tolerable in controlled, limited use environments, runtime-based licensing fees become increasingly burdensome as organizations adopt containerization, scale across hybrid infrastructures, or deploy applications in dynamic production ecosystems. Fortunately, there are modern alternatives that eliminate these costs without requiring a full system rewrite.
How Runtime-Based Licensing Slows Modern COBOL Development
Traditional runtime-based licensing charges based on metrics like CPU cycles, concurrent users, transaction volume, or execution frequency. As a result, every new deployment or usage spike comes with a financial penalty—often one that’s difficult to predict in advance.
Runtime-based COBOL licensing may charge organizations based on:
- CPU utilization
- concurrent users
- transaction volume
- application execution frequency
This model may have aligned with static, monolithic applications decades ago, but it creates friction in modern delivery pipelines. Continuous integration and automated testing introduce frequent executions. Containerized workloads spin up and down dynamically. Microservices may call COBOL logic thousands of times per hour. All of this means that the cost of running your software can quickly eclipse the cost of developing it.
During periods of market volatility, transaction volumes can surge dramatically. For example, on April 7, 2025, the National Securities Clearing Corporation (NSCC) processed 545 million transactions—a 33% increase over its previous peak in 2021. (DTCC 2025)
In systems where licensing models tie runtime fees to execution volume, these spikes can lead to sudden and significant cost increases. For organizations relying on COBOL-based systems to handle large volumes of mission-critical transactions, the financial impact of such usage-based licensing can be both substantial and difficult to forecast.
The Operational Cost of Uncertainty
The problem isn’t just financial—it’s architectural. When runtime costs are variable, they affect how decisions are made across engineering, finance, and operations. Teams become reluctant to containerize or migrate workloads when every move raises questions about licensing exposure. Deployment frequency is throttled to avoid triggering new fees. And modern development patterns—like autoscaling or dynamic routing—become cost centers rather than efficiency gains.
This undermines the core goals of modernization: flexibility, velocity, and cost efficiency.
Benefits of Fixed-Cost COBOL Licensing
Eliminating runtime fees means reclaiming control over how, where, and how often you run your applications. A fixed-cost licensing model simplifies budgeting, decouples technical decisions from licensing constraints, and supports continuous delivery practices without financial penalties.
That’s the approach provided by Fujitsu NetCOBOL, a fixed-cost COBOL compiler with no runtime execution fees.NetCOBOL: a zero-runtime-fee COBOL compiler backed by decades of enterprise deployment and supported by Fujitsu. With NetCOBOL, there are no charges for application execution—whether it runs once or a million times across environments.
A Cleaner Path Forward for COBOL Licensing
Runtime-based COBOL licensing forces organizations to optimize around cost rather than code. When execution fees are tied to transaction volume or application usage, engineering decisions become constrained by licensing exposure. This misalignment slows delivery, increases operational overhead, and limits the ability to scale applications across modern infrastructure.
By moving to a fixed-cost COBOL compiler like Fujitsu NetCOBOL, organizations eliminate runtime licensing fees and regain control over how their applications run. Without execution-based costs, teams can freely scale workloads, adopt modern deployment practices, and evolve their COBOL environments alongside the business.
Frequently Asked Questions
What is runtime-based licensing in COBOL?
Runtime-based licensing charges organizations each time a COBOL application executes. Fees may be calculated based on metrics such as transaction volume, CPU usage, or number of application executions.
Why do runtime fees become expensive in modern environments?
Modern architectures rely on frequent application execution through containerization, CI/CD pipelines, autoscaling infrastructure, and microservices. When licensing fees are tied to execution volume, costs can increase rapidly.
What is a fixed-cost COBOL compiler?
A fixed-cost COBOL compiler uses a licensing model where organizations pay for the compiler itself but do not pay fees when applications run.
How does Fujitsu NetCOBOL eliminate runtime licensing fees?
Fujitsu NetCOBOL is a COBOL compiler that does not charge runtime execution fees. Once applications are compiled, they can run as often as needed without additional licensing costs.
Learn more about Fujitsu NetCOBOL