Pre-launch beta — HTTP load tests from the dashboard

Create, run, and monitor HTTP load testsfrom one dashboard

250RPS

Free test

60 seconds of real traffic on your API. No credit card needed.

Each free test is capped at 250 requests per second and 60 seconds
No credit card — verify your email and start
The target domain does not have to be verified inside that cap
One active test at a time: pending, provisioned, or running
After it completes or fails, the next test can start. Paid plans are unchanged

Start free →

Free test

250 RPS · 60s

GEThttps://api.example.com/v1/health

0 sent · 0 failedReady

Total time

0.0s

RPS

—

Requests

Success

—

Avg latency

—

p50

—

Min —Max —HTTP 200 0Failed 0

Requests each secondtarget 250 RPS

Free

250 RPS · 60s · no card

Compose

New test, curl, or Postman

Live

One active test on free

Report

Latency, throughput, PDF

Core capabilities

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

Verify your email, start a free test at up to 250 RPS for 60 seconds, follow the status-history timeline, then read the report. Verify a domain when you need a higher cap. Load generators run in the cloud; nothing to install.

HTTP request builder

New test is the composer. 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. Dashboard is an overview; Tests is history.

Load configuration

Set duration, ramp-up, and target RPS. The free plan caps each test at 250 RPS and 60 seconds, and allows one active test (pending, provisioned, or running). Starting another while one is open is rejected until that test completes or fails. Paid plans keep their own caps. Before start, the dashboard checks remaining requests — duration × RPS.

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.

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.

Nav · 12.4k remaining

Plan and usage

Quota is allotted, available, held, and used on the workspace. Remaining requests sit in the nav as a quota chip, next to notifications. Starting a test places a hold until the run settles. Owners and admins check out on Plan with Razorpay — apply now, queue after the current period, or cancel an in-flight checkout. Usage shows the ledger and open holds.

Workspace · MCP keys

MCP for agents and CI

Owners and admins create a key on MCP keys. Clients that can set headers send X-Access-Key and X-Secret-Key. Clients that cannot, including Claude connectors, use the same keys on the URL: /mcp?access_key=…&secret_key=…. The secret is shown once. Quota, domain rules, and plan caps stay the same.

How it works

From a free account to New test, a polled run, then a report you can download

Sign in — no credit card

Register with email or Google. We create a personal workspace on the free plan. Verify your email before the first test. Logged-in users skip login and land on Dashboard.

Start inside the free cap

Paste curl or Postman, or set method, URL, query, headers, and JSON body. Free tests stay at or below 250 RPS and 60 seconds without a verified domain. One test can be pending, provisioned, or running. If quota is short (duration × RPS), start is blocked.

Verify a domain to go higher

Above 250 RPS or 60 seconds, prove ownership with DNS TXT or an HTTP file, on a plan that allows that load. Paid plans are not limited to one active test. Tests may target that host or a subdomain.

Poll live events, then the report

The run page polls every 3 seconds through pending, provisioned, and running. When the test completes or fails, a free workspace can start the next one. Download a PDF of the report.

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

Created
request_created
Resources
resources_ready
Testing
testing_in_progress
Report
report_generating

Total

Success

Failed

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

Success

0.0%

P95

0ms

Avg RPS

P95 latency

0ms

Average RPS

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 Account — or invite someone, which also converts the workspace — to share tests, reports, domains, and request quota. Tests, Usage, and Plan stay scoped to the current organization. The Organization nav item only shows for company workspaces.

Personal workspace

Created automatically at sign-up on the free plan. Rename it in Account. Run tests inside 250 RPS and 60 seconds without a verified domain, and keep request quota to yourself until you are ready for a team.

Upgrade to company

Owner-only, one-way. Enter a company name in Account — 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 quota and billing

Company tests, domains, and subscription are one org-scoped pool — allotted, available, held, and used. Members can view usage; Owner and Admin manage Plan and Razorpay checkout. Companies can verify up to ten domains.

Acme Corp

Company workspace · Owner, Admin, Member

Active

Jane Doe

jane@acme.com

Owner

Mike Kim

mike@acme.com

Admin

Sara Reyes

sara@acme.com

Member

Shared

Team tests

Roles

Quota

Shared plan

Security & access

Manage signed-in devices from Account

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

Device	Status	Last active	Actions
MacBook Pro · Chrome	This device	Now	—
iPhone · Safari	Signed in	2h ago
Windows · Firefox	Signed in	3d ago
Linux · Chrome	Signed in	1w ago

MCP

Run the same load test from an MCP client

The dashboard stays the place you compose and watch a run. Owners and admins can also hand a key to Claude or another MCP client. The client calls Loadcurl’s /mcp endpoint. There is no CLI to install.

Create a named key that expires in 1–365 days. The secret is shown once.
Send X-Access-Key and X-Secret-Key when the client supports custom headers.
Otherwise paste the connector link: /mcp?access_key=…&secret_key=…
The client runs run_test, polls get_test_status, then reads get_test_report.
An organization can keep 20 keys that are not revoked. Revoke a key to cut a client off.

loadcurl

Headers, or the keys on the URL

Active

Custom headers

{
  "mcpServers": {
    "loadcurl": {
      "url": "https://<api-origin>/mcp",
      "headers": {
        "X-Access-Key": "lcak_…",
        "X-Secret-Key": "lcsk_…"
      }
    }
  }
}

No custom headers

https://<api-origin>/mcp?access_key=lcak_…&secret_key=lcsk_…

run_testget_test_statusget_test_reportlist_testsstop_testget_test_limits

Pricing

Four plans for monthly request quota

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 on Plan with Razorpay — apply now, queue a plan after the current period, or cancel an in-flight checkout. Usage shows the ledger, open holds, and payment history.Free starts at 250 RPS and 60 seconds per test, with one active test at a time and no credit card. Paid plans keep their own RPS, duration, and concurrency. Confirm live numbers in the dashboard.

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