Skip to main content
The Hacktron Platform is the shared workspace for setting up Hacktron across your organization. Start here if you need to connect GitHub, choose which repositories Hacktron should review, manage access, or handle billing and pentests for the organization.

What you will see first

platform-integrations-dark

Most teams start in Integrations, then move through repositories, people, billing, and pentests as they roll Hacktron out.
When you first arrive, the path depends on how you got here:
  • If you are setting up a new organization, you will be asked whether you are here By myself or With my team.
  • Choose By myself if you want the individual path for the CLI and VS Code extension. Choose With my team if you want shared setup, collaboration, and pull request scanning.
  • If you were invited, you do not need to go through onboarding. You sign in or create an account, then join the organization directly.
  • If you arrived from hacktron login, you may need to sign in first and then continue from there.
If you choose With my team, GitHub is usually the main setup step. Slack is optional, and repository coverage can stay off until you are ready to turn it on.

Who the Platform is for

The Platform is for shared, organization-level work. It also connects directly to Workbench, because this is where seats and access are managed for the organization.
platform-persona-team-reference

Use the Platform for shared setup across the organization, including continuous code reviews across repositories, pentests, teammates, and centralised billing.
platform-persona-individual-reference

Use Workbench for work that happens directly in code. The CLI and the IDE extensions work alongside the Platform to provide security workflows in your terminal and editor.

Initial setup

One common way to get started is:
  1. Connect GitHub in Integrations
  2. Open Repositories and choose where Hacktron should run
  3. Use People to check who can access the organization and what role they have
  4. Use Billing if an owner needs to add payment information, manage seats, or buy credits
  5. Use Pentests when you want a larger scoped assessment

Pages overview

The Platform is split into a few key pages:
  • Integrations connects GitHub and other supporting tools
  • Repositories decides where Hacktron should actually run
  • People controls who has access
  • Billing manages seats, credits, and shared budgets
  • Pentests is for larger, scoped assessments beyond day-to-day review

Platform vs Workbench

Workbench is an integral part of the Platform, built for individual usage. Apart from providing access to Workbench, the Platform is used to manage:
  • repository coverage
  • people and roles
  • billing, seats, and credits
  • pentests and other org-level activity
Use Workbench when you are doing the work itself in code through the CLI or IDE. For example, someone might be invited through the Platform, assigned a Sec seat there, and then use that access and those credits in Workbench.