App Overview

App is the umbrella section for the product surfaces you use in Dreadnode.

Start here when you need one page that answers:

• which app surface should I use first?
• how do org, workspace, and project context affect everything else?
• what does the hosted project surface actually look like once I am inside Studio?
• where do Hub, evaluations, optimization, Agents, training, worlds, compute, and admin controls fit?

For agents and automation, this is the shortest useful app map: what the major surfaces are, which context scopes them, and where to look next depending on the workflow.

Context hierarchy

Most questions reduce to this chain:

Organization
  -> Workspace
     -> Project
        -> Execution resources

Layer	What it is for	What it is not
Organization	top-level tenant, membership, billing, and plan boundary	not the day-to-day work bucket
Workspace	primary access boundary for a team, engagement, or personal area	not the billing boundary
Project	grouping context for related work inside a workspace	not a permission boundary
Execution resources	tasks, runtimes, sandboxes, evaluations, training jobs, worlds resources, traces, and sessions	not org or workspace administration

Studio project surface

The hosted day-to-day work surface is the Studio route:

/{org}/studio/{workspace}/{project}

That route is the project shell for interactive work. In the current frontend it does three jobs:

• keep project chat and composer anchored to the current org, workspace, and project
• resolve the project key to a real project ID so sandbox and runtime state can hydrate correctly
• open project-side panels for Files, Summary, and Runtime

If you open Studio without a fully qualified project URL, the app resolves one for you:

• /{org}/studio picks the default or first accessible workspace, then redirects to the most recently updated project in that workspace
• /{org}/studio/{workspace} resolves the most recently updated project in that workspace, falling back to the default project key if necessary

That makes Studio project-first in practice, even though permissions and billing still come from the surrounding workspace and organization.

Surface map

Surface	What it is for	First stop
Studio project surface	run interactive project work, inspect files, review summaries, and manage runtime state	Projects
Hub	browse and manage shared registries	Hub
Evaluations	run judged repeatable benchmark jobs	Evaluations
Optimization	improve capabilities against pinned datasets and promote results	Optimization
Agents	inspect deployed agent traffic, query telemetry, and analyze traces	Agents
Training	run hosted SFT and RL jobs	Training
Worlds	generate manifests and trajectories for security environments	Worlds
AI Red Teaming	organize assessment campaigns and reporting	AI Red Teaming
Compute	manage the runtime and sandbox execution model	Compute
Account	understand boundaries, settings, projects, credentials, and billing	Account

Context layers

Organization

Use the organization layer when you care about:

• members, invitations, teams, and top-level ownership
• credits and billing in SaaS mode
• org-scoped shared registries like capabilities, security tasks, datasets, and models

For the detailed organization rules, use Organizations.

Workspace

Use the workspace layer when you care about:

• who can access a body of work
• which projects belong together
• workspace-specific permissions and storage credentials

For the access-control and sharing rules, use Workspaces.

Project

Use the project layer when you care about:

• the Studio URL and active project shell you are working in
• grouping the project’s runtime, sessions, evaluations, and traces
• choosing the default context for a workflow
• separating one engagement, benchmark suite, or experiment from another inside the same workspace

For the grouping and default-context rules, use Projects.

How this maps to the app

The frontend groups the product into Hub, Lab, Operations, Compute, and Manage. Studio sits across those areas as the project-level workspace where interactive work begins. The docs use one App section, but the ordering below mirrors that product flow where it matches directly.

Product area	Docs pages
Studio	Projects for the project route, chat shell, Files, Summary, and Runtime panels
workspace context	organization, workspace, and project model on this page and in Account
Hub	Hub with Capabilities, Security Tasks, Datasets, and Models
Lab	Evaluations, Optimization, Worlds, and Training
Operations	AI Red Teaming and Agents
Compute	Compute with Runtimes and Sandboxes
Manage	Account, Settings, Secrets, Credits, User administration