Height shut down: what to move to

Height, the project tool that described itself as autonomous project management, ended service on 24 September 2025. If your team was on it, you need a new place for your tasks, and the right one depends mostly on where your code and issues live.

We make Gitsu, a client for GitHub Projects, so one option below is ours. This page gives the facts about Height's shutdown, then the realistic destinations and where each falls short.

When did the Height app shut down?

Height's service ended on 24 September 2025. Its founder, Michael Villar, wrote on height.app that after three and a half years of being publicly available the company had decided to discontinue operations six months after the notice, with that date as the final day of service. We read the notice in the Internet Archive on 24 October 2026. The notice does not name a successor product.

Because the service is gone, you cannot export from it now. If you saved an export before the end date, keep it. If you did not, the sections below are about starting your next tracker, not migrating from a running one. We did not test any Height export format, so we make no claim about what an export contains.

What did Height do, and what do you need to replace?

Height described itself as a collaboration tool with autonomous project management, built for product teams. Its archived marketing page listed live collaboration in Spreadsheet, Kanban, Gantt and Calendar views, a chat interface for discussing tasks in context, a customisable data model and shortcuts, and automation aimed at backlog upkeep, spec updates and bug triage.

That gives you a checklist for any replacement. Decide which of these you actually used:

1. A task list or board for the daily backlog.
2. Gantt or calendar views for planning.
3. Chat attached to tasks.
4. Autonomous features such as automatic triage and spec updates.
5. A custom data model.

Most replacements cover the first and some of the second. Few cover chat or the autonomous features the way Height did, so decide early whether you will miss them.

Where can a Height team go?

The choice splits on whether the work should stay outside GitHub or move into it. Prices below were read on 24 October 2026 unless noted.

Linear's pricing page lists Basic at $10 per user per month and Business at $16, with cycles, a triage inbox and initiatives; see Linear vs GitHub Issues. Plane is open source and offers cloud and self-hosted plans on its pricing page; our research did not test its GitHub integration. Zenhub's Free plan allows 250 issues and two repositories, and its Teams plan was listed at $4.99 per user per month billed yearly on 24 October 2026; see Gitsu compared with Zenhub. A side-by-side is in the roundup of GitHub Projects tools, and Zenhub vs Linear covers the two paid options head to head.

What does Height do better than the options above?

Height did several things none of them match, and a fair page should say so. It had a chat experience for discussing projects in context, so discussion and activity sat in one place. It offered Spreadsheet, Kanban, Gantt and Calendar over the same tasks in one workspace, with live collaboration. It marketed autonomous features that triaged bugs and kept backlogs and specs current without being asked. And it let a team define its own attributes and data model.

Of the four options above, Linear covers fast keyboard-first planning and a triage queue, Plane covers customisation, and none replaces Height's built-in autonomous behaviour. GitHub Projects with Gitsu covers none of the chat or the Gantt and calendar views. If those were why your team used Height, expect to give some up, or to pair a chat tool with the tracker you choose. Gitsu's own agent route is different in kind: its paid desktop app bundles an MCP server so a coding agent you already use can read and update the board, and nothing there triages for you on its own.

Should a team on GitHub move to GitHub Projects instead?

Yes, if your code and pull requests are in GitHub and you were running Height beside them. Moving tasks into GitHub issues removes the second system, so nobody reconciles a tracker with the repository. GitHub Projects is free with every GitHub account and has board, table and roadmap layouts. What a Height team usually misses there is speed and filtering, which is what Gitsu adds.

Gitsu is a web app and a native macOS app that read and write your GitHub boards directly. It gives you dense lists with grouping, a command palette over every write (⌘K), nested AND/OR filters across field types, bulk edit and a roadmap drawn from date or iteration fields. Every change is an ordinary change to the GitHub project, so teammates can keep using github.com. The web app is free; paid macOS Seats add desktop agents and MCP access, with current prices on the pricing page.

What does Gitsu not do for a Height team?

Gitsu does not import from Height. Its only importer, in the web app, is for Linear, so it works on a GitHub Projects board once the tasks are already GitHub issues, and GitHub issue creation goes through its CLI or API. It has no built-in project chat (its paid desktop app has an agent panel for running coding agents beside the board), no Gantt or calendar view, no automatic triage, no sprint rollover, no burndown charts, no notifications inbox and no mobile app. It shows one project at a time and loads up to 2,000 items per project, telling you when it stopped. It is a client for GitHub, so it does not replace a standalone tracker for work that has no GitHub issue.

Which should you pick?

Pick by where the work belongs. Choose Linear or Plane if you want a standalone tracker and your team will move there together. Choose Zenhub if you plan in sprints on GitHub issues and need burndown and velocity. Choose GitHub Projects with Gitsu if your issues and pull requests are in GitHub and you want one place for them, worked from a fast keyboard-driven client.

To try that route, create GitHub issues for the work you still need, open the project in the free Gitsu web app, apply a filter you use for triage and run a bulk edit. Follow getting started with the Gitsu web app. Within one session you will know whether the daily loop works for your team, before you commit to a second tracker.