Height app alternatives are hosted issue trackers built for software teams, project tools that live inside GitHub, trackers you can host yourself, all-in-one work platforms, and flat-priced project apps that don't charge per person. For a product and engineering team, start with a fast issue tracker and only widen the search if non-technical colleagues need the same tool.
Height sold itself as a task and project tracker for product and engineering teams. Its site at height.app wasn't responding when this guide was last updated, so check its current status directly before you plan around it. Either way, the job you're filling is the same: tracking issues and projects for a team that ships software. A similar issue tracker, Kitemaker, says on its own site that it was acquired and its service discontinued, which is a fair reminder that the tool you pick next should make it easy to take your data with you.
Which one fits your team: five situations
A small product team that wants speed. Go for a hosted issue tracker designed for software teams. They're designed around engineering work from the start, so you won't spend a week bending a general tool into shape. For a young company, my guide to the best project management tool for startups goes further on that stage.
Developers who live in GitHub. A project tool that sits inside GitHub keeps boards next to the code and pull requests, so engineers don't open another tab. The trade-off is that people outside engineering will find it awkward.
A team that has to own its data. Pick a tracker with a self-hosted edition. You run it on your own servers, which answers security questions and protects you if a vendor ever closes its doors, at the cost of looking after updates yourself.
A company where marketing, support and ops share the board. An all-in-one work platform, with tasks, docs and AI in one workspace, will serve mixed teams better than a pure issue tracker, even if engineers find it slower.
A team about to grow fast. Look hard at flat-priced project tools. When the bill doesn't rise with every new hire, a hiring plan doesn't turn into a software budget meeting.
Issue trackers built for software teams
Linear
Fast-moving software teams get a hosted tool for issue tracking and product planning that's built around speed.
Shortcut
Boards, roadmaps and an AI agent all sit inside this hosted project tracker made for software teams.
Plane
Project and knowledge management in one place, which you can run in the vendor's cloud or host on your own servers.
Zenhub
Engineers who'd rather never leave GitHub get project management that lives right inside it.
Jira
Atlassian's issue and project tracker serves software teams and others, and now ships with AI agents built in.
Work platforms and project tools for mixed teams
ClickUp
One workspace for tasks, docs and AI, aimed at teams that want every kind of work kept in a single place.
Asana
Larger and less technical teams run their work and projects here, with AI teammates now part of the platform.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Basecamp
A project tool for general team work across a whole company, a closer match for mixed teams than for engineering ticket queues.
Backlog
Nulab's tool combines project management with issue tracking, so tasks and bugs sit side by side for the whole team.
Per seat or flat fee: what drives the bill
Per-seat pricing is the norm for issue trackers and work platforms: you pay a monthly amount for every person with an account, and some quote that per-person figure on yearly billing, so check which billing period the headline assumes. Where there's a free plan, it caps something, whether that's members, projects or features, so read the limits rather than the word free.
Some project tools charge a flat fee instead. Flat packages against per seat tracking is the question in how Basecamp and Linear compare. One sells plans by tier with no per-user charge at all, and another sets one flat monthly price per plan, whatever your headcount. The per-person prices on the per-seat trackers here sit in a fairly narrow, modest band, so the bigger question is how many seats you'll pay for, not which vendor shaves a little off each one. For a team of five, per-seat tools can come out cheaper. For a team of forty, flat pricing can win by a wide margin. The only way to know is to price your own headcount on each vendor's pricing page, including the people you expect to hire next year, and to check whether guests, clients or read-only viewers count as seats.
Getting your data out again
Whichever way it's hosted, the thing I'd check before signing up is the exit. A tracker holds years of decisions, so a tool that can't hand them back cleanly is a risk, however pleasant it feels to use day to day.
Before you sign up, open each tool's export options. If you can't pull every issue, comment and attachment out in a standard format, you're one acquisition away from another migration.
Agents in the tracker
Issue trackers now sell AI agents as a feature, describing themselves as systems for teams and agents rather than just teams. In practice that means an assistant working inside the tracker alongside your team, so ask each vendor exactly what its agent does on its own and what it won't touch. I'd judge a tracker on how fast humans can use it first and treat the agent as a bonus. For a wider look at where AI fits into project work, my guide to AI project management tools covers the options beyond software teams.
Do you make issue trackers or project management tools for software teams? Tool makers can ask to be considered for a featured place on this list.
A trial day with real tickets
Export everything you can from your current tracker first, ideally as CSV or JSON, and keep a copy somewhere safe. Pick your two front runners and import the same slice into each: one active project, its open issues, a handful of closed ones and anything with attachments. Check that assignees, labels, status and comments survived.
Then ask two engineers and one non-engineer to run a normal day in each tool. Time how long it takes to file a bug, find last week's issue and move a ticket through to done. The tool that wins that afternoon is the one I'd back to still be in use in six months, whatever the feature grid says. If you'd like a broader comparison before deciding, my roundup of the best issue tracking software covers trackers outside the software-team niche too.
Once you've chosen, pick a cut-over date at the start of a sprint, freeze new tickets in the old tool from that morning, and run a final full export the night before. Links to old issues live in commit messages, pull requests and chat threads, so leave the old tracker readable until those links stop being clicked.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.


