Question 1

What is Loadcurl?

Accepted Answer

Loadcurl is a dashboard for creating, running, and monitoring HTTP load tests. You sign in at app.loadcurl.com, 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 — no websockets — through pending, provisioned, and running. When it finishes you get a report with latency, throughput, and HTTP outcomes, plus PDF export. Usage is gated by a request wallet on your subscription plan.

Question 2

Who is Loadcurl for?

Accepted Answer

Engineers and teams who want to load test an HTTP API from the browser — no workers or CLI to install. Start on a personal workspace, then upgrade to a company when you need to share tests, wallet quota, and billing.

Question 3

How do I run my first load test?

Accepted Answer

Register (email or Google), open Home — the composer plus run history and quota cards — fill the request or paste curl / Postman, set duration, ramp-up, and target RPS, then start. The app checks remaining wallet requests (duration × RPS) first. If quota is short, the run does not start. Only test systems you own or have permission to test.

Question 4

Do I need to install anything?

Accepted Answer

No. Use the web dashboard. There is no CLI or CI/CD integration in the current product.

Question 5

What can I test?

Accepted Answer

HTTP endpoints with GET, POST, PUT, PATCH, or DELETE. Add query params, headers, and a JSON object body. GraphQL can be sent as HTTP if you set the right URL, headers, and body — there is no separate gRPC or WebSocket tester yet.

Question 6

Can I chain multiple endpoints?

Accepted Answer

Not yet. Each test is one HTTP request repeated under your load profile.

Question 7

What is in the test report?

Accepted Answer

Request counts, HTTP 2xx–5xx, timeouts, success rates, throughput vs target RPS, and latency percentiles (p50–p99), including groups for successful vs failed requests. After live status becomes completed or failed, the run page polls the report until it is ready. Open the run from history and download a PDF. There is no public share link or A–F grade.

Question 8

Does the run page use websockets?

Accepted Answer

No. The run page polls every 3 seconds: live status while the test is pending, provisioned, or running, then the report endpoint after it finishes. Status history covers created, resources, testing, report, and terminal events (failed or stopped). If a history row has not arrived yet, the UI still shows a synthesized step such as "Preparing your test…" or "Test in progress…".

Question 9

How do I manage my account from the dashboard?

Accepted Answer

Home is the composer plus run history. Open a run for the event timeline, live metrics, and the report. Billing and Wallet cover plans, Razorpay checkout, and request quota (allotted, available, held, used) plus ledger, holds, and payments. Profile, Settings, sessions, and in-app notifications are in the same dashboard. Organization appears in the nav only for company workspaces.

Question 10

Are in-app notifications the same as run events?

Accepted Answer

No. The run page shows a status-history timeline for that test (created, resources, testing, report, or failed/stopped). In-app notifications are a separate inbox — list, mark one read, or mark all read — not a generic event bus for load tests.

Question 11

Do I need to create an organization?

Accepted Answer

No. Sign-up creates a personal workspace. Upgrade to a company from Settings when you want teammates. Inviting someone also converts personal to company. The change is one-way.

Question 12

What roles exist?

Accepted Answer

Owner, Admin, and Member. Owner and Admin invite as Admin or Member, manage members, and start Razorpay checkout. Members run tests and can view wallet balance. Invitees accept from the email link. Owner cannot leave until they transfer ownership.

Question 13

Is there a free plan?

Accepted Answer

Yes. You can start without a credit card. Billing lists plans for your market (US or India). Target RPS is capped by the current plan. Owners and admins check out with Razorpay; if a paid period is still active, a new plan can be queued instead of applied immediately. You can also cancel an in-flight checkout or activate a scheduled plan.

Question 14

How does the request wallet work?

Accepted Answer

The wallet is request quota on the current organization: allotted, available, held, and used. Starting a test places a hold of duration × RPS until the run settles — subscription, ledger, and holds refresh at that point. If you do not have enough remaining requests, start is blocked. Personal quota stays in that workspace; a company shares one pool. Wallet also shows the ledger, open holds, and payment history.

Question 15

Is it safe to load test production?

Accepted Answer

Traffic is real. Prefer staging, use a modest RPS, and set a ramp-up. You are responsible for testing systems you are allowed to test.

Question 16

How are sessions stored?

Accepted Answer

Sign-in uses an HttpOnly refresh cookie and an access token in memory. A device id is stored in the browser. Settings → Sessions lists devices so you can revoke one, revoke the others, or log out. Logout clears the token and cached dashboard data. Change password signs out every session.

Question 17

How does Loadcurl handle request credentials?

Accepted Answer

Headers and bodies you enter are stored to run the test and build the report. Data is sent over TLS. Prefer staging tokens. See the Privacy Policy for account, workspace, and session data.

Frequently asked questions

Getting started

Testing & dashboard

Workspaces & pricing

Security & data

Still have questions?