Every flaw has a price

Bounty per validated finding

A pentest where you only pay for validated findings. Set your profile, read the price, print a practice invoice. The grid is indicative; it is frozen in the contract.

01 / Your grid

Organisation size
Renown
Tested scope
Size
x 1
Renown
x 1
Scope
x 1
Your multiplier
x 1
Illustration: the mass of the stack follows the amount.

A validated critical finding is worth up to

from €3,000

€7,500

Indicative grid, frozen in the contract signed before the first test.

Request a pentest

02 / The grid

Four levels, one price each

Each validated finding lands in a level according to its CVSS score. The level sets the range, the score places the amount inside it.

  • low

    CVSS 0.1 to 3.9

    €100 to €250

  • medium

    CVSS 4 to 6.9

    €300 to €900

  • high

    CVSS 7 to 8.9

    €1,000 to €2,500

  • critical

    CVSS 9 to 10

    €3,000 to €7,500

Indicative grid, frozen in the contract. Bars follow a logarithmic scale of the maximum, so critical does not flatten the rest.

03 / The score

A score, not an opinion

Eight switches, like a test bench. The score depends only on the vector: it sets the severity, then the amount inside the range.

We use CVSS 3.1, not 4.0: 3.1 is computed by an exact public formula you can check by hand. 4.0 relies on lookup tables. The score depends on the vector alone, not on our opinion.

CVSS 3.1 base score

9.8

criticalband 9 to 10

Bounty on your grid

€6,600

Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Typical examples: illustrations, not findings.

AV Attack vector
AC Complexity
PR Privileges required
UI User interaction
S Scope
C Confidentiality
I Integrity
A Availability

04 / The invoice

Your invoice, line by line

Choose how many findings of each level are validated, add a mission cap (30 days, adjustable) if you like. The receipt prints.

Simulation based on the midpoint of each range of your grid. Fictional example, not a quote: a real finding is paid according to its CVSS score.

Number of validated findings
low2
medium1
high1
critical0

Leave empty for no cap.

┌────────────────────────────────────┐
│ GAMEON  SIMULATED INVOICE          │
│ FICTIONAL EXAMPLE, NOT A QUOTE     │
├────────────────────────────────────┤
│ 2 x low             €175      €350 │
│ 1 x medium          €600      €600 │
│ 1 x high          €1,750    €1,750 │
├────────────────────────────────────┤
│ Subtotal                    €2,700 │
├────────────────────────────────────┤
│ TOTAL BILLED                €2,700 │
└────────────────────────────────────┘
 \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

05 / For your management

One page to pass around

Your profile, your grid and the mechanics on one A4 page. Nothing is sent and nothing appears in the page address.

06 / The rules

What is paid, what is not

Written before the first test, no hidden clause.

  1. Triage

    You have 5 business days to triage each report. No answer past that deadline: the finding is accepted, as the contract states.

  2. Duplicates

    A finding already known is paid, unless you show a dated ticket that predates our report. One root cause across several endpoints earns a single bounty.

  3. Severity disagreement

    It is settled on the CVSS vector: we discuss each metric, not an adjective.

  4. Mission cap (30 days, adjustable)

    Cap reached: testing pauses, nothing is billed above it, and you decide whether to raise it.

  5. Declined mandate

    We may decline a mandate after the scoping call.

  6. Non-eligible classes

    These observations are not paid, because they show no demonstrated impact.

    • Missing headers without demonstrated impact
    • Version disclosure
    • Self-XSS
    • Unexploited scanner output
    • Missing rate limiting without impact
    • SPF or DMARC alone

Your pentest, paid per flaw.

Indicative grid, frozen in the contract. Reply within 2 business days, from a person.