Softwr

Technology · head to head

Height vs Selenium

H

Height

Technology

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

From
Free
Rated
-
Selenium logo

Selenium

Testing

Browser automation framework and the W3C WebDriver standard

From
Free
Rated
-

The short version

  • 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.; Selenium flaky tests are the standing complaint: explicit waits and synchronisation are the tester’s job, where newer tools handle it automatically
  • They diverge on capability: Height covers Autonomous triage, Selenium covers W3C WebDriver.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Height and Selenium actually diverge.

Attributes where Height and Selenium differ
AttributeHeightSelenium
Pricing modelUnknownOpen source, no licence fee
PlatformsWebLinux, macOS, Windows, Web
CategoryTechnologyTesting
Founded2018Unknown

Identical on both: starting price (Free), free tier (Yes), 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 Selenium

  • W3C WebDriver
  • Many language bindings
  • Selenium Grid
  • Broad browser support

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 Selenium
  • Teams leaving Jira because its configuration and administration cost more attention than the tracking is worthnot Selenium
  • A support or intake queue where incoming requests need categorising and deduplicating before anyone can plan themnot Selenium
  • Startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat appnot Selenium

Selenium

  • Cross-browser testing where Safari and legacy browsers must be coverednot Height
  • Teams whose test suites are written in Java or C# rather than JavaScriptnot Height
  • Distributing a large suite across a grid of machinesnot 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.

Selenium

  • Flaky tests are the standing complaint: explicit waits and synchronisation are the tester’s job, where newer tools handle it automatically
  • Setup involves drivers, versions and grid infrastructure that Playwright and Cypress bundle away
  • Slower to run than tools that talk to browsers over a debugging protocol rather than WebDriver

Pricing, plan by plan

Height

Free

No published plan breakdown. See the Height review.

Selenium

Free
  • SeleniumFree
    • Full functionality
    • Unlimited tests
    • Community support

Which should you pick?

Choose Height if

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

Choose Selenium if

  • You need w3c webdriver.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Web.
  • You also want many language bindings.

Questions people ask

Is Height or Selenium better?
Neither clearly leads. Height starts at Free and Selenium at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Height or Selenium?
Height starts at Free and Selenium at Free.
Does Height or Selenium run on more platforms?
Height runs on Web. Selenium runs on Linux, macOS, Windows, Web.
Can I use Height for free?
Both have a free tier, so you can try either at no cost before committing.
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 Selenium is typically brought in for.
What can Height do that Selenium cannot?
Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat. Selenium covers W3C WebDriver, Many language bindings, Selenium Grid, Broad browser support.

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.

Selenium: Is Selenium free?

Yes, open source with no licence fee. Paid costs come from grid infrastructure or services like BrowserStack.

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.

Selenium: Selenium or Playwright?

Playwright handles waiting automatically and is faster to set up, which removes most flakiness complaints. Selenium wins on language breadth, browser coverage including Safari, and existing suites you already have.

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.

Selenium: Is Selenium still relevant?

Yes. Its WebDriver protocol is a W3C standard implemented by every major browser, and very large existing suites are not rewritten cheaply.

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.

Share

Related pages

Other head to heads