Amazon Q Developer

D▼ -19 vs last quarter

CAUTION — END-OF-SUPPORT confirmed.

Rate this tool Add to compare

Dimension breakdown

Score · confidence

UX / DX

50% conf55

Capability

50% conf50

ReliabilityIncomplete data at this time

Value

50% conf10

CommunityIncomplete data at this time

Enterprise / Compliance

50% conf40

Autonomy

50% conf50

Integration

50% conf60

Sources blend review platforms, community sentiment, the Signal Radar and practitioner ratings. Scores re-blend each quarter.

CAUTION — END-OF-SUPPORT confirmed. AWS official announcement (Apr 30, 2026): new signups blocked 2026-05-15; Opus 4.6 removed from Q Developer Pro 2026-05-29; full EOS for IDE plugins and paid subscriptions 2027-04-30.

AWS-recommended migration path is Kiro (kiro.dev) — VS Code foundation and CLI backward-compatible (q / q chat entry points work in Kiro CLI). Eclipse and Visual Studio users have NO native Kiro plugin — must adopt Kiro standalone IDE or Kiro CLI. Existing SOC 2 II / ISO 27001 attestations remain valid through normal audit cycle; AWS commits only to critical bugfixes through 2027-04-30, no new certifications (no HIPAA BAA, no FedRAMP).

DO NOT recommend for any new engagement. Existing deployments must plan Kiro migration by Q1 2027.

Recommended

Use cases

Not yet assessed — this section fills in as ACES research covers the tool.

Score caps

Risk flags

Stalled development
stabilityTemporary
No releases or updates in 90+ days
Caps all dimensions at 60
Removed when — New release published with active development signals

Assessment

Status rationale

Not Enterprise Viable — CONFIRMED TERMINAL TRAJECTORY. AWS official EOL announcement (Apr 30, 2026) is the authoritative primary source. New signups blocked 2026-05-15.

Full EOS 2027-04-30. Migration path to Kiro documented but Eclipse and Visual Studio users face material friction (no native Kiro plugin — standalone IDE or CLI only).

Existing SOC 2 II / ISO 27001 posture remains valid through normal audit cycle but no new certifications coming. Critical bugfixes only through sunset.

Recommending Q Developer for any new engagement, or for any existing engagement without a documented Kiro migration plan by Q1 2027, would be negligent. The orchestrator should consider a future schema enhancement to support a 'Deprecated' or 'Sunset' lifecycle indicator distinct from Detected — current schema captures the state correctly via stalled-development cap + viability=2 + CAUTION quick take + notEnterpriseReadyReason.

Watch for

Movement triggers

Demotion Signal

No further downward signal-level movement available in current four-tier signal model (Validated/Assessed/Tracked/Detected).

Stays at Detected with CAUTION quick take + notEnterpriseReadyReason + stalled-development cap + viability=2.

Upgrade Would Require

AWS rescission of EOL announcement AND re-commitment to Q Developer roadmap AND restoration of latest model availability (Opus 4.7+) — no plausible signals any of these will occur.

Track Kiro (kiro) as the AWS-strategic replacement.

Caution