Create a Debricked account

Create your Debricked account with ease. Follow this step-by-step guide to have your account up and running in no time.

In order to use our service, you need to create a Debricked account. Luckily, this is very easy to do. Simply navigate to our website and click on Start for Free or Log in.

Sign up with email​​​​​​​

Note that this will create a new company account. If you intend to join an existing company account, please contact your company admin.

To sign up using your email address:

  1. Fill in your email

  2. Read and accept the privacy policy and terms and conditions

  3. Fill in your details

  4. Set a secure password for your account

Sign up using GitHub SSO

You can also sign up using your GitHub account:

  1. Click the GitHub button on the Sign-up page

  2. Sign in using your GitHub credentials

  3. Next, you can either choose an organization to connect to, or continue without connecting to an organization. If your company/colleagues already use Debricked, join the existing organization. If you are the first collaborator to join or simply want to use our tool privately, continue without connecting to an organization.

  4. Choose the email address you want to use with your Debricked account and enter your information

  5. Add a password. You will only need it if you have admin rights. It will not be used for logging in via GitHub, but to access the admin pages. You can still use this password to log in if you use your email instead of GitHub SSO, so make sure to choose a secure password.

Admin Role

If you are the first collaborator in our organization to sign up or are not connected to an organization, you get admin rights. Please note that even if you sign up using SSO, we require a password for the admin interface, due to handling of sensitive information.

As an admin, you are allowed to:

  • Add, remove, or edit users

  • Manage access tokens

  • Change user permissions such as:

    • Allow SSO

    • Enforce comments when marking vulnerabilities as unaffected

    • Allow users to snooze vulnerability automations

Last updated