Developer Tools · head to head
Fig vs Height
Fig
Developer Tools
IDE-style autocomplete for your existing terminal
- From
- Free
- Free plan
- Yes
Height
Technology
A project management tool from a small independent vendor that uses AI agents to handle routine ticket maintenance.
- From
- Free
- Free plan
- Yes
The short version
- Each has a real cost: Fig shut down on 1 September 2024. Amazon acquired Fig in August 2023 and folded it into Amazon Q Developer, which now carries the terminal autocomplete; Height it is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which Fig and Height actually diverge.
Identical on both: starting price (Free), free tier (Yes), platforms (Web), user rating (Not yet rated).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Fig
Nothing recorded that Height does not also cover.
Only in Height
- Autonomous triage
- Duplicate detection
- Attribute maintenance
- Per-task chat
- Multiple views
- Developer integrations
- Custom fields and filters
- Public API
What people use each for
The jobs each tool is most often brought in to do.
Fig
No use cases recorded yet. See the Fig review.
Height
- A product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has timenot Fig
- Teams leaving Jira because its configuration and administration cost more attention than the tracking is worthnot Fig
- A support or intake queue where incoming requests need categorising and deduplicating before anyone can plan themnot Fig
- Startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat appnot Fig
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Fig
- Shut down on 1 September 2024. Amazon acquired Fig in August 2023 and folded it into Amazon Q Developer, which now carries the terminal autocomplete
- The standalone desktop app is no longer available or supported
- The completion specs remain open source on GitHub, but the product that consumed them is gone
Height
- It is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
- The 2024 relaunch as Height 2.0 reoriented the product around AI agents and changed workflows customers had already built on, which is the clearest available evidence of how much the product may be re-shaped again under you.
- The ecosystem is small next to Jira, Linear and Asana: fewer third-party integrations, no consultancy market, and far less written material to search when something behaves unexpectedly, so support questions go to the vendor and wait.
- The automation only pays off if tasks contain enough substance for a model to work with; on a team whose tickets are two-word titles, the agents have nothing to triage or deduplicate and the product reduces to an ordinary tracker at a premium.
- Task content is processed by hosted large language models, so a security review becomes a question about subprocessors and data handling, and there is no self-hosted or on-premises deployment to fall back on if the answer is unacceptable.
- There is no widely used two-way synchronisation with Jira, so an organisation where one team adopts Height and the rest stay on Jira ends up with two systems of record and manual reconciliation between them.
Pricing, plan by plan
Fig
FreeNo published plan breakdown. See the Fig review.
Height
FreeNo published plan breakdown. See the Height review.
Which should you pick?
Choose Height if
- You need autonomous triage.
- You want to start without paying.
- You also want duplicate detection.
Questions people ask
- Is Fig or Height better?
- Neither clearly leads. Fig starts at Free and Height at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Fig or Height?
- Fig starts at Free and Height at Free.
- Does Fig or Height run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Fig for free?
- Both have a free tier, so you can try either at no cost before committing.
- What can Fig do that Height cannot?
- Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat.
Answered from the vendors’ own pages
Height: How is this different from Jira automation?
Jira automation is rule-based: you define a trigger and an action. Height's agents read the content of tasks and act on judgement, such as recognising that two tickets describe the same bug, which no rule can express.
Height: Can we self-host it?
No. It is software as a service only, with no on-premises or private-cloud deployment. If your requirements rule out a hosted tracker, this is not a candidate.
Height: What happens to our data if the company fails?
You would need an export and a migration to another tool. This is the standard risk with a single-product startup, and it is worth confirming the export path covers task history, comments and custom fields before committing to it.
Height: Does it work for non-engineering teams?
Yes, the views and custom fields are generic enough for marketing, operations or support queues. Its integrations, though, are aimed at software teams, so a non-engineering team gets less of the surrounding value.
Height: Do the AI features need our tickets to be well written?
In practice, yes. Triage, deduplication and attribute maintenance work from what is written in the task, so the return is much higher on a team that already writes descriptive tickets than on one that does not.
Related pages
Other head to heads
- Fig vs Visual Studio Code
- Fig vs ESLint
- Fig vs Turborepo
- Fig vs pnpm
- Fig vs Sweep
- Fig vs Cody
- Fig vs Warp
- Fig vs Keycloak
- Fig vs Rust
- Fig vs CodeSandbox
- Fig vs Vite
- Fig vs Daytona
- Fig vs Visual Studio
- Fig vs Xlinesoft
- Fig vs Ona (formerly Gitpod)
- Fig vs Sourcegraph
- Fig vs Asana
- Fig vs ClickUp
- Fig vs Linear
- Fig vs Monday.com
- Fig vs Shortcut
- Fig vs Coda
- Fig vs Intercom
- Fig vs Attio
- Fig vs Jenkins
- Fig vs Kubernetes
- Fig vs Notion
- Fig vs Figma
- Fig vs Site24x7
- Fig vs StatusCake
- Fig vs Storybook
- Fig vs WebStorm
- Fig vs Zabbix Cloud
- Height vs Visual Studio Code
- Height vs ESLint
- Height vs Turborepo
- Height vs pnpm
- Height vs Sweep
- Height vs Cody
- Height vs Warp
- Height vs Keycloak
- Height vs Rust
- Height vs CodeSandbox
- Height vs Vite
- Height vs Daytona
- Height vs Visual Studio
- Height vs Xlinesoft
- Height vs Ona (formerly Gitpod)
- Height vs Sourcegraph
- Height vs Asana
- Height vs ClickUp
- Height vs Linear
- Height vs Monday.com
- Height vs Shortcut
- Height vs Coda
- Height vs Intercom
- Height vs Attio
- Height vs Jenkins
- Height vs Kubernetes
- Height vs Notion
- Height vs Figma
- Height vs Site24x7
- Height vs StatusCake
- Height vs Storybook
- Height vs WebStorm
- Height vs Zabbix Cloud