Skip to main content

03 · Trademark

The brand exploration ran a designer-level similarity scan — not a formal legal clearance. This doc captures what was found, what we hedged, and what's still open.

This is not legal advice. Run the final mark and name through counsel before filing or external launch.

Headline finding — the V0 collision​

The V0 suffix in SecurityV0 has a non-trivial overlap with Vercel's v0 trademark — Vercel's AI-codegen product, registered with both the name and a wordmark. Vercel's brand guidelines explicitly forbid use of confusingly similar marks or product names.

We use V0 as a versioning / posture cue, not as an AI-tool name. Substantive misalignment with Vercel's product, but visual similarity amplifies the risk.

Voluntary hedges in the spec​

The brand spec encodes three voluntary hedges, all aimed at making the "this is a version, not a co-brand" reading unmistakable:

  1. Two-tone wordmark, always. Security solid + V0 demoted (one weight lighter, neutral color). Recoloring V0 to slate makes it look like a Vercel-v0 co-promotion. Forbidden — see 01 · Logo system.
  2. No [V0] or [v0] in the bracket mark. Putting v0 inside its own bracketed badge is precisely Vercel's wordmark format. The mark is locked to [S].
  3. No V-shaped icon paired with a 0. That silhouette reads as Vercel-adjacent at small sizes (favicon, sidebar). The chevron / notch / orbit explorations were dropped for this reason.

Findings — full set​

Captured from the v3 brand-research scan (2026-05-05). Severity is the scan's best estimate, not a legal verdict.

High risk​

The V0 suffix collides with Vercel's v0 trademark.

Vercel registers v0 as a trademark covering the name and logo. Their brand guidelines forbid use of confusingly similar marks or product names. SecurityV0 uses V0 as a versioning cue, not an AI tool, but the visual similarity amplifies the risk.

Affects: the wordmark (every SecurityV0 surface contains V0). Hedge: two-tone wordmark, never elevate V0 to the mark. Counsel review before filing.

The notch / chevron mark resembles Vercel's triangle.

A geometric V cut into a square reads as the same negative-space-triangle motif Vercel has owned since 2015. At favicon and sidebar sizes the resemblance is strong.

Affects: the dropped "F · Notch / chevron" exploration. Action taken: dropped from the mark candidate set.

Medium risk​

Orbit + V0 reads as "AI" branding.

Circle-with-tracking-dot motifs are heavily used by AI/agent products. Combined with V0, the impression skews "AI tool" when the product is a security platform.

Affects: the dropped "C · Orbit / V0 dot" exploration. Action taken: dropped from the mark candidate set.

Low risk​

Shields are saturated in security branding.

McAfee, Norton, Cloudflare-adjacent, hundreds of MSSPs use shield silhouettes. Not a legal conflict (the shape is generic), but a memorability problem — the mark blends into category noise.

Affects: the dropped "B · Shield" exploration. Action taken: dropped from the mark candidate set. The earlier feat/branding-shield direction was rejected here.

Bracket monograms are common in dev-tool branding.

Square brackets around a letter is a recognizable pattern (Bitbucket-era, dozens of CLI tools). No specific conflict, but the silhouette reads as "generic dev tool" before "security."

Affects: the adopted "A · Bracket monogram [S]" — our current direction. Hedge: the engineering register is the point. The brackets are part of the deterministic-product story, not decoration. Differentiation comes from voice, color discipline, and the surface contract — not the silhouette.

Safe — no close match​

Wordmark-only. A typographic-only mark avoids icon-collision risk entirely. Currently used as a fallback for dense surfaces (footers, body copy).

Stacked block. Two-layer block referencing the "posture / evidence" stack from the product itself. No close visual match in the security or dev-tool space. Held as a future option; not currently shipped.

Why we landed on [S]​

After ranking the safe directions, [S] bracket monogram was picked over the safer Wordmark-only and Stacked-block alternatives because:

  1. The brackets visually encode the engineering / deterministic register the product itself uses (path IDs, scanner output).
  2. It scales cleanly to favicon (16 px) and OS launcher (128 px) without redrawing.
  3. It survives the trademark hedge — the mark is [S], not [V0]. The V0 lives only in the wordmark, demoted.

The trade-off: the bracket monogram silhouette is generic in dev-tool branding (low risk above). We accept the trade-off because the engineering register is more important to the product story than silhouette uniqueness. The decision is recorded in DDR-001.

Sources reviewed​

  • vercel.com/geist/brands
  • brandfetch.com/v0.dev
  • industry surveys (Looka, DesignMantic, Wix coverage of security branding patterns)

This is a designer-level similarity scan, not a formal trademark search. Recommend formal clearance via counsel before filing or external launch.

Open​

  • Formal trademark search. Not yet run.
  • Counsel review of the SecurityV0 name itself. The V0 suffix is the dominant risk; an early read from counsel before the name appears on customer-facing contracts is prudent.
  • International filing strategy. Out of scope for this spec.

When any of those land, capture the result here (or move to decisions/ if it produces a binding choice).