Skip to main content
Hackrate creates your organization and initial security program during onboarding. You do not need to create either one in the platform. Use this guide to prepare the details Hackrate needs, access your workspace, review the program, and get ready for reports. If Hackrate has already invited you, start with the Access your organization step below.

​
What to prepare

Bring the following to your onboarding conversation. You can refine the details with Hackrate before launch.
  • Your company name and the email address of your security lead
  • The service you want to run: managed bug bounty, managed VDP, or PTaaS
  • The assets researchers may test, any exclusions, and testing restrictions
  • Your response team and the person who can approve program decisions
  • A reward budget and payout preferences if you plan to offer bounties
  • Your preferred launch timing and whether the program should be public or private

​
Onboarding steps

1

Contact Hackrate

Request a demo to start onboarding. Tell Hackrate what you want to test and what kind of researcher engagement you need. If you are already in contact with the team, continue with your Hackrate contact.
2

Plan your program together

Agree on the service type, initial scope, testing rules, researcher access, and launch timing. For a bug bounty program, also agree on rewards and budget. Hackrate uses these decisions to prepare your organization and program.
3

Access your organization

Hackrate creates the organization and initial program, then arranges access for your team. Follow the invitation instructions to register or sign in with the invited email address.After signing in, open Organizations and My Programs to confirm that the organization and program are visible. If they are missing, contact your Hackrate onboarding contact. You cannot add a new organization or program yourself.
4

Review the program configuration

Check the program name, description, policy, targets and exclusions, testing windows, and public or private visibility. If rewards are enabled, review the bounty table and budget. Send corrections to Hackrate or update fields available to your assigned role.
Be specific about out-of-scope assets and restricted testing. Researchers rely on these boundaries when deciding what they may test.
5

Prepare your response team

Confirm who will review reports and who can make program decisions. If your role allows it, invite teammates, set notification preferences, and connect any integrations your team needs.
6

Confirm the launch with Hackrate

Review the final scope, policy, researcher access, and rewards with the Hackrate team. Agree on when the program will become active and how researchers will be invited or informed. Hackrate coordinates the launch with you.
7

Handle your first report

New submissions appear in your report inbox. Review the finding, work with Hackrate’s managed triage team, respond to the researcher where needed, and track remediation. Use analytics to follow report activity and reward spending.

​
What to do next

Account setup

Review access, invite your team, and set notification preferences.

Program overview

Understand program settings, visibility, and lifecycle states.

Targets and scope

Review the assets researchers can test and the boundaries they must respect.

Report triage

Learn how to review, discuss, and resolve incoming findings.