Free for non-commercial use under AGPL-3.0 with additional terms; commercial use needs a paid license.
First released
2022
Last verified
Answer
LPS (Load, Performance and Stress) is a .NET 8 global tool installed with `dotnet tool install --global lps` and driven entirely by a YAML file, so scenarios need no scripting or code. Tests are structured as rounds of iterations executed by virtual clients, with iteration modes shaping request timing to mimic steady users or bursts.
About
LPS (Load, Performance and Stress) is a .NET 8 global tool installed with `dotnet tool install --global lps` and driven entirely by a YAML file, so scenarios need no scripting or code. Tests are structured as rounds of iterations executed by virtual clients, with iteration modes shaping request timing to mimic steady users or bursts, and declarative helper methods generating random values, counters, and timestamps. Runs can be spread across nodes in a master-slave topology while a real-time dashboard tracks metrics, and a watchdog throttles tests before the generating machine saturates. SkipIf expressions branch at runtime, termination rules stop a run on sustained errors, and failure criteria act as post-run quality gates on error rate and percentiles.
Best for
API and protocol throughput or latency campaigns
Teams that want a free tier before committing to paid capacity
Groups comfortable scripting in YAML
Not the best fit when
Teams unwilling to operate generators, results storage, and scaling
Architecture and concurrency
LPS Tool is commonly operated as self-hosted software with scenario authoring in YAML. Concurrency and distribution depend on how you size workers or injectors.
Specs
Scripting
YAML
Protocols
HTTPHTTPS
Operating systems
WindowsmacOSLinux
Tags
dotnetyamlclidistributed
CATALOG LAST VERIFIED · 2026-08-12
Frequently asked
ANSWER-SHAPED
Who is LPS Tool for?
LPS Tool is best for engineers focused on API and protocol-level throughput and latency. It offers a freemium path, so teams can start small before buying capacity. Vendor: Mohamad Haidar. Deployment model: self-hosted. Free for non-commercial use under AGPL-3.0 with additional terms; commercial use needs a paid license.
How does LPS Tool differ from Artillery?
Compared with Artillery, LPS Tool is freemium while Artillery is open source; scripting centers on YAML rather than JavaScript, TypeScript. LPS Tool lists protocols HTTP, HTTPS; Artillery lists HTTP, HTTPS, WebSocket, Socket.IO, MQTT. 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 LPS Tool use?
LPS Tool uses YAML for scripting or scenario definition. Runtime model: protocol-oriented virtual users configured through the product workflow. OS support: Windows, macOS, Linux. Protocols: HTTP, HTTPS. 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 LPS Tool?
LPS Tool is primarily self-hosted; teams typically run generators on their own machines, CI runners, or private cloud. Plan for generator capacity, network access to targets, and result storage yourself. Pricing model: Free for non-commercial use under AGPL-3.0 with additional terms; commercial use needs a paid license.
What are known limitations of LPS Tool?
LPS Tool limitations to weigh: self-hosted tools require you to provision, scale, and observe load generators yourself. Status: active. Always validate against your target protocols and scale with a proof-of-concept. Confirm details against the official site and a short proof-of-concept in your environment.