Softwr

Developer Tools · head to head

GitLab CI/CD vs Height

GitLab CI/CD logo

GitLab CI/CD

Developer Tools

Automatically build, test, deploy, and monitor your applications with GitLab CI/CD

From
Free
Free plan
Yes
Full reviewWebsite
H

Height

Technology

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

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Each has a real cost: GitLab CI/CD compute minute quotas for Premium and Ultimate tiers not disclosed in documentation; 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.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which GitLab CI/CD and Height actually diverge.

Attributes where GitLab CI/CD and Height differ
AttributeGitLab CI/CDHeight
Pricing modelfreemiumUnknown
CategoryDeveloper ToolsTechnology
FoundedUnknown2018

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

Nothing recorded that Height does not also cover.

Only in Height

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

What people use each for

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

GitLab CI/CD

  • Reducing open source project infrastructure costs with public project discountsnot Height
  • Enforcing monthly CI/CD spending limits and quota notificationsnot Height
  • Allocating compute minutes to open source contributors affordablynot Height
  • Forecasting CI/CD spending patterns across multiple projectsnot Height
  • Providing private runners for cost control without owning infrastructurenot Height

Height

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

Where each one falls short

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

GitLab CI/CD

  • Compute minute quotas for Premium and Ultimate tiers not disclosed in documentation
  • Additional compute minutes beyond quota incur charges; exact pricing not specified

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.

Pricing, plan by plan

GitLab CI/CD

Free
  • FreeFree
    • 400 compute minutes per month for free tier namespaces
    • Linux x86-64 runners at 1x cost factor
  • Premium$null/tiered
    • Higher monthly compute minute quotas than free tier
    • Additional compute minutes available for purchase
  • Ultimate$null/tiered
    • Highest monthly compute minute allocations
    • Additional compute minutes available for purchase

Height

Free

No published plan breakdown. See the Height review.

Which should you pick?

Choose GitLab CI/CD if

  • You want to start without paying.
GitLab CI/CD review

Choose Height if

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

Questions people ask

Is GitLab CI/CD or Height better?
Neither clearly leads. GitLab CI/CD starts at Free and Height at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, GitLab CI/CD or Height?
GitLab CI/CD starts at Free and Height at Free.
Does GitLab CI/CD or Height run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use GitLab CI/CD for free?
Both have a free tier, so you can try either at no cost before committing.
What is GitLab CI/CD best used for?
GitLab CI/CD is most often used for reducing open source project infrastructure costs with public project discounts, enforcing monthly ci/cd spending limits and quota notifications, allocating compute minutes to open source contributors affordably, forecasting ci/cd spending patterns across multiple projects. Of those, reducing open source project infrastructure costs with public project discounts and enforcing monthly ci/cd spending limits and quota notifications are not what Height is typically brought in for.
What can GitLab CI/CD do that Height cannot?
Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat.

Answered from the vendors’ own pages

GitLab CI/CD: How many GitLab CI compute minutes does the free tier include?

The free tier of GitLab CI includes 400 compute minutes per month for free tier namespaces on GitLab.com.

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

GitLab CI/CD: What is the cost factor for different GitLab CI runner types?

Linux x86-64 small runners cost 1x; medium runners cost 2x; large runners cost 3x. macOS and Windows runners have cost factors of 6-12x and are in beta status.

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.

GitLab CI/CD: Do public open-source projects get discounts on GitLab CI compute minutes?

Public open-source projects receive a 0.5x discount on compute minutes. Public forks of GitLab open-source projects receive a 0.008x discount.

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.

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

More on GitLab CI/CD

More on Height

Keep looking

Other head to heads