Pre-launch beta — HTTP load tests from the dashboard

Create, run, and monitor HTTP load testsfrom one dashboard

Sign in, compose a request or paste curl / Postman on Home, set duration, ramp-up, and target RPS, then start a test. The run page polls every 3 seconds through pending, provisioned, and running — then a report with latency, throughput, and HTTP outcomes, including PDF export. A request wallet on your plan holds quota until the run settles.

Start free →
Home · composer
Paste curl / Postman
GEThttps://api.example.com/v2/users
Scenario name
Fetch user profile
ParamsHeadersBody
page1
limit50
80
Hold 2,400 / 3,000 remainingWallet check passed
Compose
Home builder, curl, or Postman
Live
Polled events every 3 seconds
Report
Latency, throughput, PDF
Wallet
Hold duration × RPS until settle

Core capabilities

A dashboard for creating, running, and monitoring HTTP load tests

Compose a request, start a run, follow the status-history timeline, then read the report — auth, wallet, billing, and workspaces included. Load generators run in the cloud; nothing to install.

HTTP request builder

Home is the composer plus run history. Set method, URL, query params, headers, and a JSON body — or paste curl / Postman and we fill the form. GET, POST, PUT, PATCH, and DELETE are supported.

Detailed test reports

When a run finishes, the page polls the report until it is ready: request summary, HTTP 2xx–5xx, timeouts, throughput vs target RPS, and latency percentiles (p50–p99). Download the same numbers as a PDF.

Live run and event timeline

The run page does not use websockets. It polls every 3 seconds: pending, provisioned, running, then completed, failed, or stopped. Status history covers created, resources, testing, report, and terminal events. Stop a live run from the same page.

Personal and company workspaces

Sign-up creates a personal workspace. Upgrade to a company to invite, promote, remove, or transfer ownership between Owner, Admin, and Member. Organization appears in the nav only for company workspaces. Tests, wallet, and subscription stay scoped to the current org.

Sessions and account security

Sign-in keeps an access token in memory and an HttpOnly refresh cookie. Settings lists devices so you can revoke one session, revoke the others, or log out. Change password signs out every session.

Load configuration

Set duration, ramp-up, and target RPS (capped by your plan). Before start, the dashboard checks remaining wallet requests — duration × RPS. If quota is short, the run does not start.

Nav · 12.4k remaining

Request wallet and billing

Quota is allotted, available, held, and used on the workspace. Remaining requests also sit in the dashboard nav as a quota chip, next to notifications, so you see usage before you start. Starting a test places a hold until the run settles. Owners and admins check out with Razorpay — apply now, queue after the current period, or cancel an in-flight checkout.

Email and Google sign-in

Register with email or continue with Google. Verify your inbox, reset a forgotten password, and change password from Settings. Logged-in users who open login or register are sent to the dashboard; verify, reset, and forgot stay reachable.

Test history on the dashboard

Home doubles as your composer and run history — build a request or open a past run without leaving the page. Inbox notifications are a separate list: mark one or all read. They are not the test lifecycle timeline.

How it works

From Home composer to a polled run, then a report you can download

01

Sign in — personal workspace ready

Register with email or Google. We create a personal workspace so you can test immediately. Verify email from Settings if needed. Logged-in users skip login and land on Home.

02

Compose on Home

Home is the request builder plus run history and quota cards. Paste curl or Postman, or set method, URL, query, headers, and JSON body.

03

Start with a wallet hold

Set duration, ramp-up, and target RPS. The app checks remaining requests (duration × RPS). If quota is short, start is blocked. Otherwise the backend places a hold until the run settles, then opens the run page.

04

Poll live events, then the report

The run page polls every 3 seconds through pending, provisioned, and running. Follow created → resources → testing → report events, stop if needed, then download a PDF.

Live run

Follow events while the test executes

The run page does not use websockets. It polls every 3 seconds: pending, provisioned, running, then completed, failed, or stopped. Status history is grouped into created, resources, testing, and report — plus failed or stopped. Live metrics tick on the same page; stop a run while it is still live.

  • Pending → provisioned → running → completed or failed
  • Event timeline plus live totals, success, failures, and RPS — with a 3s poll countdown
  • Stop from the run page while the test is still live
GET /v2/users
100 req/s · 30s duration · ramp 5s
Created
  1. Created
    request_created
  2. Resources
    resources_ready
  3. Testing
    testing_in_progress
  4. Report
    report_generating
Total
0
Success
0
Failed
0
Avg time
0 ms
Throughput96 RPS
Logs / response
200142msGET /v2/users
200156msGET /v2/users
200201msGET /v2/users
200138msGET /v2/users

Test reports

See how the endpoint behaved under the load you chose

When live status becomes completed or failed, polling switches to the report until it is ready. You get request summary, throughput vs target RPS, error mix, and latency tails — including successful vs failed groups — then PDF export.

  • Request summary: counts, 2xx–5xx, timeouts, and transport errors
  • Throughput vs the target RPS you configured
  • Latency p50, p95, p99 for all, successful, and failed requests
  • Polling continues until the report is ready or failed — it does not spin forever
  • Download the same report as a PDF from the run page
GET /v2/users
100 req/s · 30s duration · ramp 5s
Completed
0%
Success
0.0%
P95
0ms
Avg RPS
0
P95 latency
0ms
Average RPS
0
Success rate
0.0%
Peak throughput
0.0 MB/s
HTTP 5xx
0.0%
p99 latency
0ms
How to read this
Success rate is high, but p95 and p99 are elevated versus p50. Compare successful vs failed latency groups on the run page, then download the PDF. If report generation fails, polling still finishes with a failed status — the run is not left spinning.

Workspaces

Start personal. Upgrade to a company when you need a team.

You get a personal workspace at sign-up. Upgrade from Settings — or invite someone, which also converts the workspace — to share tests, reports, and the request wallet. Tests, wallet, and subscription stay scoped to the current organization. The Organization nav item only shows for company workspaces.

Personal workspace

Created automatically at sign-up. Rename it in Settings. Run tests and keep the request wallet to yourself until you are ready for a team.

Upgrade to company

Owner-only, one-way. Enter a company name in Settings — or invite someone, which also converts the workspace. Organization then appears in the sidebar. You can stay the only member.

Invite and roles

Owner and Admin invite by email as Admin or Member. Teammates accept from the invite link. Owner can transfer ownership; leaving restores your personal workspace.

Shared wallet and billing

Company tests, wallet, and subscription are one org-scoped pool — allotted, available, held, and used. Members can view balance; Owner and Admin manage plans and Razorpay checkout.

Acme Corp
Company workspace · Owner, Admin, Member
Active
JD
Jane Doe
jane@acme.com
Owner
MK
Mike Kim
mike@acme.com
Admin
SR
Sara Reyes
sara@acme.com
Member
Shared
Team tests
3
Roles
Wallet
Team wallet

Security & access

Manage signed-in devices from Settings

Sign-in uses an access token in memory and an HttpOnly refresh cookie. Each browser gets a device id. Revoke a session you do not recognize, log out every other device, or sign out entirely — which clears the token and cached data.

Active sessions

MacBook Pro · Chrome

Current

This device · Now

iPhone · Safari

Active

Signed in · 2h ago

Windows · Firefox

Active

Signed in · 3d ago

Linux · Chrome

Active

Signed in · 1w ago

Pricing

Four plans for the request wallet

Free, Starter, Growth, and Scale. Quota is allotted, available, held, and used on the workspace; company teams share one pool. Owners and admins check out with Razorpay — apply now, queue a plan after the current period, or cancel an in-flight checkout. Wallet also shows the ledger, open holds, and payment history.Each plan caps requests / month, max RPS, test duration, history, and team size. Target RPS on a run is capped by the current plan.

Pricing is shown in your local currency. We detect your market (US or India) from timezone and locale, then load that catalog.

Loading subscription plans