Renamed

Amazon CodeWhisperer became Amazon Q Developer on April 30, 2024

Go to Amazon Q Developer

perch vs Amazon CodeWhisperer

Side-by-side comparison of features, pricing, and ratings

Analysis reviewed Live tool data as of 2026-09-29
Cross-checked through our multi-step verification ·
Saved

At a glance

DimensionperchAmazon CodeWhisperer
CategorySemantic code linter (CLI)AI coding assistant / IDE plugin
PricingFreeFreemium (free tier + Pro)
Installnpm install -g @lakeday/perchIDE extension + CLI
Core jobEnforce repo rules with natural-language `--ensure` guaranteesGenerate code, agentic tasks, security scan, modernization
IntegrationsGitHub Actions, Claude Code, Codex, CursorVS Code, JetBrains, Visual Studio, Eclipse, AWS Console, Slack, Teams, GitLab, GitHub
Current namePerch (@lakeday/perch)Rebranded to Amazon Q Developer (Apr 2024)
perch
perch

Perch is a semantic code linter that turns your team's review rules into committed, executable policy checks powered by Jev.

Visit Website
Amazon CodeWhisperer
Amazon CodeWhisperer

Renamed: Amazon CodeWhisperer became Amazon Q Developer on April 30, 2024; all its features moved there.

Visit Website
Pricing
Free
Freemium
Plans
Free (MIT license); per-scan Jev analysis billed separately
$0/mo
$19/user/mo
Popularity
1 views
6.3k views
Skill Level
Intermediate
Intermediate
API Available
Platforms
CLI
WebDesktopCLIPlugin
Categories
🔎 Code Review & Quality🔐 Application & Code Security
💻 Code & Development🛠️ Autonomous Coding Agents🔐 Application & Code Security
Features
Run semantic scans across a source tree with `perch scan` for defects and security issues
Author custom lints in perch.yaml with plain-language guarantees via `--ensure`
Scope rules by unit with `--each method` or `--each file`
Limit rules to path globs with `--where "src/**/*.ts"`
Report each finding with rule ID, file:line, severity, confidence percentage, and method name
Filter a scan to one rule with `perch scan --filter rule=<name>`
Test a rule against a specific symbol with `perch check <file>::<method> --rules <name>`
Detect off-by-one loop errors, weak cryptography (MD5-hashed tokens), and unhandled nulls
Score findings probabilistically (e.g. 91%, 93%, 72%) rather than pass/fail
Scan only changed files with surrounding context using `perch scan --since origin/main`
Fail CI jobs on breaking findings with exit code 3
Store findings locally in the .perch directory
Apply rules to non-code files such as Markdown documentation with `--each file`
Install the Perch skill for Claude Code, Codex, or Cursor so agents check their own fixes
Report scan summaries with finding count, methods touched, and estimated cost
Real-time code suggestions from snippets to full functions
Inline chat inside the code editor
CLI autocompletions and natural-language-to-bash translation
Agentic coding that autonomously implements features
Agentic documentation, testing, review and refactoring of code
Software upgrades, including Java 8 to Java 17
Software upgrades, including .NET porting from Windows to Linux
Security vulnerability scanning with remediation suggestions
Customizable recommendations by connecting private repositories
AWS expert assistance in the AWS Management Console
AWS assistance in Microsoft Teams and Slack
Enterprise access controls via AWS IAM Identity Center
IDE plugins for JetBrains, VS Code, Visual Studio and Eclipse
Command line plugin
Support ends for IDE plugins on April 30, 2027; AWS points to Kiro
Integrations
GitHub Actions
Claude Code
Codex
Cursor
VS Code
JetBrains IDEs
Visual Studio
Eclipse
Command line
AWS Management Console
AWS Console Mobile Application
Microsoft Teams
Slack
GitHub.com
GitHub Enterprise Cloud
GitLab

What real users say: perch vs Amazon CodeWhisperer

Not marketing copy and not our opinion — a structured sweep of public discussion (reviews, forums, communities and video comments), showing what people praise and what they complain about for each tool.

perch

70 mentions across 6 sources · 14% positive — critical (weighted across 6 sources)

Reddit, Hacker News, YouTube, Product Hunt, GitHub, Lemmy

What users praise

  • • Free and globally installed via npm as @lakeday/perch — zero cost to try.
  • • Natural-language rules in perch.yaml let you encode team conventions as reviewable code.
  • • Findings include rule ID, file:line, severity, confidence percentage, and enclosing method.
  • • Per-finding confidence scoring avoids binary pass/fail and reduces false-positive fatigue.

What frustrates them

  • • Almost no independent user reviews or testimonials exist for the actual linter.
  • • Open language-filtering bug means shipped scans may flag irrelevant vulnerability classes.
  • • No listed integrations with CI/CD, editors, or Slack — everything is manual CLI wiring.
  • • Name collision with Google Perch and a board game makes community support hard to find.

Researched Sep 26, 2026

Amazon CodeWhisperer

11 mentions across 3 sources · 55% positive — mixed (weighted across 3 sources)

Hacker News, YouTube, Product Hunt

What users praise

  • • Generous free tier: 50 agentic chat interactions and 1,000 lines of transformation monthly.
  • • Built-in open-source license reference tracker provides clear attribution and legal safety.
  • • Seamless integration within AWS ecosystem, including console, Slack, and Microsoft Teams.
  • • Strong security scanner that identifies vulnerabilities and suggests fixes directly in code.

What frustrates them

  • • AWS-centric focus is a disadvantage for non-AWS cloud developers.
  • • Semantic analysis concept criticized as fundamentally flawed by HN commenter.
  • • Some view tool as trend-driven rather than innovative, lacking true 'semantic' understanding.
  • • Performance quality of code suggestions not consistently benchmarked against GPT or Copilot.

Researched Sep 9, 2026

Feature-by-feature

Q Developer and Perch overlap only in "code quality," and even there they do different things. Q Developer is a generative assistant: real-time suggestions, inline chat, CLI autocompletion and natural-language-to-bash, agentic multi-step implementation with unit tests, Java 8-to-17 upgrades and .NET Windows-to-Linux porting, plus an AWS-expert chat in Slack, Teams, and the AWS Console. Its built-in security scanner finds vulnerabilities and proposes fixes. Perch doesn't generate or refactor code at all. It scans a tree with perch scan and reports rule ID, file:line, severity, a confidence percentage (e.g. 91%, 78%), and the enclosing method — probabilistic judgments, not pass/fail. Its differentiator is authoring: you write rules in perch.yaml with perch rules add --ensure in plain language, scope them with --each method/--each file and --where "src/**/*.ts", filter with --filter rule=<name>, test against a symbol with perch check <file>::<method>, and scan only changed files via --since origin/main. It catches off-by-one loops, MD5-hashed tokens, and unhandled nulls, fails CI on breaking findings with exit code 3, and stores results in .perch. Q Developer's checks are vendor-defined; Perch's are whatever your team commits.

Pricing compared

Q Developer is freemium per its pricing data: there's a free tier plus a Pro tier whose stated benefit is that proprietary content isn't used for service improvement — relevant if your code can't train a vendor model. Specific dollar figures aren't in the data provided, so verify current AWS pricing before budgeting. Perch is free and open to install globally via npm (npm install -g @lakeday/perch), with findings stored locally in .perch. The honest cost of Perch isn't license fees — it's the engineering time to write and maintain your perch.yaml rules, since zero-config linting is explicitly not the product. If your team won't invest that authoring time, Perch delivers little; if it will, the marginal cost per scan is near zero. For Q Developer, the calculus flips: you get immediate value out of the box, but you're paying (or accepting the free tier's terms) and you're anchored to the AWS ecosystem. Note the not-for lists: Q Developer isn't for multi-cloud or non-AWS teams; Perch isn't for teams needing a hosted dashboard or org-wide analytics.

Who should pick which

  • AWS-centric dev team modernizing legacy apps
    Pick: Amazon CodeWhisperer

    Java 8-to-17 upgrades and .NET Windows-to-Linux porting are built-in agentic features no linter touches.

  • Team reviewing AI-generated PRs from Cursor/Codex/Claude Code
    Pick: perch

    It integrates with those agents and gates code with committed, readable rules and confidence-scored findings.

  • Enterprise needing IAM-based access controls and privacy
    Pick: Amazon CodeWhisperer

    IAM Identity Center controls and Pro-tier privacy protections are listed features; Perch explicitly lacks multi-user policy management.

  • Solo dev who wants defect/security detection cheaply
    Pick: perch

    Free, local findings in .perch with near-zero scan cost — provided you write your own rules.

  • Team whose review friction is project-specific behavior
    Pick: perch

    '--ensure' natural-language rules target things like logging secrets or discount caps that generic linters miss.

Frequently Asked Questions

Is Amazon CodeWhisperer still called that?

No — it rebranded to Amazon Q Developer in April 2024, with expanded agentic features. The slug here is legacy naming.

Can I run both Perch and Q Developer together?

Yes. They operate at different layers. Q Developer generates, refactors, and scans inside your IDE; Perch enforces repo-committed rules in CI. Many teams will stack them.

Does Perch generate or fix code?

No. It finds and reports issues with rule ID, location, severity, and confidence. Fixing is left to you or your AI coding agent.

Do I need to write rules for Perch to be useful?

Yes. Perch explicitly isn't zero-config drop-in linting — value depends on your perch.yaml rules authored via `perch rules add --ensure`.

Can Q Developer enforce my team's custom policy rules in CI?

Its security scanning and remediation suggestions are vendor-defined (AWS-focused). If you need repo-committed natural-language rules with exit code 3 CI gating, that's Perch's job.

Is Perch suitable for org-wide analytics or hosted dashboards?

Its not-for list rules these out. Findings live locally in `.perch`; there's no multi-user policy management or cross-repo analytics.

More perch or Amazon CodeWhisperer comparisons

Explore each tool further

Browse these categories

Still deciding? Get the weekly AI tools brief

One email a week — new tools, honest comparisons, no spam.

Last reviewed: September 26, 2026