Docs

Documentation

A practical guide to getting started with domain verification, load testing profiles, live metrics, workspaces, and templates.

Getting started
Sign in, confirm that your Default workspace exists, verify a target domain if you plan to test an external host, and launch your first run from the dashboard.
  • Create or confirm a workspace context
  • Register and verify a domain for external targets
  • Start a run from New Test or execute a saved template
Target domain verification
To prevent unauthorized traffic against third-party systems, external hosts require domain verification before any load test can be scheduled or executed.
  • DNS TXT Verification: Add the designated TXT token to your domain DNS records.
  • HTTP Token Verification: Place a temporary verification token file at your /.well-known/ endpoint.
  • Localhost exception: Local addresses (localhost, 127.0.0.1) are permitted for local MVP testing.
Load testing profiles and real-time metrics
Configure your test profile based on concurrent Virtual Users (VUs) or target Requests Per Second (RPS). Live streaming charts monitor latency and throughput.
  • Virtual Users (VU): Simulates concurrent client connections maintaining active sessions.
  • Requests Per Second (RPS): Generates a sustained request rate to benchmark backend throughput.
  • Latency percentiles: p50, p95, and p99 metrics highlight tail latency spikes rather than misleading averages.
  • Error analysis: Immediate breakdown of HTTP 4xx, 5xx, and network timeout rates.
Workspaces and reusable templates
Organize performance engineering across projects and teams without re-entering parameters for every release candidate.
  • Save complex headers, payloads, and ramp schedules as reusable templates.
  • Compare current run metrics against baseline runs to spot performance regressions.
  • Invite teammates to shared workspaces with role-based access control.
API access
API and automation support are part of the roadmap. The product UI already reflects those upcoming capabilities, but paid automation access is not publicly enabled yet.