beta mode
Business / Server setup guide

Connect your server in four steps.

Add your connection details, request approval and follow installation in My servers. Start using your resource once its status is Ready.

Setup journey · illustration, not your server’s live status

  1. 1. Add detailsAddress and SSH sign-in
  2. 2. Request approvalAdministrator review
  3. 3. InstallFollow progress in My servers
  4. 4. Ready to testChoose your approved resource

1. Add your server details

In My servers, choose Add server. Give it a recognizable name and enter its public IPv4 address. Use a Debian or Ubuntu server with Python 3, at least 2 GB available memory and 8 GB free disk. Root access is needed to install missing prerequisites.

2. Choose how to sign in

Enter the SSH username, then choose a password or private SSH key. Add the server identity public key from your provider console; this is different from your private sign-in key. The form includes instructions for finding it. Change the default SSH port of 22 under Advanced connection settings if needed.

3. Request approval

Review the maximum simulated users, confirm that you control the server and select Request setup. An administrator must review and approve installation. Approval is manual, with no guaranteed time. Keep My servers open to check the status, or contact support if you need help.

4. Follow installation

After approval, your server card shows installation progress and the latest setup message. Wait for Ready before selecting it for a test. If setup fails, check the displayed error, SSH access and available resources, then contact support for a retry.

Use your ready server

For website or API load tests, choose Start testing and select your server in Testing server. Select a verified website, set users and duration, then run the test. For databases, choose Connect database. Network tests need approved sending and receiving servers. Capacity and safety limits still apply.

Access and removal

Only the assigned account can select its server. LoadVM needs its connection address to manage setup. Connection credentials are encrypted at rest; detailed results appear in your account. To disconnect, open Connection details & removal. Cleanup removes LoadVM-owned components and saved credentials after success; shared prerequisites remain.