Everything breaks.We build it and break it first.

A young studio that builds software, then does its worst to it: load it, probe it, break it, fix it, prove it. Your customers and your attackers get what survives.

0 %At rest100 %Broken

It breaks at 100 %. The retest loads the repaired part to 140 %.

The load that broke itHolds

What we build

Before anything can break

Web apps, mobile apps and the backends behind them, from a one-page scope to launch. Built by people who spend the rest of the week breaking software, so testing is designed in, not bolted on at the end.

What we build: the bracket at this stage of the testWhat we build: the bracket at this stage of the test

What we load

Before the release

We push traffic past your best day and run every release candidate through exploratory and regression passes. The limits show up here, on our clock, not on launch day.

What we load: the bracket at this stage of the testWhat we load: the bracket at this stage of the test

What we probe

Before the breach

Penetration testing of web, API, mobile and cloud, the way an attacker would do it, then a hard look at the code and architecture behind them. The next hole is usually a design decision.

What we probe: the bracket at this stage of the testWhat we probe: the bracket at this stage of the test

What we report

Before the incident

One finding per page: what we did, what we saw, what it means, how to fix it. Severity on the five-stop scale you see on this object. Nothing inflated, nothing buried.

What we report: the bracket at this stage of the testWhat we report: the bracket at this stage of the test

How we fix and retest

Before it ships

We stay for the fix, review the change, load it again past the original and show you it holds.

How we fix and retest: the bracket at this stage of the testHow we fix and retest: the bracket at this stage of the test

Services

We build it, then we break it. Either way you end with proof: a launch with a test report behind it, or a report you can act on and a retest that shows the fix held.

Send us a URL and we will tell you what we would test.

Name the system, add a line about what worries you if you like, and a person replies within one working day with what we would test first and how.

Send us a URL and we will tell you what we would test.

A staging or production address, or a repository.

Optional. What it is, or what keeps you up at night.

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

Starter engagements

Five ways to start small, each with a written scope, a fixed timeline and a price you can see before you talk to us.

Starter checks from ₹4,999

Launch pricing for our first ten clients: 10 places left.

  • Launch pricing, 10 places left

    Starter check

    Start here

    Launch price ₹4,999List price ₹9,999

    Fixed price. Request it through the form, no call needed.

    Who it is for
    A founder who wants a first look at the one thing that must not break: login, checkout, the payments API.
    Scope
    One critical flow or one API area, tested the way an attacker and a careful tester would.
    Typical duration
    3 working days
    What you get
    • A 5 to 8 page report with evidence and fixes
    • A 30-minute walkthrough call with your engineers
    • One retest within 30 days of the report
    Not covered
    Anything outside the one flow or area you name. Source-code review. Load testing.

All five starter engagements, with prices and what is not covered

Be one of our first three clients.

A tightly scoped check on one critical flow, for the first clients who help us get the studio right. You get the full report and a retest; we get told the truth.

3 of 3 places left.

How the programme works

What you get
A tightly scoped check on one critical flow, for example login and signup, checkout, or one API, delivered in 3 to 5 working days, free or up to ₹5,000, with the full report and a retest.
What we ask in return
  • Honest feedback on the work and on how we worked.
  • A short testimonial, if you are happy with the result.
  • Permission to publish an anonymised case study.
  • Two introductions to people who might need us.
Scope and terms
One flow. A fixed number of days. Signed rules of engagement and a written scope. Nothing outside that is tested. Read the rules of engagement, opens in a new tab.

Apply for a place

The deliverables

A new studio has no client logos. It has reports. Here are four pages from four kinds of engagement, redacted: a security finding, a QA defect, a load test and a launch handover.

Open the sample reports (PDF), opens in a new tabAll four, the same content as on this page, as one file you can forward.

Templates, free to use

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.

breakfirst.devPage 7 of 14

How an engagement runs

One sequence, in order. No phases named after planets; the durations are what they usually take.

How a development project runs

A full testing engagement. Scope to signed-off retest is usually four to eight weeks; a Starter check runs in three working days.

  1. Scope and rules of engagement

    Two days

    We agree targets, test windows, test accounts, data handling and who to call if something breaks in production.

  2. Threat model

    Two to three days

    We map what you have, who would attack it and where the value sits. It decides where the testing time goes.

  3. Test

    One to three weeks

    Manual testing with evidence captured as we go. You hear about critical findings the same day, not in the report.

  4. Report and walkthrough call

    Three days after testing ends60 min

    Written findings with fixes, then a sixty-minute call with your engineers to go through each one (thirty minutes for a Starter check).

  5. Retest

    Within thirty days, included30 days

    We verify each fix, update the status in the report and sign it off.

Book a scoping call

Tell us what you are building, or what keeps you up at night. Within one working day a person replies with questions and a next step.

What the call covers

  1. What you are building, or what needs testing, and why now.
  2. What is in scope and what is not: systems, environments, data.
  3. Test windows, accounts, access and who to call if something breaks.
  4. What you get back, in what form, and when.
Book a scoping call

Optional. A staging URL or a repository link helps us scope faster.

Optional. Customer, admin, support, and so on.

Optional. For example Next.js, Django, Postgres, AWS.

Optional. A date, or a release name.

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

Or write to hello@breakfirst.dev

Send us a URL