Creating your Blacksands account
Every Blacksands Cyber deployment — Broker, Bouncer, or Bursar — starts with the same three steps: create an account, verify your email, and create an organization. This article walks through each one.
1. Register with email and password
Head to the signup page and register with a work email address and a password. We recommend using a password manager to generate a strong, unique password; Blacksands does not currently support social sign-on, so this email and password combination is your account's primary credential until you provision certificate-based identities for your users and devices.
2. Verify your email
After registering, we send a verification link to the email address you provided. You must click this link before you can create an organization or select a plan. The link confirms that you own the mailbox and protects against typo-squatted or spoofed signups. If the email doesn't arrive within a few minutes, check your spam or quarantine folder — some corporate mail filters are aggressive about links in new-sender email. If it still hasn't arrived, see Contacting support.
3. Create your first organization
Once your email is verified, you'll be prompted to create your first organization. An organization is a slug-based namespace — for example, acme-manufacturing — that becomes the home for your users, devices, certificates, and billing. The slug you choose becomes part of internal routing and console URLs, so pick something short and stable; you can rename the organization's display name later, but the slug itself is not designed to change after resources are provisioned against it.
Creating an organization is what unlocks self-serve plan selection. Until an organization exists, there's nothing to attach a plan to — once it does, you'll move straight into Choosing a plan.
What happens behind the scenes
Account creation, email verification, and organization creation are independent, ordered steps by design — this is the same "no single system can grant access alone" philosophy that runs through the rest of the platform. A verified email proves identity ownership; an organization establishes a tenant boundary; only after both exist can billing, certificates, and access grants be issued. If you're setting this up on behalf of a company, we recommend using a shared or role-based email address (like it@yourcompany.com) as the organization owner rather than a single employee's personal work email, so ownership doesn't get orphaned if that person changes roles.
