Two solutions—On-Site Agent and On-Prem Load Injector—allow you to simulate real user load on internal environments behind firewalls or restricted networks.

On-Site Agent and On-Prem Load Injector software for load testing behind a firewall can be downloaded from the LoadView user interface via the Manage menu.

When to Choose What

On-Site Proxy

A lightweight proxy server resides inside your network, forwarding traffic from Dotcom‑Monitor’s cloud injectors to your internal app.

Choose On-Site Proxy if:

  • You want to test internal applications with cloud-based scalability.
  • Your app is behind a firewall but reachable via a proxy tunnel.
  • You prefer minimal local infrastructure setup.

To install and start load testing internal applications with On-Site Proxy, please follow the guideline provided in the LoadView On-Site Proxy Agent Installation article.

On‑Prem Load Injector

You install a self‑managed injector server directly inside your network, generating test traffic locally.

Choose On-Prem LoadView Injector if:

  • You cannot allow any external traffic to reach your app.
  • You need complete control over test traffic inside a secured environment.
  • Your test requires simulating ONLY local users from multiple internal endpoints.

Learn how to install and configure On-Prem Injector from the LoadView On-Prem Load Injector Installation & Configuration article.

On-Site Agent vs. On-Prem LoadView Injector

Feature / Capability On-Site Agent On-Prem Injector
Primary Use Case Load test internal apps using LoadView’s cloud injectors Load test internal apps using locally installed injectors
Load Traffic Origin Cloud-based injectors → On-Site Agent → target app Locally installed injector →target app
Public Network Dependency during testing Yes – LoadView cloud-based injectors initiate the test No – test stays fully within internal network
Typical Deployment Proxy server inside LAN Load injector server(s) inside LAN
Firewall Changes Allow proxy to establish outbound connection to LoadView Allow injectors to establish outbound connection to LoadView
Scaling Load Generation Cloud handles scaling Scaling by installing more local injectors
Best For Internal applications where load should still originate from the cloud, but needs to pass through the firewall Internal-only or isolated networks where traffic must remain 100% inside