Skip to main content
Back to time machine

Blitzy

Tracked across 15 snapshots (2026-03-12 → 2026-06-12).

Tool detailAsk about this trajectory
Latest rating
68
Rating delta
+68
Latest signal
Tracked
Tracked
Caps now applied
2

Rating timeline

02550751002026-03-12 — rating 0, no level2026-03-30 — rating 0, no level2026-04-07 — rating 0, no level2026-04-09 — rating 65, Tracked2026-04-10 — rating 65, Tracked2026-04-20 — rating 60, Tracked2026-04-21 — rating 60, Tracked2026-04-30 — rating 60, Tracked2026-05-04 — rating 54, Tracked2026-05-05 — rating 65, Tracked2026-05-16 — rating 71, Tracked2026-05-18 — rating 71, Tracked2026-05-28 — rating 71, Tracked2026-06-10 — rating 68, Tracked2026-06-12 — rating 68, Tracked2026-03-122026-04-302026-06-12

Dimension trajectory

Autonomy

16/20
2002026-03-12 — 0/202026-03-30 — 0/202026-04-07 — 0/202026-04-09 — 16/202026-04-10 — 16/202026-04-20 — 17/202026-04-21 — 17/202026-04-30 — 17/202026-05-04 — 16/202026-05-05 — 16/202026-05-16 — 16/202026-05-18 — 16/202026-05-28 — 16/202026-06-10 — 16/202026-06-12 — 16/20

Integration

12/20
2002026-03-12 — 0/202026-03-30 — 0/202026-04-07 — 0/202026-04-09 — 12/202026-04-10 — 12/202026-04-20 — 11/202026-04-21 — 11/202026-04-30 — 11/202026-05-04 — 12/202026-05-05 — 12/202026-05-16 — 13/202026-05-18 — 13/202026-05-28 — 13/202026-06-10 — 12/202026-06-12 — 12/20

Context

15/20
2002026-03-12 — 0/202026-03-30 — 0/202026-04-07 — 0/202026-04-09 — 17/202026-04-10 — 17/202026-04-20 — 16/202026-04-21 — 16/202026-04-30 — 16/202026-05-04 — 17/202026-05-05 — 17/202026-05-16 — 17/202026-05-18 — 17/202026-05-28 — 17/202026-06-10 — 15/202026-06-12 — 15/20

Compliance

15/20
2002026-03-12 — 0/202026-03-30 — 0/202026-04-07 — 0/202026-04-09 — 13/202026-04-10 — 13/202026-04-20 — 13/202026-04-21 — 13/202026-04-30 — 13/202026-05-04 — 13/202026-05-05 — 13/202026-05-16 — 15/202026-05-18 — 15/202026-05-28 — 15/202026-06-10 — 15/202026-06-12 — 15/20

Viability

16/20
2002026-04-20 — 8/202026-04-21 — 8/202026-04-30 — 8/202026-05-04 — 0/202026-05-16 — 17/202026-05-18 — 17/202026-05-28 — 17/202026-06-10 — 16/202026-06-12 — 16/20

Interface

7/20
2002026-03-12 — 0/202026-03-30 — 0/202026-04-07 — 0/202026-04-09 — 7/202026-04-10 — 7/202026-04-20 — 7/202026-04-21 — 7/202026-04-30 — 7/202026-05-04 — 7/202026-05-05 — 7/202026-05-16 — 7/202026-05-18 — 7/202026-05-28 — 7/202026-06-10 — 7/202026-06-12 — 7/20

Cap timeline

Q2 26no-automation-modeno-automation-mode: 2026-04-09 → 2026-04-10no-automation-mode: 2026-05-04 → 2026-06-12pricing-opacitypricing-opacity: 2026-04-09 → 2026-04-10pricing-opacity: 2026-05-04 → 2026-06-12

Notable events

  • 2026-04-09Signal— → Tracked
  • 2026-04-09Cap +no-automation-mode
  • 2026-04-09Cap +pricing-opacity
  • 2026-04-09Jump+65 rating
  • 2026-04-20Cap −no-automation-mode
  • 2026-04-20Cap −pricing-opacity
  • 2026-04-20Drop-5 rating
  • 2026-05-04Cap +no-automation-mode
  • 2026-05-04Cap +pricing-opacity
  • 2026-05-04Drop-6 rating
  • 2026-05-05Jump+11 rating
  • 2026-05-16Jump+6 rating

What would move this next

Upgrade to Adopted if: CLI/API or IDE integration launches (removes web-only constraint and lifts no-automation-mode cap), second wave of Fortune 500 reference customers published, pricing transparency improves to self-serve tiers below $50K. Downgrade to Emerging if: Customer retention issues emerge post-contract (36-48 month lock-in), interface limitations cause developer-led adoption stalls, funding trajectory reverses.

Blitzy — history | Agentic Developer Tools Radar · Signal