1
Get a license file
Black Hat Ethical Hacking issues a signed
.license file for your organization. One license can grant several modules at once (for example remediation for Synapse and pro for D0pam1ne Pro itself), each with its own end date, plus the team seats and the client companies allowed. So a single file can carry, say, Pro for a year and Synapse for six months.2
Upload it
An admin opens the Licensing page and uploads the file. The modules turn on the moment it verifies.
3
Renew when it ends
Each module locks on its own end date while the others keep working, and a new license replaces the one before it rather than stacking, so you re-issue a client a single up-to-date file. An admin can also remove a license at any time to lock a module again. Your remediation data is kept; only access pauses.
D0pam1ne Pro itself is gated the same way: a standard build is locked behind an activation screen until a license that grants the
pro module is installed, shown before onboarding.Verification is fully offline. The license carries an Ed25519 signature that is checked against a public key baked into the build, so a self-hosted install keeps working without ever reaching BHEH. There is no phone-home.
Seats and client users
- Team seats count your own provider-side accounts.
- Client companies is how many client organizations you can set up.
- Client end users a customer asks you to add under a paid company are free and never count against seats, because the client already paid for the project. You can give each one access to a whole project, a project group, or specific issues. See Clients and groups.