WEBDIVE BRAND SYSTEM · VERSION 1.0

Technical depth.
Clear evidence.

WebDive helps development teams inspect what a web journey actually loaded, used, and cost. The identity combines engineering precision with the momentum of going beneath the surface.

IDENTITY

Logo system

The angled container represents a downward dive through layers of application behavior. The W is intentionally compact and structural.

Clear space

Keep at least one mark-width of clear space around the full lockup. Do not crowd it with navigation, partner logos, or borders.

Minimum size

Use the full lockup at 120 px wide or larger. Below that size, use the standalone mark at no less than 24 px.

Do not alter

Do not stretch, rotate, outline, add shadows, recolor the amber mark, or place the dark wordmark on insufficient contrast.

COLOR

Signal over decoration

The palette reflects an established developer tool: deep technical surfaces, neutral workspaces, and amber used only for attention and identity.

Deep Navy

#172033

Headers, primary type, dark surfaces

Signal Blue

#2463D4

Actions, selected states, links

Dive Amber

#F59E0B

Brand mark, attention, identity rule

Workspace

#EEF2F7

Application and document backgrounds

Slate

#667085

Supporting copy and metadata

Risk Red

#D92D20

High priority and destructive actions

TYPOGRAPHY

System-native and direct.

Use the operating system’s UI sans-serif stack for product and web surfaces. Use a system monospace stack for filenames, formulas, protocol commands, and measured values. This avoids external font requests and keeps the product local-first.

Go beneath the bundle.Resource analysis for real application journeys.blocking = max(0, task − 50ms)
VOICE

Precise, calm, useful.

  • Lead with evidence. State what was measured before recommending action.
  • Name uncertainty. Use “attributed,” “estimated,” and “during this journey” where appropriate.
  • Avoid drama. Prefer “High priority” to “Critical disaster.”
  • Make action concrete. Point to the resource, metric, impact, and next investigation.
MESSAGING

Positioning and approved language

PRIMARY TAGLINE

Go beneath the bundle.

DESCRIPTOR

Local journey performance analysis for Chrome DevTools.

VALUE PROPOSITION

Connect loaded resources to coverage, CPU, long tasks, rendering work, and original modules without sending application data to a backend.

PRIVACY STATEMENT

Captured application data stays in the extension. WebDive has no analytics or hosted analysis service.

Use

  • Measured during this journey
  • URL-attributed sampled CPU
  • Optimization opportunity
  • Local run history

Avoid

  • Guaranteed performance gain
  • Definitely safe to delete
  • Complete causal attribution
  • Anonymous or magical “AI insights”
COMPANY PRESENTATION

How WebDive should appear publicly

Product screenshots

Use real measurements or clearly label illustrative data. Show enough browser context to establish that WebDive is a DevTools product, while removing confidential URLs and source.

Privacy claims

Say “no backend” and “data stays in the extension.” Do not imply that source-map requests are offline; WebDive may request a map declared by an inspected script.

Company boilerplate

WebDive builds local-first developer tooling that turns browser telemetry into specific, explainable performance evidence.