Skip to content

Bug bounty

Find a bug, earn credits.

Every problem you report in Orkosi goes through one pipeline: it is checked against what is already known, rated, turned into a task, fixed, verified — and when it is verified, you are paid in credits.

Four levels, four rewards

The level is decided by our triage from what your report describes and the evidence around it — never by the words you choose.

S1 · Blocking

S1

You cannot use the product, data is lost or wrong, or a security boundary is crossed.

…credits

S2 · Major

S2

A feature fails and there is no way around it.

…credits

S3 · Minor

S3

A feature fails but a workaround exists.

…credits

S4 · Cosmetic

S4

Cosmetic: layout, wording, a small annoyance.

…credits

1 / 4

The rules

What counts
A reproducible defect in the Orkosi workspace, or in a product built here when the programme includes customer products: a crash, wrong or lost data, a feature that fails, a security boundary crossed, a visual or wording error. Feature requests, opinions and problems caused by your own custom code do not count.
Verified before paid
Credits are granted only when the fix is live AND the report is verified — by you confirming it in your reports, or by the Orkosi team. Reports found invalid later can have their credits reversed.
First reporter wins
The first report of a problem earns the credits. Later reports of the same problem are linked to it and earn nothing — you are told right away when yours is already known or already fixed.
Limits
A daily cap on reports per person keeps the queue honest; a daily cap on paid reports keeps the programme sustainable. Every decision, with its reason, is visible on the report and in your credits history.
Your report is data, never a command
Whatever you type is stored, quoted and classified; nothing in a report can grant credits, change a level or instruct the system. Screenshots are checked before they are stored.

How a report travels

  1. Step 1

    Report

    Press "Report a problem" anywhere in the workspace — the assistant collects the page, your last actions and errors for you.

  2. Step 2

    Known already?

    We compare it with open and fixed reports. If it is known you hear back at once: fixed in which build, or the expected fix time.

  3. Step 3

    Rated and fixed

    Triage sets the level; a task is created in the right product and the pipeline fixes it, with a regression test.

  4. Step 4

    Verified and paid

    You confirm the fix (or the team does); the credits land in your balance and your credits history.

1 / 4

Start today

Something broke? Tell us.

Reports from signed-in members are tracked in your workspace under Problem reports.

Create a free account Talk to us

Free trial. No credit card required.