Your API keys, authorization tokens, custom headers, and request payloads contain sensitive intellectual property. LoadTest is engineered from the ground up so that your confidential data is loaded into memory only during execution, scrubbed from disk the instant a test launches, and completely inaccessible to anyone—including us.
0 Days
Payload Retention
Purged from DB upon launch
256-bit
Tenant-Bound AEAD
AES-GCM with orgId HKDF
0 Access
Platform Blindness
Staff view only [REDACTED]
100%
Client E2EE Vault
WebCrypto zero-knowledge
Request Lifecycle
Follow how sensitive parameters, authentication headers, and request bodies move through LoadTest from your browser to ephemeral execution and automatic purge.
You configure your load test in the browser. When E2EE is enabled, your browser encrypts sensitive headers and body using WebCrypto PBKDF2 before sending over TLS 1.3.
Configurations at rest are sealed with AES-256-GCM using keys mathematically bound to your organization ID. No cross-tenant access is cryptographically possible.
The instant a test is dispatched to worker RAM, the database immediately purges the payload. Cold storage, backups, and disks contain zero sensitive request data.
Workers execute the load test strictly from volatile memory. When the run finishes, only aggregate latency percentiles and status codes are preserved. Worker RAM is wiped.
Security Pillars
Every component of LoadTest is architected to minimize data exposure, enforce cryptographic boundaries, and guarantee peace of mind for engineering teams.
Your payloads cease to exist the instant a test starts.
Traditional load testing platforms store request bodies, GraphQL queries, auth headers, and customer records permanently in their databases. LoadTest operates under a zero-retention model: the exact second a test is dispatched to worker memory, the backend immediately purges the payload and sensitive headers from the database. When the test completes, our database contains strictly aggregated performance statistics (latency percentiles, error rates, throughput). Zero payload trace remains on disk or in backups.
Cryptographically bound to your organization ID with AES-256-GCM.
We do not rely solely on software-level SQL WHERE clauses to separate customers. Every customer organization has its encryption keys mathematically derived using HKDF with the unique organization ID (orgId) as Authenticated Associated Data (AAD). If a malicious actor or compromised query somehow retrieved ciphertext belonging to your organization, it is cryptographically impossible to decrypt using any other tenant’s keys.
Even our platform engineers and administrators cannot view your data.
We follow a strict Zero-Access security model. Internal administrators, support personnel, and telemetry services have zero visibility into your target paths, Authorization headers, Bearer tokens, or request bodies. All internal administrative and telemetry inspection APIs automatically redact sensitive URLs and payloads to [REDACTED] before reaching any internal dashboard.
Client-side WebCrypto encryption. We cannot decrypt your templates even if subpoenaed.
For teams in banking, healthcare, fintech, or defense that require ultimate confidentiality, LoadTest offers an optional client-side End-to-End Encryption (E2EE) Vault. Before your test configuration ever leaves your browser, it is encrypted locally using the standard WebCrypto API (PBKDF2 with 100,000 rounds of SHA-256 and AES-256-GCM). Our servers store only sealed ciphertext (#sealed:e2ee:...). We never receive your passphrase and possess zero ability to decrypt your payload.
Keep enterprise load traffic completely isolated inside your private perimeter.
Enterprise workspaces can deploy private, dedicated load-testing agents. When a test is dispatched, LoadTest automatically routes the job exclusively to your designated workers. Your load generation traffic never shares compute resources or network interfaces with multi-tenant public workers.
Side-by-Side Comparison
See why enterprise security teams and compliance officers choose LoadTest over legacy load testing platforms.
| Security Capability | Traditional Platforms | LoadTest Zero-Trust |
|---|---|---|
| Request Body & Payload Storage | Saved indefinitely in databases, search clusters, and disk backups | Purged from DB immediately upon launch; executed strictly in volatile RAM |
| Auth Tokens & Bearer Headers | Often logged in plaintext or protected by generic database-wide keys | Protected by Tenant-Bound AEAD (AES-256-GCM) with organization HKDF context |
| Internal Staff & Admin Access | Support engineers and database admins can view full request payloads | Platform Admin Blindness: sensitive URLs and payloads are redacted to [REDACTED] |
| Client-Side Zero-Knowledge Vault | Unsupported; server has full access to all templates and secrets | Browser WebCrypto E2EE Vault (PBKDF2 100k + AES-GCM); server has zero access |
| Target Domain Authorization | Often permits arbitrary URL attacks or DDoS against third-party systems | Strict DNS TXT or HTTP token verification required before testing external hosts |
| Worker Fleet Isolation | Shared multi-tenant containers mixing requests from various accounts | Dedicated, private worker fleet routing scoped strictly to your organization |
Security & Compliance FAQ
Everything you need to know about our cryptographic model, data minimization, and audit compliance.
No. LoadTest implements a strict Zero-Retention execution policy. The exact second a load test starts, our backend executes a secure purge query that scrubs request bodies, custom headers, and sensitive query parameters from our database. Only aggregated statistics (such as p50, p95, p99 latency percentiles, requests per second, and HTTP status code counts) remain.
No. We enforce Platform Admin Blindness across our platform. Internal administration dashboards and telemetry APIs automatically redact target paths, authorization headers, and request bodies to [REDACTED]. Even with elevated backend privileges, our personnel cannot view your sensitive payloads.
Every cryptographic operation utilizes AES-256-GCM where encryption keys are derived via HKDF using your organization ID (orgId) as Authenticated Associated Data (AAD). Even in the hypothetical scenario of a raw database snapshot leak, ciphertext belonging to Organization A cannot be decrypted by Organization B.
The E2EE Vault is an optional zero-knowledge security layer built on the browser WebCrypto API. When saving a sensitive template, your browser generates an AES-256-GCM key from your personal passphrase using PBKDF2 (100,000 rounds of SHA-256). The plaintext never touches our servers—only the encrypted ciphertext is sent. If legally compelled or subpoenaed, LoadTest cannot decrypt your payload because we never receive your passphrase.
Our architecture is designed around the core compliance principle of Data Minimization. By eliminating persistent storage of request payloads, scrubbing sensitive data immediately upon execution, maintaining tenant-bound cryptographic boundaries, and providing cryptographic domain verification, LoadTest helps your security team satisfy stringent audit and compliance requirements.
Before any load test can be scheduled or dispatched against an external domain, the account holder must prove administrative ownership of the domain via a cryptographic DNS TXT record or an HTTP verification file hosted at /.well-known/. This strictly prevents malicious actors from using LoadTest for unauthorized stress testing or denial-of-service attempts.