KiroAmazon Web Services · ai-idevs
Google AntigravityGoogle · ai-ide
AWS's spec-driven agent IDE vs Google's agent-first IDE. Both are new, both push a 'plan first' workflow, both gate capacity behind their parents' subscriptions.
agentlist.io · documented attributes · sources and dates shown per value
Compare the same attributes
Every entry uses the same category fields. Open a source to check the scope and date behind a value. Not documented means we have no supported value, not that a feature is absent.
| Attribute | KiroAwaiting documentation reviewCode interactively · provisional | Google AntigravityAwaiting documentation reviewCode interactively · provisional |
|---|---|---|
| Common attributesDirectory metadata and source-documented values. Not documented is an evidence gap, not a negative claim. | ||
| CategoryAgentlist's buyer category; directory classification rather than a product capability. | Coding assistants | Coding assistants |
| Entry typeDirectory classification distinguishing products, frameworks, infrastructure and protocols. | product | product |
| Directory coverageHow the entry entered this directory; not a quality rating or a claim that every field is verified. | Cataloged | Cataloged |
| Recorded availabilityAvailability classification in the directory; check the source and review date before relying on current access. | active | active |
| InterfacesDocumented ways a person or application interacts with the entry. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| Execution / hostingWhere the documented service or workload runs; this is not a data-residency guarantee. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| Pricing basisSource-described price and billing basis. Different units and plans are not directly equivalent. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. |
| LicenseDocumented license for the specified component or offering. | Not documented | Not documented |
| Coding assistantsComparable questions for this category. Sources and dates describe the evidence; no performance ranking is implied. | ||
| File editingReads and changes project files, including multi-file edits. | Not documented | Not documented |
| Repository contextUses context across a repository rather than only the current file. | Not documented | Not documented |
| Shell accessCan execute terminal or shell commands. | Not documented | Not documented |
| Code executionRuns code in an execution environment. | Not documented | Not documented |
| Git and pull requestsSupports documented branch, commit or pull-request workflows; consult the cited scope. | Not documented | Not documented |
| MCP supportDocumented MCP client or server support; consult scope for the role. | Not documented | Not documented |
| Provider subscriptionsAccepts an existing provider subscription; supported providers and plans must be scoped. | Not documented | Not documented |
Pick which
pick Kiro if
You want spec-driven development (requirements → design → tasks) inside the AWS ecosystem.
pick Google Antigravity if
You want Google's agent-first surface and already pay for Google AI Pro/Ultra.
watch out
Both credit systems are young and have already repriced once — re-check before annualizing.
Feature notes
- Kiro
- 01Spec-driven workflow
- 02Agent hooks
- 03Auto agent
- 04MCP
- 05Kiro CLI
- 06Claude + open-weight models
- Google Antigravity
- 01Agent manager
- 02Gemini 3.x + Claude + gpt-oss models
- 03Antigravity CLI
- 04Browser tool
- 05Free Individual tier
Frequently asked
Kiro or Google Antigravity — which should I pick?
AWS's spec-driven agent IDE vs Google's agent-first IDE. Both are new, both push a 'plan first' workflow, both gate capacity behind their parents' subscriptions. Pick Kiro if: You want spec-driven development (requirements → design → tasks) inside the AWS ecosystem. Pick Google Antigravity if: You want Google's agent-first surface and already pay for Google AI Pro/Ultra.
Is Kiro or Google Antigravity cheaper?
Kiro: Free (50 credits); Pro $20/user/mo; Pro+ $40; Pro Max $100; Power $200. Google Antigravity: Individual free; higher quota via Google AI Pro $19.99 / Ultra $99.99–$199.99. These are recorded catalog prices, not a fresh quote. Check vendor pricing for current plans, usage charges and seat terms.
Does Kiro or Google Antigravity run locally?
Kiro hosting: local, cloud. Google Antigravity hosting: local, cloud. Interfaces differ too: Kiro exposes editor/cli, Google Antigravity exposes editor/cli.
Are Kiro and Google Antigravity still maintained?
Recorded catalog status — Kiro: actively maintained. Google Antigravity: actively maintained. Check the linked sources for current availability; the catalog's creation date is not a product verification date.