wouldit.work

Developer tools

Fig: a loved terminal autocomplete tool, acquired by AWS and sunset a year later

Fig added IDE-style autocomplete to the command line and built a big open-source community. Amazon acquired its technology in 2023, folded it into CodeWhisperer, then Amazon Q, and shut Fig down on 1 September 2024.

Product
Fig
Founder
Brendan Falk
Launched
2020
Model
Free tier + paid team plans (made free after the acquisition)

Published · 2 min read · 6 sources

  • #terminal
  • #cli
  • #autocomplete
  • #yc
  • #acquisition
  • #sunset
  • #open-source-community
  • #aws

Key takeaways

  • YC-backed, founded in 2020, raised a little over $2M; claimed hundreds of thousands of users and 22k GitHub stars.
  • Aug 2023: Amazon acquired Fig's technology and the team joined AWS. New signups stopped and paid features became free.
  • Fig was sunset on 1 Sep 2024 and user data deleted; core features moved to Amazon's command-line tool.

What it is

Fig brought IDE-style autocomplete to the terminal: suggestions and descriptions for the next command as you type (TechCrunch). It also offered Scripts, Dotfiles, Plugins and Servers (Fig blog, archived). The fig.io site returned errors when checked on 3 Nov 2026, so the Fig pages below are Wayback Machine copies.

Timeline

  • 2020: founded in San Francisco; a Y Combinator company that raised "a little north of $2 million" (TechCrunch).
  • Aug 2023: "Amazon has acquired Fig's technology" and the team joins AWS. Paid Team features become free and new signups stop (Fig blog, archived). Terms were not disclosed (TechCrunch).
  • Nov 2023: the team ships Amazon CodeWhisperer for command line (Fig blog, archived).
  • Early 2024: Fig announces it will be sunset on 1 September 2024; user data will be deleted that day (Fig blog, archived).
  • 1 Sep 2024: access ends; users are pointed to Amazon Q for command line (Fig, archived).
  • 3 Nov 2026: the open-source completion specs repo still shows 25,000+ stars (GitHub API).

Why it worked

  • A daily pain for developers. Remembering CLI flags is tedious; Fig saved keystrokes in a tool used constantly (TechCrunch).
  • Community-built coverage. By the end the team cited "hundreds of thousands of users, 22k GitHub stars, 13k Discord members, 400+ open source contributors, and 5 products" (Fig, archived).
  • Strategic value to a giant. TechCrunch said Fig claimed users at Google, Microsoft and Amazon, and linked the deal to AWS's generative AI push (TechCrunch).

What to learn

  1. A loved developer tool is not the same as a business. Fig's most visible outcome was an acquisition of its technology, not a standalone company.
  2. If you sell to big tech's developers, big tech may decide to own the feature.
  3. Community assets (open specs, contributors) can outlive the product; the specs repo is still public (GitHub).

Risks and what didn't work

  • Product loss after acquisition. Fig was shut down about a year after the deal, and Scripts, Dotfiles, Plugins and Servers were not carried over (Fig blog, archived).
  • Users had to migrate to Amazon's tool, and data not exported was deleted (Fig blog, archived).
  • The price and Fig's revenue were never disclosed; user counts are company-reported (TechCrunch).

FAQ

Short answers drawn from the sections above.

What is Fig?

Fig brought IDE-style autocomplete to the terminal: suggestions and descriptions for the next command as you type (TechCrunch). It also offered Scripts, Dotfiles, Plugins and Servers (Fig blog, archived). The fig.io site returned errors when checked on 3 Nov 2026, so the Fig pages below are Wayback Machine copies.

Why did Fig work?

  • A daily pain for developers. Remembering CLI flags is tedious; Fig saved keystrokes in a tool used constantly (TechCrunch).
  • Community-built coverage. By the end the team cited "hundreds of thousands of users, 22k GitHub stars, 13k Discord members, 400+ open source contributors, and 5 products" (Fig, archived).
  • Strategic value to a giant. TechCrunch said Fig claimed users at Google, Microsoft and Amazon, and linked the deal to AWS's generative AI push (TechCrunch).

What can indie builders learn from Fig?

  1. A loved developer tool is not the same as a business. Fig's most visible outcome was an acquisition of its technology, not a standalone company.
  2. If you sell to big tech's developers, big tech may decide to own the feature.
  3. Community assets (open specs, contributors) can outlive the product; the specs repo is still public (GitHub).

What didn't work for Fig, and what are the risks?

  • Product loss after acquisition. Fig was shut down about a year after the deal, and Scripts, Dotfiles, Plugins and Servers were not carried over (Fig blog, archived).
  • Users had to migrate to Amazon's tool, and data not exported was deleted (Fig blog, archived).
  • The price and Fig's revenue were never disclosed; user counts are company-reported (TechCrunch).

Sources

Every link cited above, in order of first use.

  1. 1.TechCrunch (techcrunch.com)
  2. 2.Fig blog, archived (web.archive.org)
  3. 3.Fig blog, archived (web.archive.org)
  4. 4.Fig, archived (web.archive.org)
  5. 5.GitHub API (api.github.com)
  6. 6.GitHub (github.com)

Related case studies

More in Developer tools →