Architecture options

NeoLoad Web is flexible: you can run it entirely in the cloud, entirely on your own infrastructure, or as a mix of both.

This topic explains the different deployment models and helps you choose the one that fits your requirements.

Deployment models

A NeoLoad environment has three components: the controller orchestrates tests, load generators simulate virtual users, and NeoLoad Web stores results, manages infrastructure, and provides dashboards for your team to analyze performance.

Where these components run depends on your deployment model. The following table compares the three deployment options:

Aspect

Cloud

On-premises

Hybrid

Who manages NeoLoad Web

Tricentis NeoLoad

You

Tricentis NeoLoad

Where do load generators run

Tricentis NeoLoad cloud

Your servers

Both

Where does NeoLoad store results

Tricentis NeoLoad cloud

Your database

Tricentis NeoLoad cloud

How it scales

Elastic: Add cloud load generators on demand

Fixed: Limited by your hardware

Elastic: Go to cloud when needed

Network requirements

Outbound HTTPS to Tricentis NeoLoad cloud

Internal only

Internal and outbound HTTPS

When to use

You want to start quickly with minimal infrastructure work, and your application is reachable from the internet.

Data residency rules require all test data to stay on your network, or your application lives in an air-gapped environment.

You need on-premises load generation but want cloud-based analytics. You can also add cloud load generators for large-scale tests.

What you need

A NeoLoad Web SaaS tenant, a server for the controller, outbound HTTPS on port 443, and an API access token.

Servers for the controller, load generators, and NeoLoad Web with a database backend.

A NeoLoad Web SaaS tenant, servers for the controller and on-premises load generators, and outbound HTTPS to the Tricentis NeoLoad cloud.

Choose your deployment model

If you're not sure where to start, go with cloud. It's the fastest way to get going, and you can always add on-premises components later.

What's next

Here's where to go after you've chosen your deployment model: