How to budget

The reward pool is
one part of the cost.

Hackrate's bug bounty service is quoted around your scope and the support you need. A useful proposal separates service fees from researcher rewards and makes any setup, payment or additional-work charges explicit.

Start with a planning period and the assets you want to include. Then account for the work your own team will do, especially remediation. A low volume of reports does not remove every operating cost.

YOUR PLANNING MODEL

Service fees + setup + researcher rewards + internal effort + agreed extras

Compare all items over the same period and confirm currency, taxes and payment terms.
01 / PLATFORM AND MANAGEMENT

The service that runs the program.

Budget for platform access and the management work included in your agreement. That can include report validation, researcher communication, coordination and reward administration.

Ask about service levels, report limits, included retesting and the price of additional work. Confirm which activities remain with your team.

02 / RESEARCHER REWARDS

Funding for qualifying discoveries.

Allocate a separate reward pool. Define eligible findings, impact and severity criteria, duplicate handling and approval responsibilities before research begins.

The pool is a funding plan. Actual payouts depend on qualifying submissions and the program rules; the amount does not promise a number of findings.

03 / SETUP AND ACCESS

The work before launch.

Scope definition, program rules, test accounts, access arrangements and integrations require preparation. Establish which setup tasks are included in the quote and which are charged separately.

Your team may need to prepare environments, explain workflows and coordinate with asset owners or technical providers.

04 / YOUR TEAM'S CAPACITY

Decisions, fixes and follow-through.

Plan time for technical questions, reward decisions and risk prioritization. Reserve engineering capacity for investigation, remediation and any agreed verification.

Managed triage can reduce raw report handling. It does not make your team's implementation work disappear.

See the customer responsibilities

What changes the cost?

Scope the program
before comparing quotes.

Asset complexity, access, participation, management coverage and the reward schedule all influence the budget. These three setups illustrate different cost drivers.

A FOCUSED PRIVATE LAUNCH

One product, deliberate invitations.

Start with a defined application and a manageable participation model. Preparation includes test accounts, researcher access and a named technical owner.

Budget around

Setup, management coverage, a separate reward allocation and the capacity to answer product questions.

Explore private programs

A BROADER ONGOING PROGRAM

More assets and technical owners.

Multiple products and wider participation can add coordination and validation work. Submission volume remains uncertain, even with a larger scope.

Budget around

Coverage across teams, escalation, report-handling capacity, reward funding and regular scope reviews.

Explore public participation

A SELF-MANAGED PROGRAM

Your team operates the workflow.

Your staff own the handling tasks assigned to them, such as validation and researcher communication. Platform and reward costs still need to be agreed.

Budget around

Internal expertise, availability, tools and continuity, alongside platform access and researcher rewards.

Explore self-managed programs

A worked planning example

Make the assumptions
visible.

This is a hypothetical 12-month budget exercise, not a Hackrate quote, a market benchmark or a recommended reward schedule. The amounts and hours below are chosen only to demonstrate the calculation. Replace them with your approved assumptions and proposal.

In this example, the team allocates €10,000 for rewards and assumes six hours of internal coordination per month at an internal cost of €80 per hour. Remediation work is budgeted separately.

STEP 01 / MODEL A REWARD ALLOCATION

One possible funding scenario.

4 medium findings × €500
€2,000
2 high findings × €1,500
€3,000
1 critical finding × €3,000
€3,000
Unallocated contingency
€2,000
Illustrative reward allocation
€10,000

This is a hypothetical mix, not a forecast of seven findings. Severity labels alone do not set a reward: eligibility, impact and program rules also matter. Unspent allocation is not the same as a paid reward.

STEP 02 / ADD THE OTHER BUDGET ITEMS

Build the annual view.

Reward allocation
€10,000
Coordination: 6 hours × €80 × 12 months
€5,760
Illustrative subtotal
€15,760
Platform and management fees
From quote
Any setup and agreed extras
From quote
Engineering remediation
Plan separately

€15,760 is not the full program price. Add the quoted fees, engineering budget and any applicable taxes. Internal hours represent a planning assumption, not a service commitment or a Hackrate charge.

Review commitments as well as payments.

Track paid rewards, approved but unpaid rewards and submissions awaiting decisions. Agree when to review funding, who can replenish it, and how changes to future scope or participation are communicated. Assess the workload after launch and revise your forecast using observed activity.

Prepare for a useful proposal

Bring the scope.
Ask for the breakdown.

A quote is easier to compare when it explains the work, limits and responsibilities behind the price. Give each provider the same requirements and compare the total planned cost over the same period.

Use the current solutions and pricing page to start a conversation about Hackrate's services. Confirm the final scope and commercial terms in your proposal.

What to bring.

  • The applications, APIs and other assets you control.
  • User roles, test-account needs and important workflows.
  • Your preferred private or public participation model.
  • The handling tasks you want Hackrate to manage.
  • Your planning period and proposed reward allocation.
  • The people who approve scope, rewards and fixes.

What the proposal should clarify.

  • Recurring fees, setup charges and contract duration.
  • Reward funding, approval, payments and any related fees.
  • Included validation, communication and escalation.
  • Report limits, additional work and retesting terms.
  • Currency, taxes, invoicing and treatment of unused reward funds.
  • How scope changes, budget reviews and renewal are handled.

Still deciding which service you need?

A managed VDP supports incoming disclosure handling, while a penetration test commissions a scoped assessment. Their budgets fund different work from a bug bounty program.

Compare bug bounty, pentesting and managed VDP

Frequently asked questions

The details worth agreeing.

Use these answers to prepare the conversation about your own scope and responsibilities.

How much does a Hackrate bug bounty program cost?

Hackrate bug bounty pricing depends on the scope and agreed service. Request a proposal that separates platform and management fees, any setup charges, reward funding and optional work. This guide does not publish a fixed package price or a market-average estimate. Its numerical example is a hypothetical planning exercise, not a Hackrate quote.

Are researcher rewards included in the management fee?

Treat researcher rewards as a separate budget item and confirm the arrangement in your proposal. Management or platform fees pay for the agreed service; rewards are paid for qualifying submissions under the program rules. Specify who approves rewards, how funds are provided and whether any payment-related charges apply.

Do we only pay when a valid vulnerability is found?

Qualifying bounty rewards follow the program's rules, but that does not make the entire engagement pay-per-finding. Platform access, management, setup or other agreed services can have their own fees even if no qualifying report arrives. Your team also spends time preparing scope, answering questions and handling remediation.

How should we choose the size of the reward pool?

Consider the assets, potential impact, research effort, participation model and reward schedule. Model several possible mixes of qualifying findings and keep a contingency within an approved budget. Review actual activity after launch. A pool is a funding plan, not a prediction of the number of vulnerabilities or a guarantee that researchers will participate.

Is a private bug bounty program always cheaper than a public one?

No. Private participation allows more deliberate invitations, while a public program can reach a broader researcher community. Total cost still depends on scope, rewards, activity and management arrangements. A focused private launch can help you learn about workload, but it does not guarantee lower costs or a fixed number of submissions.

What happens if the reward budget is nearly exhausted?

Agree the review, funding and communication process before launch. Monitor approved and pending rewards, and decide when to replenish funds or adjust future participation and scope. Handle reports submitted under existing rules according to those rules; a budget review should not silently change the terms for research already performed.

Can we start with managed VDP instead?

A managed VDP may fit when your immediate objective is to receive and handle disclosures. It does not provide the same service as commissioning active research through a bug bounty program. Choose the model based on the outcome you need, then compare its service fees, included handling and customer workload.

A practical next step

Turn your scope into a useful quote.

Share the assets, participation model, management support and planning period you have in mind. We can separate service costs, reward funding and customer responsibilities in the proposal.

Hackrate

Our platform helps companies to identify software vulnerabilities in a cost-efficient way. It provides a secure and centralized view of ethical hacking projects for your company.

US Patent Applied for HackGATE #63/645,845

Hackrate Status

Hackrate Ethical Hacking Platform |
2026 ©

CVE Program Numbering Authority