1. The short version
You may use this platform to send load at infrastructure you own or are contractually authorised to test, and at nothing else. The DNS verification step is the mechanism that enforces this, and it is not negotiable, waivable or removable. If you cannot complete verification for a target, you may not test that target, whatever permission you believe you have.
You pay for plans that bundle runs, run minutes and a traffic ceiling. We bill the plan monthly in advance and overage per minute after the fact, at the published rate. You can cap overage at zero, and we recommend you do until you understand your usage. Verification, reports and the audit log are included in every plan.
We do not promise that a run will find anything interesting, that your service will survive the traffic, or that a passing result means your system is safe. A load test is a measurement, and measurements have error bars. If that framing is not acceptable, the platform is not the right tool for the job.
2. Accounts and eligibility
You need an account with a working email address and, where the law requires it, the legal capacity to enter a contract. Accounts are for named individuals and teams; you may invite colleagues, and you remain responsible for every run started from the account, including runs started by an invited colleague at 02:00 while you were asleep. Seat-level activity is logged for exactly this reason.
You must be at least eighteen years old to hold an account. If you are accepting these terms for an employer, you confirm that you may bind that employer, and the employer is the contracting party. If you are an agency testing on a client's behalf, the client's authorisation is your problem to document. Our verification is a control, not a substitute for your professional obligation.
We may refuse, suspend or close an account where a run appears designed to target a third party, where verification evidence looks manufactured, or where a payment instrument is disputed without contact. Suspension for a verification or abuse reason is immediate and does not require a cure period; everything else gets written notice and seven days.
3. Verification and authorised targets
A target is authorised for your account only after the DNS TXT record we issue resolves to the expected token from our resolvers and matches the exact hostname you entered. The check runs again when a run starts, and a failure at that moment refuses the run. Authorisation covers the hostname, not the IP address it resolves to, and not other hostnames on the same certificate, server or CDN.
You agree not to attempt to verify a target you do not control by any other route: no borrowed tokens, no DNS rebinding, no wildcard games, no asking a colleague at the target company to "just add this record" without telling them what it is for. Where we find that a target was authorised dishonestly, we terminate the account and may report the conduct to the relevant provider or authority.
Verification records are yours to remove. Remove them when an engagement ends; if you leave them, you are leaving a standing authorisation tied to your account, and you accept the consequences of that choice. Rotating the token invalidates the old record and requires a fresh check before the next run.
4. Runs, ceilings and fair use
A plan sets a monthly run count, a maximum window per run and a traffic ceiling. The ceiling is enforced before a run starts and is not a target. Runs are queued on shared infrastructure; where a plan includes priority queueing, the priority applies to start time, not to the ceiling or the duration. We may reschedule a run where infrastructure maintenance would make the measurement unreliable, and you will be told before the window opens where possible.
You may not use runs to probe a target's defences for exploitation, to test a competitor's resilience, to demonstrate an attack for a client who has not authorised the target, or to generate traffic for any purpose other than measuring capacity. Runs must carry a maintenance note describing the test; a note that says "test" is not a note, and repeated empty notes are a signal we take seriously.
We may throttle, stop or refuse any run that threatens the stability of the platform or a third-party network, including a run whose traffic pattern we did not anticipate. Where a run is stopped for this reason, the run minute is not charged. Where a run is stopped because of a mistake in your configuration, the run minute is charged and a credit may be issued at our discretion.
5. Fees, taxes and renewal
Plan fees are billed monthly in advance and are exclusive of VAT, sales tax and any withholding a jurisdiction imposes. Overage is billed monthly in arrears at the rate published on the pricing page on the day the minute was consumed. Prices may change with thirty days' notice before your next renewal; a price change never applies retroactively to a period you have already paid for.
Plans renew automatically until cancelled. Cancellation from the dashboard takes effect at the end of the paid period, and the account keeps read access to reports during that period. Failed payments get a seven-day grace period and a written reminder; after that the account is suspended and runs stop.
Refunds follow the policy on the pricing page: fourteen days and zero consumed run minutes. Chargebacks filed without contacting support first may result in immediate suspension while the dispute is open. We would rather fix a billing mistake than argue about one.
6. Data, reports and confidentiality
You keep ownership of the configuration, the reports and the verification records tied to your account. We keep them for ninety days after a run and may keep billing records for the period the tax law requires. Reports may be used in aggregate, with identifiers removed, to improve the platform; they are never sold and never published with a customer name attached without written permission.
We treat your target list and your run schedule as confidential. Support staff see them only when resolving a ticket, and access is logged. If you need a data processing agreement for a client engagement, ask; we will sign a reasonable one, and we will not use the request as an upsell.
You are responsible for the lawful basis on which you process any personal data that appears in a test payload. Do not put real customer records into a load test, in production or in staging. A report is easier to share when it contains synthetic data, and the habit also keeps you out of a breach notification.
7. Availability, warranty and liability
The platform is provided as it is. We target 99.5% monthly availability for the scheduler and do not warrant a specific result, a specific ceiling under all network conditions, or that a run will complete if your target or its upstream path fails. Planned maintenance is announced on the status page and excluded from the availability figure.
To the maximum extent the law allows, our aggregate liability for any claim arising from the service is limited to the fees you paid in the three months before the event. We are not liable for lost profits, lost data, business interruption or the cost of substitute testing. Nothing in these terms excludes liability that cannot lawfully be excluded, and nothing here limits your obligation not to send traffic at a target you do not control.
You indemnify us against third-party claims arising from your use of the platform in breach of these terms, including a claim brought by the operator of a target you tested without authority. That indemnity is the commercial mirror of the verification rule: we build the control, you take responsibility for the target.
8. Changes and governing law
We may update these terms; material changes are announced by email at least fourteen days before they take effect, and continued use after that date is acceptance. If you do not accept a change, cancel before it takes effect and we will refund any unused, prepaid run minutes on a pro-rata basis.
These terms are governed by the laws of the jurisdiction in which the operating entity is registered, without regard to conflict-of-law rules. Disputes go to the courts of that jurisdiction, except where consumer law gives you a mandatory forum closer to home. Before filing anything, write to [email protected]; most disagreements are a billing line and a reply.
If a clause is found unenforceable, the rest survives. These terms, the pricing page and the acceptable use policy are the whole agreement about the service, and they replace anything said in a sales call. A statement in a chat window does not amend them.