# LoadRunner Cloud

> LoadRunner Cloud is a commercial, vendor-hosted cloud load testing service from OpenText, scripted in JavaScript, C, Java.

- Canonical: https://perf.jmeter.ai/tools/loadrunner-cloud/
- Review: https://perf.jmeter.ai/reviews/loadrunner-cloud/
- Official: https://www.opentext.com/products/loadrunner-cloud

- Vendor: OpenText
- Category: Cloud Load Testing
- License: Commercial — Commercial subscription; request a quote.
- Deployment: Cloud
- Status: Active
- Scripting: JavaScript, C, Java
- Protocols: HTTP, HTTPS, WebSocket, JMeter, Gatling, Kafka, MQTT, SAP, Citrix, Selenium
- OS support: Browser
- First released: 2019
- Latest release: 25.1 (25.1)
- Last verified: 2026-08-11

## What it is
LoadRunner Cloud runs performance tests from managed cloud infrastructure. It supports browser and protocol testing with integrated results and collaboration features.

## Choose it when
- Teams that want managed load generation without operating injectors
- Organizations budgeting for commercial licenses or subscriptions
- Groups comfortable scripting in JavaScript, C, Java

## Look elsewhere when
- Strictly air-gapped environments with no approved cloud path
- Projects that require a fully free open-source stack only

## Architecture
LoadRunner Cloud runs as a cloud service: scenarios use JavaScript, C, Java, while generators and orchestration are vendor-managed.

## Pricing
Pricing is flexible and based on usage, with options for Virtual Users (fixed license for a set number of users) or Virtual User Hours (VUH, a consumable pay-per-use model). Pay-per-use licenses can be purchased through OpenText sales or the AWS Marketplace.

## Compare
- [LoadRunner Cloud alternatives](https://perf.jmeter.ai/alternatives/loadrunner-cloud/)

## FAQ
### Who is LoadRunner Cloud for?
LoadRunner Cloud is best for teams that want managed load generation without operating generators themselves. It is commercial software, typically licensed for larger or governed programs. Vendor: OpenText. Deployment model: cloud. Commercial subscription; request a quote. Confirm details against the official site and a short proof-of-concept in your environment.

### How does LoadRunner Cloud differ from Apica?
Compared with Apica, scripting centers on JavaScript, C, Java rather than JavaScript. LoadRunner Cloud lists protocols HTTP, HTTPS, WebSocket, JMeter, Gatling, Kafka, MQTT, SAP, Citrix, Selenium; Apica lists HTTP, HTTPS, REST. Status is active versus active. Use the Test Rig to compare full specs side by side before a proof-of-concept.

### What scripting language and concurrency model does LoadRunner Cloud use?
LoadRunner Cloud uses JavaScript, C, Java for scripting or scenario definition. Runtime model: code-first scenarios where virtual users execute scripted behavior under load. OS support: Browser. Protocols: HTTP, HTTPS, WebSocket, JMeter, Gatling, Kafka, MQTT, SAP, Citrix, Selenium. Match these to how your team already authors tests and which systems you must drive under load.

### What is the cloud or enterprise path for LoadRunner Cloud?
LoadRunner Cloud is cloud-hosted: you run tests on vendor-managed infrastructure without operating load generators yourself. That usually speeds ramp-up for distributed load while shifting capacity planning and data residency to the vendor. Pricing model: Commercial subscription; request a quote. Confirm details against the official site and a short proof-of-concept in your environment.

### What are known limitations of LoadRunner Cloud?
LoadRunner Cloud limitations to weigh: cloud services trade operational simplicity for vendor pricing, data residency, and network path differences versus your production topology; commercial licensing and quotes can gate large-scale or enterprise use. Status: active. Always validate against your target protocols and scale with a proof-of-concept.

---
Curated by NaveenKumar Namachivayam (QAInsights) · methodology: https://perf.jmeter.ai/about/#methodology · corrections: https://github.com/QAInsights/Performance-Testing-Tools/issues/new?title=Tool%20submission%3A%20&body=Tool%20name%3A%20%0AOfficial%20URL%3A%20%0AWhat%20should%20be%20added%20or%20corrected%3F%20%0A