Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Amazon Web Services acquired Fig’s technology and brought its team into AWS in August 2023. The deal’s financial terms were not disclosed. Fig later ended its standalone service; its command-line work moved through Amazon CodeWhisperer and Amazon Q Developer, whose CLI AWS documentation says was rebranded as Kiro by 2026.
What AWS acquired
Fig announced on August 28, 2023, that Amazon had acquired its technology and that the Fig team, including its co-founders, would join AWS. The announcement described a technology acquisition, not a public purchase of the entire operating company. Neither a purchase price nor a valuation, retention package, or detailed deal structure was disclosed. Fig’s acquisition announcement is the primary account; TechCrunch’s coverage followed the next day.
Fig was a San Francisco startup founded in 2020 and a Y Combinator alumnus. TechCrunch reported that it had raised slightly more than $2 million and named investors including Y Combinator, General Catalyst, Datadog CEO Olivier Pomel, Eventbrite founder Kevin Hartz, and former GitHub CTO Jason Warner. Those are reported startup-background figures, not terms of Amazon’s deal.
What Fig did for developers
Fig aimed to make text-based work in the terminal easier to navigate. Its signature feature was command-line autocomplete: as a developer typed, Fig could suggest commands and options and show inline descriptions. The company said its completion specifications covered hundreds of popular command-line tools, and developers could extend them.
#1 Best Overall
Autocomplete was only part of the pitch. Fig’s product family also included scripts, shared dotfiles and secrets, SSH and access workflows, a plugin store, and terminal integrations. It presented the terminal as a place for interactive developer tools, not merely a prompt for typing commands. Its historical overview describes that broader ambition: Fig’s product overview. Its download page listed supported terminals and development environments, but those historical compatibility claims do not mean the standalone software remains supported.
Why the acquisition mattered to AWS
AWS did not publicly lay out every strategic motive for the deal. One reasonable interpretation is that Fig brought expertise in terminal user experience at a time when cloud and AI companies were competing to help developers across the “inner loop” of building and operating software.
Developers use terminals to run cloud CLIs, inspect logs, deploy infrastructure, manage containers, and automate routine work. AWS already has a major command-line surface in the AWS CLI. Fig’s completion interface and knowledge of developer workflows could make complex commands easier to discover; its team’s experience could also complement AWS’s developing AI-assistant efforts. That is analysis of the fit, not a confirmed statement that AWS acquired Fig for any one of those reasons or solely to promote AWS services.
Free tools Windows power users keep installed
One-click scans. No signup required.
What Fig users were told at the time
In contemporaneous coverage, Fig’s paid features were reported to have become free for existing users after the acquisition announcement. The team said it planned to combine Fig’s expertise with AWS’s resources, but the announcement did not give users a detailed integration roadmap. It was therefore unclear how the product would evolve, including what the change would mean for developers working outside AWS. TechCrunch’s August 2023 report covered those immediate user-facing changes and uncertainties.
Fig’s path through AWS products
| Date | What happened |
|---|---|
| August 28, 2023 | Fig announced that Amazon acquired its technology and its team joined AWS. |
| November 2023 | Fig said the team had shipped Amazon CodeWhisperer for command line. |
| February 5, 2024 | Fig announced that its standalone product would sunset on September 1, 2024. |
| September 1, 2024 | Fig access ended; users were directed to Amazon’s successor tooling. |
| 2024 onward | CodeWhisperer capabilities moved into Amazon Q Developer. |
| By 2026 | AWS documentation said the Amazon Q Developer CLI had been rebranded as Kiro. |
When it announced the sunset, Fig said users could export their data with fig export and that it would delete user data on September 1, 2024. Its migration flow was also described as automatically exporting data for users moving to CodeWhisperer. Those were historical sunset instructions, not current Fig migration steps. Fig’s sunset announcement has the details.
Is Kiro the same product as Fig?
No. The lineage is best understood as a series of AWS product transitions: Fig’s command-line effort was directed to CodeWhisperer for command line, CodeWhisperer capabilities later moved into Amazon Q Developer, and AWS documentation says the Q Developer CLI has been rebranded as Kiro. That is continuity in the command-line direction and team history, not proof that all of Fig became one current product.
Rank #3
| Fig area | What is established about the successor |
|---|---|
| Command-line assistance | AWS has a command-line assistant in the Q Developer/Kiro lineage; name and branding have changed. |
| Autocomplete and suggestions | Command-line assistance continued, but identical inline behavior or completion coverage is not established. |
| Fig Scripts | One-for-one continuity is not established. |
| Dotfiles and secrets | One-for-one continuity is not established. |
| SSH and team access | One-for-one continuity is not established. |
| Open completion specifications and plugin ecosystem | Fig’s historical extensibility was part of its product; preservation as a supported standalone Fig service is not established. |
AWS describes its command-line assistant as able to generate code, suggest changes, read and write local files, call AWS APIs, run shell commands, and work with native and MCP-based tools. Those are broader agent-style capabilities than Fig’s original autocomplete focus. See AWS’s command-line and product overview and its Q Developer CLI-to-Kiro rebranding documentation.
Recommended Free Tools
What to check before choosing the successor
Match the interaction to the job
Fig’s appeal was fast, inline command discovery. An AI terminal agent can do more, such as work across files or run commands, but that broader scope may be unnecessary if all you want is deterministic shell completion. Check the current Kiro experience against the terminal, shell, and suggestion style you actually use.
Consider cloud fit and portability
Fig was positioned as a general developer tool. Kiro is part of an AWS-owned product line, which may suit AWS users, but developers on Azure, Google Cloud, on-premises systems, or mixed infrastructure should check whether the integrations and workflow fit. Do not infer cloud neutrality or lock-in solely from the product’s ancestry.
Review data use and permissions
An assistant that can use code context, read or write files, execute shell commands, or call cloud APIs has a wider risk surface than autocomplete. Review AWS’s current data-use and privacy documentation before sending sensitive material, inspect proposed commands, and use least-privilege credentials. Avoid giving an agent production credentials unless the workflow and permissions are deliberately constrained.
Check sign-in, limits, and price
AWS’s getting-started material lists AWS Builder ID for personal use and IAM Identity Center for organizational access. A Builder ID is not an AWS console identity and does not provide console access or IAM roles; see AWS’s Builder ID guidance and current getting-started information.
AWS pricing information available in August 2026 listed Amazon Q Developer Free at $0 with 50 agentic requests per month and up to 1,000 lines of code per month for the cited transformation capability, and Pro at $19 per user per month with higher limits and additional organizational capabilities. These are plan-specific limits and prices, not a guarantee of Kiro’s future pricing or eligibility; check AWS’s current pricing page and tier documentation before signing up. AWS documents q whoami to check the signed-in identity and q chat to start an interactive session; the CLI’s name and upgrade path may change during the Kiro transition. The documented Builder ID Pro upgrade flow used /subscribe from the CLI. See AWS’s Pro upgrade instructions.
Best Value
Alternatives if you only want command completion
If the main thing you miss is Fig’s lightweight, predictable completion rather than AI-driven file edits or command execution, shell-native completion may be a closer fit. Zsh, Fish, and Bash each maintain their own completion systems: Zsh, Fish, and Bash. Their features and setup differ, and they are not direct equivalents to Fig’s broader scripts, sharing, or plugin ambitions.
For a different AI-terminal approach, Warp is a terminal product to investigate; for GitHub-centered teams, GitHub Copilot is a broader coding-assistant ecosystem. Compare shell and OS support, whether suggestions are deterministic or AI-generated, local versus cloud-assisted operation, enterprise controls, and command permissions rather than assuming feature parity. The conventional AWS CLI remains the tool for issuing AWS service commands; it is not itself a Fig-style AI autocomplete product. AWS announced that CLI v1 entered maintenance mode on July 15, 2026, with end of support scheduled for July 15, 2027, and recommends CLI v2: AWS’s lifecycle announcement.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
