How Perbug works

Both verticals — software bugs and AI failures/annotation — run through one escrow-backed pipeline. Money is funded before work starts and moves only on confirmation.

For clients

1
Create a project
Define scope and out-of-scope, attach assets (creds are envelope-encrypted at rest), and write the rules.
2
Set the bounty table
Price each severity explicitly. Fund escrow via Stripe — must cover at least 2× your highest bounty before you can publish.
3
Review submissions
An inbox sorted by severity. Confirm (set final severity), reject with a reason, mark duplicate (must link), or request info.
4
Pay automatically
Confirming reserves escrow and triggers a Stripe Connect payout within 24h. Unused escrow refunds on close.

For workers

1
Pass qualification
One-time test per vertical — a seeded buggy app for software, a gold-labeled sample set per annotation task type.
2
Claim work
Browse the board or accept an invite. Filter by platform, min bounty, tier, skills, and NDA status.
3
Submit clean
Structured repro, environment, evidence. We embed + dedup-check and quality-score before you submit.
4
Build reputation
Confirmed finds, severity-weighted earnings, gold accuracy, and dispute wins compound into your tier and unlock private programs.

Fair by construction

5-day SLA

If a client sits on a submission, it auto-escalates to a vetted triager — and the client is charged the triage fee.

Real disputes

Rejected? Dispute within 7 days. A triager arbitrates: upheld (0%), partial (25% default), or overturned (100%). 'Known issue' rejections require a pre-dated ticket.

Double-entry ledger

Every cent is two ledger rows. Debits always equal credits, and Stripe is reconciled nightly.

Get started See pricing