Security and data flow
Know what runs locally and what the platform stores.
Load Test Lab separates customer-controlled load generation from the cloud management workflow. This page describes the behavior visible in the current product architecture without making unverified compliance claims.
By Load Test Lab product team Reviewed by Kedros, a.s. Updated Product version 1.0.0
Agent
Configure the Load Test Lab Agent for the active team.
Team Agent
Customer-controlled load generator connection
Team Agent⌃
Preview of the current Load Test Lab interface. Example data only.
Execution remains customer controlled
JMeter and the Agent run on a host selected and operated by the customer. The customer controls the JMeter installation, working directory, load-generator capacity, and network path to the system under test.
The Agent uses team-specific credentials
The platform creates an Agent identity with a team-specific communication topic and credential. The application shows credential validity, warns before JWT expiration, and supports credential regeneration.
- Team-specific Agent identity
- Configurable JMeter home
- Configurable working directory
- JWT expiration and regeneration
Results are synchronized and stored
Result files and logs are uploaded to the platform. Load Test Lab also stores generated evaluation and comparison reports, file templates, and optional attachments. Downloads use temporary presigned links.
Application access is permission based
The backend enforces role permissions, active user and team status, and project membership on protected operations. Formal security, privacy, retention, and vendor-assessment requirements should be confirmed in the applicable agreements and current security documentation.
Put Load Test Lab into practice
Prove the value with a real test.
Start with the scripts and load generator your team already uses.