Not Jenkins, Not Actions, Not a Gradient Dashboard

What this means for you

Sparki is positioned against four specific patterns, not against a vague “legacy CI” strawman. Each rejection is structural: it would change the product to copy any of them, so the product does not.

The pitch

Not Jenkins or TeamCity, because the dense gray table and modal-heavy flow is the baseline being retired. Not GitHub Actions, because the YAML editor and run list is exactly what users are escaping. Not a generic SaaS dashboard with gradient blobs and big-number heroes. Not a mascot-driven toy.

Who it’s for

The seller, marketer, or founder who gets the “how is this different from GitHub Actions” question and needs four crisp comparisons that hold up under follow-up.

Proof points

• Four anti-references stated literally in PRODUCT.md, each with a structural reason: Jenkins/TeamCity, GitHub Actions UX clone, generic SaaS dashboard, mascot-driven toy
• Visual signature: gold and dark, not slate and blue and emerald; resisting that softening is named as a design principle
• Stack-collapse claim that none of the four reference points can match: build, deploy, scan, score in one keyboard-driven interface
• WCAG 2.2 AA as a floor across web, terminal, and mobile clients; not a “we’ll get to it” line item

quadrantChart
  title Sparki vs. the four anti-references
  x-axis "Slow & ceremonial" --> "Fast & direct"
  y-axis "Generic look" --> "Earned distinctiveness"
  quadrant-1 "Sparki target"
  quadrant-2 "Distinctive but slow"
  quadrant-3 "Generic and slow"
  quadrant-4 "Fast but generic"
  "Jenkins / TeamCity": [0.15, 0.25]
  "GitHub Actions UX": [0.55, 0.3]
  "Generic SaaS dashboard": [0.6, 0.2]
  "Mascot-driven toy": [0.5, 0.5]
  "Sparki": [0.85, 0.85]