Connect a private datacenter

A private datacenter is a location you operate. Once you install the Maxoperf agent inside your network, tests can pick that location and generate load from there — useful for internal services, regulated environments, or any system that should not be reachable from the public internet.

The install path is the same whether you run the agent on a single Docker host or on a Kubernetes cluster.

Before you start

You need:

• A workspace where you can create a private datacenter.
• A Docker host or a Kubernetes cluster inside the network that can reach the target.
• Outbound HTTPS connectivity from that host to the Maxoperf service endpoints.

Register the datacenter

1. Open the workspace and switch to the Private datacenters tab.

   

   Private datacenters list — every PDC the workspace owns, with its status at a glance.

2. Click New private datacenter.

3. Give it a clear name like aws-us-east-internal or colo-rack-3 and a short description.

4. Pick the runtime — Docker for a single host or Kubernetes for a cluster.

5. Save. Maxoperf generates a one-time enrollment token and an install snippet.

Install the agent

1. Copy the install snippet from the console. It includes the enrollment token and the public service endpoints the agent needs to reach.

2. Run the snippet on the host or cluster you chose. The agent registers with Maxoperf using the one-time token, then exchanges it for a long-lived identity.

3. Watch the agent status on the private-datacenter page in the console. It moves from pending enrollment to running once the agent connects.

   

   Private datacenter detail page — the meta pill row shows current agent status; auto-update readiness and identity live below it.

Treat the enrollment token like a secret

The enrollment token is single-use and short-lived, but anyone with it can register an agent against your workspace until it expires. Do not paste it into shared chat channels or commit it to a repository.

Use the location in a test

Once the agent shows running, the location appears in the Locations dropdown when you create or edit a test. Pick it like any other location.

You can mix this location with managed cloud locations in the same test — for example, run 80% of the load from a managed region and 20% from your private location to compare.

Operate the agent

• Upgrade — the agent self-upgrades on a controlled schedule. You can opt out per agent if you need to pin a specific version.
• Pause — disabling the location stops new runs from being scheduled to it. Runs in progress continue to completion.
• Revoke — deleting the private datacenter removes the agent’s identity and forces a fresh enrollment if you want to bring it back.

Where to go next

• Managed and private load locations — when each kind of location is the right fit.
• Use case: private load generation — patterns from teams running production traffic from their own infrastructure.
• Run your first test — pick the new location during test creation.