Height

Height was an AI-native project management tool built for product and engineering teams. Founded in 2018 and based in New York, it positioned itself as a chat-centric workspace with a reasoning engine at its core, aiming to automate the tedious, repetitive parts of running software projects rather than just displaying tasks in a nicer interface. Its autonomous features included keeping product documentation up to date as decisions were made, pruning and maintaining the backlog automatically, triaging bugs by prioritizing and assigning them, and drafting scheduled progress updates and standups. The pitch was that a project manager spends much of their time on legwork — grooming the backlog, sorting bugs, writing status reports — and that an AI reasoning engine could take on that legwork so people focused on the actual product. It is important to state plainly that Height's product was shut down on September 24, 2025, so it is no longer available for new adoption.

Height matters as a marker of a category shift, even though the product itself is gone. It drew a distinction that is worth understanding: AI-native versus AI-added. Most project tools bolted AI features onto an existing design as an add-on — a summarizer here, a suggestion there. Height was built the other way around, with an AI reasoning engine as the foundation and the interface arranged around it, so automation was meant to be the core of the tool rather than a feature drawer. Whether or not any single AI-native tool survives, that architectural idea — building the product around the model instead of decorating an old product with model features — is the more durable lesson. Height is a useful concrete example of what AI-native was trying to be, and its shutdown is an equally useful reminder that being early and architecturally interesting does not guarantee a business survives.

Height differed from traditional project tools like Asana, Jira, Linear, and Basecamp in what it treated as the center of the product. Those tools are structures for humans to organize work — boards, lists, tickets, dependencies — with people doing the organizing. Height tried to shift some of that organizing onto an AI engine, automating the backlog grooming, bug triage, and status writing that people normally do by hand. So the contrast was not mainly about features but about who does the routine work: the human, in a traditional tool, or the machine, in Height's vision. That ambition is exactly what made it interesting and also what made it hard — automating judgment-laden project chores reliably is a genuinely difficult problem, and Height's shutdown suggests how difficult.

Height also drew a sharper line against AI-added tools, and this is the distinction it cared most about. Many established project platforms added AI features — summaries, draft updates, smart suggestions — onto their existing designs. Height argued that bolting AI onto a human-centric tool is fundamentally different from building the tool around the AI in the first place, and it called itself AI-native to stake that claim. The honest way to place Height today is as an early, architecturally ambitious attempt at AI-native project management that did not survive as a product but illustrated a real idea. For a team choosing a live tool now, the practical lesson is to look for genuine AI-native design where automation is core, and to weigh the maturity and staying power of any such tool — because architectural elegance and an early lead are not the same as durability.

Even though Height is no longer available, the idea it represented is worth reading correctly, because AI-native tooling is a live theme across software. The useful distinction to carry forward is AI-native versus AI-added: a tool where the AI reasoning engine is the foundation and the workflow is built around it, versus one where AI features were added to an existing human-centric product. When evaluating any project or work tool that claims to be AI-powered, press on which of these it really is, because the difference shows up in whether the automation feels central and reliable or peripheral and cosmetic. Height is a concrete reference point for what the native approach was aiming at — automating the backlog, the triage, and the reporting rather than decorating them.

Read the cautionary side just as clearly. Height's shutdown in 2025 is a reminder that being early and architecturally interesting does not guarantee a product endures, and that automating judgment-heavy project work reliably is genuinely hard. So the failures to avoid are treating any AI-native label as proof of quality, adopting an early tool without weighing its maturity and staying power, and assuming automation can replace human judgment on the parts of project management that actually require it. The disciplined takeaway is to value the AI-native architectural idea, evaluate whether a given tool truly embodies it, and stay clear-eyed that the category is young — some tools will not last, as Height did not, and that risk belongs in any adoption decision.

Height — an AI-native project management tool for product and engineering teams, founded in 2018 and discontinued in 2025, that used a reasoning engine to automate routine project chores.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where height is a core concern: