Partners

Testing under your name.

For dev agencies and freelancers: QA, security testing, performance testing and compliance readiness, delivered under your name. You keep the client. We do the work.

What we do for you

  • Release QA on your builds, with a defect list your developers can act on without a call.
  • Security testing of what you ship: web apps, APIs, mobile.
  • Performance and load testing before your client’s launch.
  • Compliance readiness for the questionnaires your clients receive.

How it works

  1. You keep the client and the relationship.
  2. We sign an NDA.
  3. We agree the scope, and your branding for the report.
  4. We deliver, to you or beside you on the call.
  5. You resell at your price.

Pricing

Partner pricing is quoted per engagement, under NDA. We do not publish it.

The report, under your name

The same sample report, with your mark where ours sits and your studio in the page footer. The content is the redacted sample; nothing in it is a real client.

Confidential

Sample report, redacted

  • Application security assessment
  • Sample, no client
  • Scope: customer web app and public API
  • Testing window: 1 to 12 September 2026
  • Issued 15 September 2026

Version 1.1, after retest

Severity scale

  • Info
  • Low
  • Medium
  • High
  • Critical

The same five stops as the stress map on the object.

BF-0914-03

Insecure direct object reference on the orders endpoint

Severity
HighCVSS 3.1 base score 7.1, vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Status
Fixed and retested
Summary

Any signed-in customer can read any other customer’s order, including name, phone number and delivery address, by changing the numeric id in the URL. Order ids are sequential, so the whole order history can be enumerated.

Steps to reproduce
  1. Sign in as a test customer and place an order. Note the order id in the confirmation URL.
  2. Request the order via the API with the test customer’s token. The response is correct.
  3. Change the id to the previous number and repeat the request with the same token.
  4. The response returns another customer’s order with personal data.
Evidence
GET /api/v1/orders/48212 HTTP/1.1
Host: api.redacted.in
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.redacted
Accept: application/json

Request made with the test customer’s token. Order 48212 belongs to a different account.

Impact

Personal data of every customer is readable by any other customer. Under the DPDP Act this is a reportable personal data breach. The sequential ids make bulk extraction a one-line script.

Fix

Scope the lookup to the signed-in customer and return 404 when the order is not theirs, so the endpoint does not confirm that an id exists. Add an authorisation test to the API suite so the check cannot regress.

// before
const order = await orders.findById(req.params.id);
if (!order) return res.status(404).end();
return res.json(order);
Retest

Retested on 18 September 2026. Requests for other customers’ orders now return 404 with an empty body. The authorisation test runs in CI on every pull request. Status: fixed.

Your studio, under your namePage 7 of 14

Partner enquiry

Partner enquiry

For example SaaS startups, fintech, e-commerce, your own products.

Roughly how many releases, apps or tests a month.

We use this only to reply. How we treat your data.

Send us a URL