Softwr

Technology · head to head

Height vs LiquidPlanner

H

Height

Technology

A project management tool from a small independent vendor that uses AI agents to handle routine ticket maintenance.

From
Free
Rated
-
LiquidPlanner logo

LiquidPlanner

Project Management

Predictive project management

From
On request
Rated
-

The short version

  • Only Height has a free tier, so it costs nothing to try first.
  • Each has a real cost: 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.; LiquidPlanner rebranded to Tempo Portfolio Manager; the pricing page shows no published figures, only an early access sign-up
  • They diverge on capability: Height covers Autonomous triage, LiquidPlanner covers Predictive scheduling.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Height and LiquidPlanner actually diverge.

Attributes where Height and LiquidPlanner differ
AttributeHeightLiquidPlanner
Starting priceFreeOn request
Pricing modelUnknownsubscription
Free tierYesNo
CategoryTechnologyProject Management
Founded20182006

Identical on both: 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 Height

  • Autonomous triage
  • Duplicate detection
  • Attribute maintenance
  • Per-task chat
  • Multiple views
  • Developer integrations
  • Custom fields and filters
  • Public API

Only in LiquidPlanner

  • Predictive scheduling
  • Resource management
  • Time tracking
  • Analytics
  • Workload management
  • Jira
  • Salesforce
  • Slack

What people use each for

The jobs each tool is most often brought in to do.

Height

  • A product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has timenot LiquidPlanner
  • Teams leaving Jira because its configuration and administration cost more attention than the tracking is worthnot LiquidPlanner
  • A support or intake queue where incoming requests need categorising and deduplicating before anyone can plan themnot LiquidPlanner
  • Startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat appnot LiquidPlanner

LiquidPlanner

  • Productivitynot Height
  • Collaborationnot Height
  • Task managementnot Height
  • Organizationnot Height

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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.

LiquidPlanner

  • Rebranded to Tempo Portfolio Manager; the pricing page shows no published figures, only an early access sign-up

Pricing, plan by plan

Height

Free

No published plan breakdown. See the Height review.

LiquidPlanner

On request
  • Essentials$15/month
    • Project management
    • Basic scheduling
  • Professional$25/month
    • Predictive scheduling
    • Resource management
    • Analytics

Which should you pick?

Choose Height if

  • You need autonomous triage.
  • You want to start without paying.
  • You also want duplicate detection.

Choose LiquidPlanner if

  • You need predictive scheduling.
  • You also want resource management.

Questions people ask

Is Height or LiquidPlanner better?
Neither clearly leads. Height starts at Free and LiquidPlanner at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Height or LiquidPlanner?
Height has a free tier; the other does not. Paid plans start at Free for Height and On request for LiquidPlanner.
Does Height or LiquidPlanner run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Height for free?
Yes. Height has a free tier, so you can try it without paying. LiquidPlanner starts at On request.
What is Height best used for?
Height is most often used for a product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has time, teams leaving jira because its configuration and administration cost more attention than the tracking is worth, a support or intake queue where incoming requests need categorising and deduplicating before anyone can plan them, startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat app. Of those, a product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has time and teams leaving jira because its configuration and administration cost more attention than the tracking is worth are not what LiquidPlanner is typically brought in for.
What can Height do that LiquidPlanner cannot?
Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat. LiquidPlanner covers Predictive scheduling, Resource management, Time tracking, Analytics.

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.

LiquidPlanner: How is Tempo timesheets pricing calculated for my organization?

Pricing is per-user per month and scales based on organization size. For 1-10 users: $1.00/user; 11-100 users: $5.21/user; 101-250 users: $3.66/user; scaling down to $0.25-$0.39/user for organizations with 5,000+ users.

Source
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.

LiquidPlanner: What license matching requirement exists for Tempo?

Your Tempo license size must match your Jira license size, with a user defined as anyone who can log into Jira.

Source
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.

LiquidPlanner: Is there a free trial for Tempo timesheets?

Yes, Tempo offers a free trial available through the Atlassian Marketplace.

Source
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.

LiquidPlanner: What deployment options are available for Tempo?

Both Cloud and Data Center deployment options are offered, with annual billing available.

Source
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.

Share

Related pages

Other head to heads