NeoLoad
Enterprise-grade performance testing with codeless design and strong CI/CD integration. Best for teams that need professional tooling without scripting.
Overview
NeoLoad, created by Neotys in 2005 and now part of Tricentis, is an enterprise performance testing platform designed for teams that need professional load testing without deep scripting expertise. It offers both a codeless GUI for quick test creation and a script-based mode (JavaScript) for advanced scenarios. NeoLoad is particularly strong in CI/CD integration, with native plugins for Jenkins, GitLab CI, Azure DevOps, and more.
In 2026, NeoLoad is positioned as the enterprise alternative to open-source tools, offering professional support, advanced analytics, and governance features that large organisations require.
What it's used for
NeoLoad is the right choice when:
- Enterprise performance testing needed: Professional tool with support, SLAs, and governance.
- Codeless test creation preferred: GUI-based design with drag-and-drop scenario building.
- CI/CD integration is critical: Native plugins for all major CI platforms.
- Advanced analytics required: Detailed bottleneck analysis, root cause identification, and trend reporting.
Pros & Cons
Pros
- Codeless test design with optional scripting
- Excellent CI/CD integration
- Advanced bottleneck analysis and root cause identification
- Professional support and enterprise SLAs
- Strong SAP, Citrix, and legacy protocol support
Cons
- Expensive — enterprise licensing starts in the tens of thousands
- Resource-intensive controller infrastructure
- Learning curve for advanced features
- Smaller community than JMeter or k6
- Overkill for small teams or simple API load testing
Platforms & Integrations
NeoLoad runs on Windows, macOS, and Linux. It requires a controller machine and load generators. Cloud execution is available via NeoLoad Cloud.
Pricing
| Tier | Cost | Includes |
|---|---|---|
| Professional | Custom | GUI design, local execution, basic reporting |
| Enterprise | Custom | Distributed load, CI integration, advanced analytics, support |
| Cloud | Custom | On-demand cloud execution, pay-per-use pricing |
NZ Context
NeoLoad is used by a handful of large NZ enterprises with Tricentis contracts. For most NZ companies, the cost is prohibitive compared to k6 or JMeter. It is most commonly seen in NZ banking and telecommunications where enterprise support and governance are non-negotiable.
Alternatives
- JMeter — Free, open-source alternative with massive ecosystem.
- k6 — Developer-friendly and much cheaper for API load testing.
- LoadRunner — The traditional enterprise alternative from OpenText.
When to choose NeoLoad
A quick decision guide for NZ teams evaluating performance testing options.
| Choose NeoLoad when… | Choose something else when… | Combine with… |
|---|---|---|
| Your organisation already has a Tricentis contract and can bundle NeoLoad licensing into an existing enterprise agreement. | Your team is fewer than 10 engineers and load testing is occasional — k6 OSS or JMeter covers the need at zero cost. | Grafana + InfluxDB — stream NeoLoad metrics to a shared dashboard that developers, ops, and test leads all watch during a soak run. |
| Your protocols include SAP GUI, Citrix, or legacy thick-client applications that JMeter and k6 cannot record natively. | Your system is purely REST/GraphQL and your developers are comfortable writing JavaScript — k6 is faster to script, cheaper, and has better developer adoption. | Dynatrace or Datadog APM — correlate NeoLoad synthetic load with real back-end trace data to pinpoint which service degrades first under pressure. |
| You need formal governance — audit trails, role-based access, test versioning, and executive dashboards — for regulatory or compliance reasons (e.g., PCI-DSS, APRA CPS 234). | You need a quick proof-of-concept load test in the next 48 hours — the controller-and-generator infrastructure setup alone can take a day to configure correctly. | Tricentis Tosca — share test data and user-journey definitions across functional and performance suites when your organisation is already in the Tricentis ecosystem. |
| Your CI/CD pipeline runs performance gates on every release and you need a tool that integrates with Azure DevOps pipelines out of the box without custom scripting. | Budget is under $30k NZD per year — LoadRunner Cloud and NeoLoad Cloud licensing at this scale is difficult to justify when Gatling Enterprise or k6 Cloud cost a fraction of that. | Postman + Newman — use Postman to maintain the API contract tests and generate the request catalogue; import that catalogue into NeoLoad to build load scenarios without re-specifying endpoints. |
What I would do
Practitioner judgment on tool adoption, team onboarding, and when to swap.
If…
I was the lead performance tester at Harbour Bank and we had just signed a Tricentis enterprise agreement covering Tosca, qTest, and the option to add NeoLoad.
I would…
Add NeoLoad to the contract rather than running a parallel k6 capability — not because NeoLoad is technically superior for API load, but because consolidating tooling under a single vendor means one support contract, one audit trail, and one set of role-based access controls. In a regulated banking environment that operational simplicity is worth more than the scripting flexibility k6 gives you. I would then run a 90-day proof of value: pick the three highest-risk services (internet banking login, payment processing, statement generation), build baseline load profiles, and wire the NeoLoad CLI step into the Azure DevOps release pipeline so performance gates run on every deployment to production. If the gates are green for 90 days, the investment has justified itself.
If…
I was a QA engineer at TechServNZ working on a managed-services client whose legacy ERP runs on a Citrix-delivered interface and whose new digital channels are REST APIs.
I would…
Use NeoLoad specifically for the Citrix workloads — it is one of the only tools that can record and replay Citrix ICA protocol without a custom agent — and k6 for all the REST API load scenarios. Running two tools sounds like overhead, but it is actually cleaner than forcing NeoLoad to do everything: the k6 scripts live in the same Git repository as the application code, developers can run them locally in under a minute, and the results feed straight into a Grafana dashboard the whole team already uses. NeoLoad then becomes a specialist instrument for legacy protocol testing, which is exactly what it is best at. I would not try to replace k6 with NeoLoad just to have one tool.
If…
I was evaluating performance tools for Revenue NZ's next major tax-processing platform release, with a mandate to demonstrate we could handle end-of-year filing volumes before go-live.
I would…
Start by asking whether the procurement process allows a sole-source justification for NeoLoad or requires open tender. In the public sector that question often determines the answer. If we can justify it, NeoLoad's governance features — signed test reports, role-based run approvals, trend comparisons across releases — make the audit story much simpler when the CFO asks how we know the system won't fall over on 7 April. If we must tender, I would put JMeter Cloud on AWS alongside Dynatrace APM as the open-source stack, accept slightly more manual reporting work, and invest the licensing savings into a dedicated performance environment that mirrors production at 50% capacity. A realistic environment beats a premium tool running against an undersized test instance every time.
The bottom line: NeoLoad earns its cost when you have legacy protocols, a Tricentis ecosystem, or a regulatory audit trail requirement — in any other situation, the open-source alternatives will serve a NZ team better and the money saved buys you a realistic test environment, which matters more than the tool.
Interview questions
Questions you are likely to get if you list NeoLoad on your CV — with what interviewers are really testing for.
What is the difference between NeoLoad and k6, and when would you choose one over the other?
What they’re really testing: Whether you understand the tool’s positioning or just have it on your CV because a former employer used it.
Strong answer covers: NeoLoad’s codeless GUI and enterprise governance vs k6’s code-first, developer-owned approach; NeoLoad’s native support for Citrix/SAP protocols that k6 cannot handle; the cost and infrastructure overhead of NeoLoad making k6 the default for API-only load testing in most NZ teams.
When would you choose NeoLoad over LoadRunner for an enterprise performance testing programme?
What they’re really testing: Whether you can compare two expensive tools honestly rather than just defending whatever you have used.
Strong answer covers: NeoLoad’s stronger native CI/CD plugins (Jenkins, Azure DevOps, GitHub Actions) vs LoadRunner’s legacy strength in protocol breadth; Tricentis ecosystem bundling reducing per-seat cost if Tosca or qTest are already licensed; LoadRunner still winning on mainframe and legacy protocol depth in large NZ government deployments.
You’re joining TeleNZ as a performance test engineer. The team runs NeoLoad for load testing but has no performance gates in the CI pipeline. How would you approach changing that?
What they’re really testing: Whether you can drive tool adoption inside an existing organisation rather than just run scripts someone else wrote.
Strong answer covers: Starting with a single high-risk service (e.g. the customer portal login or billing API) to prove value before scaling; using the NeoLoad CLI plugin in the existing Azure DevOps or Jenkins pipeline to add a pass/fail step against a defined SLO baseline; documenting the baseline and getting sign-off from the engineering lead so the gate has authority, not just automation.
Your NeoLoad test runs cleanly on your local controller but consistently times out on the same scenario in the CI pipeline. How do you debug it?
What they’re really testing: Whether you know the infrastructure model NeoLoad uses and can reason about environment differences, not just re-run the test.
Strong answer covers: Checking load generator connectivity to the system under test (firewall rules, proxy settings, SSL certificate trust) since the CI agent and your laptop are on different networks; verifying the controller URL and project path are environment-variable-driven and not hard-coded to localhost; reviewing NeoLoad’s runtime logs on the CI agent for “LG disconnected” or “handshake failed” errors before looking at the application itself.
How would you structure a NeoLoad performance testing programme for a large-scale public-sector platform release — such as a new Revenue NZ filing system — where the test evidence needs to satisfy both an internal architecture review board and an external auditor?
What they’re really testing: Whether you understand how enterprise tooling serves governance and audit needs, not just technical load generation.
Strong answer covers: Defining SLOs upfront with business sign-off (e.g. 95th-percentile response under 3s at peak filing volume) so pass/fail criteria are objective; using NeoLoad’s signed PDF reports and trend comparison across releases as audit artefacts; running tests in a production-equivalent environment (minimum 50% capacity, same database volumes) and documenting environment limitations in the report; scheduling a soak test to surface memory leaks before go-live, not just a spike test.