Does SigRank replace Amazon Q Developer?

No — SigRank is not a coding assistant. Amazon Q Developer (formerly CodeWhisperer) is AWS's AI coding assistant, optimized for AWS workflows and cloud-native development; SigRank is the scoring layer that measures how efficiently you drive any AI tool, including Amazon Q. You keep using Amazon Q (or Claude Code, or Copilot) and run the SigRank CLI alongside it. SigRank reads your token telemetry locally, computes your Υ Yield, and publishes a signed snapshot to the leaderboard. Your assistant stays; your efficiency gets measured.

Does Amazon Q have usage metrics?

Amazon Q Developer surfaces some usage information in the AWS console — how many suggestions were accepted, reference tracking, and billing-relevant usage. That is AWS-console-scoped and AWS-locked: the numbers live inside your AWS account and do not leave it. SigRank reads the same underlying token flow but computes the full cascade architecture (Υ Yield, compression ratio, SNR, Leverage, Velocity), assigns a class tier, and lets you compare against every other operator on the board — including ones who never touch AWS.

Why does platform neutrality matter?

Because most operators do not use one tool or one cloud. You might use Amazon Q for AWS-native work, Claude Code for agentic tasks, and Cursor for refactoring. Amazon Q's metrics cover only the AWS slice; your actual efficiency is the union across all of them. SigRank is platform-neutral — it reads telemetry from Amazon Q, Claude Code, Copilot, Cursor, ChatGPT, Gemini, and 15+ others, scores them on the same cascade axis, and gives you one comparable rank. Your score follows you across tools and clouds, not the other way around.

Can I use SigRank with Amazon Q specifically?

Yes. The SigRank CLI reads token telemetry from Amazon Q Developer's local logs the same way it reads Claude Code's (ccusage is bundled for Claude Code; additional readers cover other platforms). Run `sigrank enroll` to create your operator identity, then `sigrank submit` to score and publish. Your Amazon Q sessions contribute to the same leaderboard rank as your Claude Code or Copilot sessions — unified, not siloed.

What is the difference between Amazon Q and SigRank metrics?

Amazon Q's metrics answer "how many suggestions did I accept in AWS?" — a per-session, console-local view tied to your AWS account. SigRank's metrics answer "how efficiently does this operator drive AI across all their tools?" — a cascade-level, cross-platform view. Amazon Q tells you what you did in one assistant; SigRank tells you your Υ Yield (is signal compounding or burning?), your class tier, and your global rank among all operators regardless of tool or cloud. The first is a gauge; the second is a leaderboard.

◈ SigRank vs Amazon Q Developer

Operator Scoring Across All Tools and Clouds

Amazon Q Developer is AWS-optimized. SigRank is platform-neutral — scores how efficiently you drive Amazon Q, Claude Code, Copilot, Cursor, and 15+ others. Your score follows you across tools and clouds.

The short version: Amazon Q Developer

No, SigRank does not replace Amazon Q Developer. Amazon Q Developer (formerly CodeWhisperer) is AWS's AI coding assistant — optimized for AWS workflows, cloud-native patterns, and the AWS console. That is a tool, not a metric. Amazon Q surfaces some usage data inside your AWS account, but it does not compute cascade efficiency, does not assign a class tier, and does not rank you against operators who use other tools. It assists within AWS; it does not measure how efficiently you drive AI.

SigRank is the platform-neutral layer that fixes that. It reads token telemetry from Amazon Q, Claude Code, Copilot, Cursor, and 15+ other tools, scores them all on the same cascade axis (Υ Yield), and gives you one rank that follows you across tools and clouds. You don't switch assistants to use SigRank — you add it alongside whatever you already drive.

Feature comparison

Feature	Amazon Q	SigRank
What it is	AWS AI coding assistant (formerly CodeWhisperer)	Platform-neutral operator scoring layer
Token usage tracking	Limited (AWS-console-scoped)	Yes (cascade-derived)
Cascade efficiency score (Υ = cache_read × output / input²)	No	Yes
Compression ratio + SNR + Leverage + Velocity	No	Yes
Class tier (IGNITER to ARCH+)	No	Yes
Global operator leaderboard	No	Yes
Works across Amazon Q + Claude Code + Cursor + 15+	No (Amazon Q only)	Yes
Score follows you across tools	No	Yes
Operator profiles + head-to-head compare	No	Yes
ed25519-signed snapshot submission	No	Yes
MCP server for agent integration	No	Yes
Privacy-preserving (token counts only)	Yes	Yes

The AWS lock-in problem

Amazon Q Developer's usage metrics are real — but they are AWS-console-scoped and AWS-locked. The numbers live inside your AWS account, in AWS's format, visible only in the AWS console. They do not export cleanly. They do not compare to anyone outside AWS. And they vanish the day you try a different tool or cloud.

Most operators do not live in one assistant or one cloud. A realistic week: Amazon Q for AWS-native work, Claude Code for agentic multi-file tasks, Cursor for refactoring, maybe a Copilot inline completion. Amazon Q's metrics cover one slice of that week. Your actual efficiency is the union — and SigRank is the only layer that scores the union on a single axis.

The cascade is tool-agnostic

Υ = cache_read × output / input² is computed from four token integers that every AI tool produces — input, output, cache-read, cache-write. The math does not care which assistant or cloud generated them. An operator who reuses context efficiently in Amazon Q scores the same way as one who does it in Claude Code. The cascade is the universal substrate.

Your score follows you, not the tool

SigRank's operator identity is tied to you, not to your assistant or your cloud. Enroll once, submit from any tool, and every signed snapshot feeds the same leaderboard rank. Switch from Amazon Q to Claude Code to Copilot over a month and your Υ trajectory reflects your driving across all three — not three disconnected per-tool gaages. That is the difference between a metric and a reputation.

Frequently asked questions

Does SigRank replace Amazon Q Developer?: No — SigRank is not a coding assistant. Amazon Q Developer (formerly CodeWhisperer) is AWS's AI coding assistant, optimized for AWS workflows and cloud-native development; SigRank is the scoring layer that measures how efficiently you drive any AI tool, including Amazon Q. You keep using Amazon Q (or Claude Code, or Copilot) and run the SigRank CLI alongside it. SigRank reads your token telemetry locally, computes your Υ Yield, and publishes a signed snapshot to the leaderboard. Your assistant stays; your efficiency gets measured.
Does Amazon Q have usage metrics?: Amazon Q Developer surfaces some usage information in the AWS console — how many suggestions were accepted, reference tracking, and billing-relevant usage. That is AWS-console-scoped and AWS-locked: the numbers live inside your AWS account and do not leave it. SigRank reads the same underlying token flow but computes the full cascade architecture (Υ Yield, compression ratio, SNR, Leverage, Velocity), assigns a class tier, and lets you compare against every other operator on the board — including ones who never touch AWS.
Why does platform neutrality matter?: Because most operators do not use one tool or one cloud. You might use Amazon Q for AWS-native work, Claude Code for agentic tasks, and Cursor for refactoring. Amazon Q's metrics cover only the AWS slice; your actual efficiency is the union across all of them. SigRank is platform-neutral — it reads telemetry from Amazon Q, Claude Code, Copilot, Cursor, ChatGPT, Gemini, and 15+ others, scores them on the same cascade axis, and gives you one comparable rank. Your score follows you across tools and clouds, not the other way around.
Can I use SigRank with Amazon Q specifically?: Yes. The SigRank CLI reads token telemetry from Amazon Q Developer's local logs the same way it reads Claude Code's (ccusage is bundled for Claude Code; additional readers cover other platforms). Run `sigrank enroll` to create your operator identity, then `sigrank submit` to score and publish. Your Amazon Q sessions contribute to the same leaderboard rank as your Claude Code or Copilot sessions — unified, not siloed.
What is the difference between Amazon Q and SigRank metrics?: Amazon Q's metrics answer "how many suggestions did I accept in AWS?" — a per-session, console-local view tied to your AWS account. SigRank's metrics answer "how efficiently does this operator drive AI across all their tools?" — a cascade-level, cross-platform view. Amazon Q tells you what you did in one assistant; SigRank tells you your Υ Yield (is signal compounding or burning?), your class tier, and your global rank among all operators regardless of tool or cloud. The first is a gauge; the second is a leaderboard.

Keep Amazon Q. Add the score that follows you.

Amazon Q assists your AWS workflow. SigRank measures your driving — across Amazon Q and every other tool you use. Install the CLI, submit a signed snapshot, and get a rank that doesn't reset when you switch tools or clouds.

Calculate your Υ Yield See the leaderboard