What we do, in full

Accounts, organizations and access control, for security work.

Rasd is built for individuals who track their own practice and for security teams that need clear roles. This page describes the current release in full — including what is deliberately not built yet.

01 — Personal workspaces

One account, one personal workspace.

Registration creates one account and one personal workspace. You choose Red, Blue or Both for that workspace and can change the choice at any time in settings.

There is no registration verification email in this release, so the address you enter is not treated as proven. Access is enforced on the server, not by hiding links.

Red workspace Reserved for offensive and adversary emulation work. The page states its purpose and shows an empty state. No scan or operation has run.

Blue workspace Reserved for defensive and detection work. A configured operations console can be embedded here; no data is ingested by Rasd itself.

02 — Organization workspaces

Invite people, set a role, set Red or Blue access, organize teams.

Anyone without an organization can create one and becomes its owner. Each account belongs to at most one organization at a time.

Organization roles and what each one can do
Role	Administration	Teams	Ownership
Owner	Full control, including deletion	Create, edit, delete, assign members	Can transfer or delete
Admin	Settings, invitations, roles, access	Create, edit, delete, assign members	Cannot transfer or delete
Team leader	None	Edit the teams they lead	No
Member	None	View teams they belong to	No

Role and workspace access are independent. Managing an organization does not grant Red or Blue access by itself, and team membership never grants workspace access.

03 — Not in this release

Nothing here pretends to be built.

Operation tooling, scanning, integrations, chat, billing and registration email verification are deliberately out of scope. Future work is tracked in a separate backlog rather than promised here.

Create an account Sign in