Skip to content
Dreadnode Dreadnode Dreadnode

Prerequisites

Log in with dn login and you are ready to run AI red teaming. Hosted models mean there are no API keys or compute to set up.

You can start AI red teaming with a single command. Log in with dn login and run attacks against Dreadnode-hosted models right away, with no API keys and no compute to configure. Everything else on this page is optional.

Log in

Section titled “Log in”

Authenticate with the platform so your results flow to your project dashboard:

Terminal window
dn login

This opens a browser, saves your credentials locally, and connects the CLI, TUI, and SDK to your account. Confirm it worked:

Terminal window
dn whoami

You should see your organization, workspace, and profile context.

Choose an organization

Section titled “Choose an organization”

If you belong to a single organization, you can skip this. dn login selects your default organization automatically.

If you belong to more than one, target a specific organization with --organization:

Terminal window
dn --organization <org-slug> --capability ai-red-teaming

You can also set it once with the DREADNODE_ORGANIZATION environment variable.

Pick a model

Section titled “Pick a model”

By default, use Dreadnode-hosted models. They are prefixed with dn/ and route through the Dreadnode proxy, so there are no provider API keys to manage.

Terminal window
dn --model dn/claude-opus-4-8 --capability ai-red-teaming

In the TUI, press Ctrl+K to browse the hosted models. On SaaS deployments, hosted inference is billed against your credits.

Bring your own keys

Section titled “Bring your own keys”

Prefer to use a provider account directly? Export the provider key in your shell before launching, then use that provider’s model string (for example openai/gpt-4o or anthropic/claude-sonnet-4-6). The TUI, CLI, and SDK pick up environment variables automatically.

Set up a workspace and project

Section titled “Set up a workspace and project”

Best practice: run one AI red teaming operation inside a single workspace and project. Every assessment, trace, and finding then lands in one place, and the Overview Dashboard and reports roll up into one coherent risk picture. Start a new project when you begin a new operation (a different target program, a new quarter) so each dashboard tells a clean story.

In the web UI

Section titled “In the web UI”
  1. Create the workspace (once per team or engagement): open Settings > Workspaces in your organization and add a workspace. Workspaces control access and isolate runtimes.
  2. Open the workspace and create a project from the project picker (New project). Give it a clear name, for example q2-safety-audit.
  3. Run every attack for that operation against this project so its findings aggregate together.

Creating a project needs workspace contributor access or higher. Each workspace also has a default project you can use to get started; the default project cannot be renamed or deleted.

In the TUI

Section titled “In the TUI”
  • The status bar (bottom left) shows your current workspace and project.
  • Press Ctrl+W to switch workspace.
  • Ask the agent to create and select a project: “Create a project called q2-safety-audit in the main workspace.” It sets your workspace and project context for the session.
  • Or set them at launch (also available as DREADNODE_ORGANIZATION / DREADNODE_WORKSPACE / DREADNODE_PROJECT):
Terminal window
dn --organization <org> --workspace <workspace> --project <project> \
  --model dn/claude-opus-4-8 --capability ai-red-teaming

Next steps

Section titled “Next steps”