Every platform. One execution engine.
LoadGen runs Citrix, AVD, Omnissa Horizon, RDS, web, and FAT-client targets on the same wizard family, the same agent fleet, and the same comparison view. Pick the platform — the engine adapts.
Platforms · Pick a Target
Same engine. Six platforms. Live wizard + agent strategy per target.
- ///StoreFront
- ///Gateway
- ///PNAgent
- ///External Login
Platforms Hub
Pick the platform. Land on the playbook.
Each platform ships with a dedicated cockpit, a measured before / after, and a feature map back into the engine. No two stacks are the same — but every one runs on the same code paths.
Citrix
Basic ICA + Enhanced HDX. StoreFront / Gateway / PNAgent / External Login auth, all on the same wizard.
/platforms/citrix
Azure Virtual Desktop
Native ARM discovery — Subscription, Resource Group, Host Pool authored in the wizard.
/platforms/avd
Omnissa Horizon
Connection Server, vCenter, resource-pool concurrency. Generic wizard with Omnissa / VMware support.
/platforms/vmware-horizon
Remote Desktop Services
RD Gateway, multi-session farms, slot saturation. Dedicated 8-step wizard.
/platforms/rds
Web Applications
Playwright on Core agents, plus SessionSight DEM, API flows, and uptime — one timeline.
/platforms/web-testing
FAT Client
Workload-based .lgs scripts on Full agents. Desktop apps tested without brittle UI macros.
/platforms/fat-client
Same engine. Six surfaces.
The engine adapts — the audit trail does not.
The same wizard family, agent fleet, cockpit, and audit log power every platform. Citrix HDX traces and AVD FSLogix profile-loads end up in the same comparison view — because they’re produced by the same code.
"Six platforms · one platform. Buy the engine once; apply it to whichever target the next quarter calls for."
Universal Platform Loop
Discover · Author · Execute · Validate.
The four motions every LoadGen platform shares — applied to Citrix, AVD, Horizon, RDS, Web, and FAT alike.
Discover
Native discovery for every target — ARM resources, StoreFront / Gateway URLs, Connection Server, RD Gateway, web targets. No CLI dance.
Author
Platform-specific or generic wizard authors the scenario shape — same JSON, same engine, same agents under the hood.
Execute
Right-sized agents (Core / Full / VDI) drive every workload. Activate, Reset, Kill, Logon, Logoff land per-session, not per-script.
Validate
Cross-platform comparison overlays — Citrix vs AVD, Horizon vs RDS, web vs API. Same evidence trail, same audit log.
One engine. Pick the target.
Start the trial. Run your first scenario on whichever platform is in front of you. Use the same install for the next five that come down the roadmap.
