Your sale day brings ten times the usual traffic. Find the breaking point before your customers do — OpenText Performance Engineering, formerly LoadRunner, plays your user journeys as thousands to millions of virtual users across 180+ protocols, on your own servers or as Core SaaS — with AI scripting in VuGen and a free 50-user Community licence.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
This page covers OpenText Performance Engineering — the Professional, Enterprise and Core editions, formerly LoadRunner. The rest:
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
Software plays recorded user journeys as thousands of virtual users at once, to find the breaking point before real users do.
What consolidation actually replaces, dimension by dimension.
| Dimension | Ad-hoc load scripts before launch | OpenText Performance Engineering |
|---|---|---|
| When load is tested | The week before a big launch, if at all | On every build, as a CI pipeline step |
| Which systems are covered | Web pages only; SAP and legacy left out | 180+ protocols, SAP GUI to LLM apps |
| Writing the scripts | Hand-coded, re-correlated each release | TruClient recording and Aviator in VuGen |
| Finding the bottleneck | Response times in one tool, servers in another | APM metrics merged into one analysis |
| Reaching peak load | As many users as spare laptops allow | Cloud generators; 5M+ users claimed on Core |
| What it is NOT | — | Functional testing, monitoring or a price list |
The cheapest test is free: script one journey on the 50-user Community licence, run it with server monitors attached, and see what breaks first.
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
VuGen records and edits protocol-level scripts, TruClient records in a real browser, and Aviator suggests code and fixes inside VuGen as you script.
The Controller sets virtual users, ramp-up and duration for a scenario; Enterprise adds a central server that schedules tests and shares assets across teams.
Generators on your own machines or in the cloud play the scripts; Core spreads load over 40+ AWS, Azure and Google Cloud regions or your own hosts.
Analysis merges response times with server metrics from tools such as Dynatrace, Datadog or Prometheus; an AI Analysis add-on flags anomalies.
Scripts from VuGen and TruClient, load from your hosts or the cloud — one analysis lining response times up with server metrics.
OpenText Performance Engineering finds the load at which your application slows or breaks, before your users find it for you.
Bundles cover web, mobile, SAP, Oracle E-Business, Java, .NET, databases and remote desktop, plus an LLM protocol added in 2025.
TruClient scripts the page as a user sees it; with auto-correlation, OpenText claims script creation runs twice as fast.
A chat that knows the open script writes and explains code, and a right-click on a replay error asks Aviator what went wrong.
Existing JMeter, Gatling and Selenium scripts run beside VuGen scripts, so a team’s earlier work is not thrown away.
Generators run on your own hosts or in the cloud; Core claims 5 million+ virtual users across 40+ cloud regions.
Plug-ins for Jenkins in all three editions, plus GitHub Actions, Azure DevOps and GitLab, run tests on each build.
Integrations pull data from Dynatrace, AppDynamics, Datadog, New Relic, Prometheus and CloudWatch into one analysis.
The Core Performance Engineering Analysis add-on lets engineers query a run in plain language and surfaces anomalies.
26.x releases add MCP support, so an AI agent can build a DevWeb script from a Swagger file or query test results.
Release 26.1 for the Core and Professional editions, the Enterprise 26.3 MCP server, and a customer story from o9 Solutions. All from OpenText’s official channels, the release videos on the former Micro Focus channel.
Aviator scripting and AI-driven analysis arriving in the SaaS edition with release 26.1.
What 26.1 changes for the on-premises Professional edition, from VuGen scripting to analysis.
How the Enterprise edition’s MCP server lets AI agents work with tests and results in 26.3.
A software company explains how it uses the SaaS edition to test releases before customers see them.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Here’s what genuinely sets it apart — and exactly where it stops.
OpenText lists more than 180 protocols and technologies, with bundles for SAP GUI and SAP Web, Oracle E-Business, Java, .NET, databases, remote desktop and mobile. In 2025 it added an LLM protocol for apps built on large language models, so one licence can test the old client-server system and the new chatbot.
Professional suits one site running one test at a time on its own servers. Enterprise lets distributed teams run tests concurrently and share scripts, generators and results. Core moves the same work to OpenText-hosted SaaS, with a 30-day trial and load from more than 40 cloud regions.
Release 26.1 made Performance Engineering Aviator generally available inside VuGen: a chat that reads the open script, plus an Ask Aviator option on replay errors. MCP support lets an agent build a DevWeb script from a Swagger file, and an AI Analysis add-on answers questions about a finished run.
Every paid edition is quoted, and Core names no hosting region. The free licence leaves out the COM/DCOM, Templates and GUI bundles. VuGen scripts only run on OpenText’s engines. OpenText classes the DevOps testing line as non-core and is divesting non-core units, so ask about the roadmap first.
List the five to ten user journeys that make money, the peak you expect for each, and the response times you will accept.
Script one journey on the free 50-user Community licence or the 30-day Core trial, and note which protocol bundles it needs.
Record the remaining journeys in VuGen or TruClient, fix correlation with Aviator’s help, and import any JMeter plans.
Ramp to your expected peak with server monitors attached, find the first bottleneck, fix it and run again.
Add a smaller regression load test to Jenkins, GitHub Actions or Azure DevOps so each build is checked against the baseline.
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
“Our SAP GUI order-entry flow could not be load tested with anything else we trialled. VuGen handled it in a week.”
“We found the payment gateway’s connection-pool limit at three times normal load, a month before the festive sale.”
“Bringing our old JMeter plans into the same scenario as VuGen scripts saved a rewrite we had budgeted a quarter for.”
“Aviator explains a correlation error faster than our wiki does, though we still check every function it suggests.”
“Enterprise lets our Pune and Chennai teams book controllers without clashing. Before, tests ran only at night.”
“Powerful, but new engineers need weeks to be productive, and the virtual-user quote took longer than the pilot.”
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the load testing market — tap any vendor to see why it sits where it does.
Execution strength vs product vision — the classic market map, minus the paywall.
Quote-only; free 50-user Community licence.
The grid nobody publishes — how many kinds of application a tool can load test vs how far its load can scale without your own hardware.
180+ protocols incl. SAP GUI; 5M+ users claimed on Core.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Against Grafana Cloud k6, Tricentis NeoLoad, BlazeMeter, Azure Load Testing and Apache JMeter — on deployment, protocols, price, scale, AI, governance, support and India.
| Dimension | OpenText Performance Engineering | Grafana Cloud k6 | Tricentis NeoLoad | BlazeMeter | Azure Load Testing | Apache JMeter |
|---|---|---|---|---|---|---|
| What it is | Load-testing family | Managed k6 in Grafana | Enterprise load testing | Open-source test cloud | Azure’s managed service | Free open-source tool |
| Deployment | On-prem, hybrid or SaaS | SaaS or self-run | SaaS or on-premises | SaaS; OPL on Unleashed | Azure-only service | Your own machines |
| Protocol coverage | 180+ protocols | HTTP, gRPC, WebSockets | SAP, Citrix, mainframe | What the engine speaks | JMeter or Locust only | HTTP, JDBC, JMS, more |
| Pricing model | Per virtual user | Per virtual-user hour | Quote, annual term | Tiered plans | Per VUH, pay as you go | Free, Apache licence |
| Published entry price | Free 50 VUs, then quote | $19/month + $0.15/VUh | Not published | $99/month, yearly | $0.15 per VUH | Free |
| Included vs add-on | Bundles and add-ons | Enterprise extras | Suite links cost extra | SSO only in Unleashed | Azure costs on top | Nothing bundled |
| Scale limits | 5M+ VUs (Core claim) | 1M concurrent, Ent. | Millions, per Tricentis | 50 to 5,000 VUs | 400 engines a run | Your hardware |
| Analysis and AI | Aviator, MCP, AI add-on | Grafana dashboards | Agentic analysis, MCP | Reports, AI test data | Metrics, test criteria | HTML report |
| Integrations | CI, APM and chaos tools | CI-friendly CLI | CI and two-way APM | CI pipelines and APM | Azure DevOps, GitHub | Plugins and wrappers |
| Governance and SSO | RBAC; shared repository | SAML on paid stacks | SAML 2.0 SSO | SSO on Unleashed only | Entra ID and Azure RBAC | None built in |
| India load and data | Self-host in India | Mumbai load zone | On-prem keeps it here | Mumbai load locations | Central India region | Wherever you run it |
| Support | 24x7 SaaS operations | 8×5 email on paid tier | Tricentis support | Tier 2; Tier 1 on top | Paid Azure plan | Community only |
| Lock-in and exit | VuGen scripts stay put | Open-source scripts | NeoLoad format, YAML | Bring your own scripts | Standard JMeter, Locust | No vendor at all |
| Best fit | SAP and legacy estates | Developer-led API tests | Tricentis SAP shops | JMeter at cloud scale | Azure-hosted apps | Budget, skilled teams |
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
OpenText Performance Engineering is one of 35 developer tools products TechBag carries. The Developer Tools guide narrows them to a shortlist and shows the reasoning. →
Drag the sliders (load-test scripts you maintain; engineer-hour cost). Estimates model the engineering time spent re-recording and re-correlating scripts after application changes, at an assumed 1.5 hours per script a year, with 70% of it saved by browser recording, auto-correlation and AI help in VuGen. Both figures are assumptions. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Quote only. OpenText publishes no price for Professional, Enterprise or Core Performance Engineering. Licences are counted in virtual users — permanent, time-limited, or Virtual User Flex Days that last 24 hours from first run and lapse a year after purchase — and protocols are sold in bundles. OpenText calls Core’s pricing usage-based and quotes it per customer. A free Community licence runs 50 virtual users, and Professional and Core have free trials. No rupee price is published. TechBag sizes your peak users and bundles first, then quotes in INR with GST.
Best when tests and data must stay on your servers
Best for a broader rollout
Best for SaaS load from many cloud regions
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Tell us your requirements and current tools — we’ll model it against what you spend today.
Take this into your next vendor call — including ours.
One site running one test at a time (Professional), teams testing concurrently (Enterprise), or SaaS (Core)?
Which protocol bundles do your apps need — web, SAP GUI, Oracle E-Business, remote desktop? Each changes the quote.
What is your real peak in concurrent users, and how many days a year do you test at that peak?
Permanent, time-limited, or Virtual User Flex Days that last 24 hours from first run and lapse after a year?
Do you have JMeter, Gatling or Selenium scripts worth reusing, and will they run unchanged in your edition?
Must scripts and results stay in India? If so, self-host Professional or Enterprise, or get Core’s region in writing.
Has OpenText put its roadmap and support terms for this line in writing before you sign a multi-year term?
Does the quote list edition, bundles, user counts, add-ons such as AI Analysis, and support level, in INR with GST?
List your money-making journeys and peak users first, or let a TechBag advisor pick the edition and protocol bundles, run the first script on the free licence and get the quote itemised in INR.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.