Developer Tools · head to head
Cortex vs Height
Cortex
Developer Tools
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
- From
- On request
- Free plan
- No
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
The short version
- Only Height has a free tier, so it costs nothing to try first.
- Each has a real cost: Cortex pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.; 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.
- They diverge on capability: Cortex covers Service catalogue, Height covers Autonomous triage.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which Cortex and Height actually diverge.
Identical on both: 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 Cortex
- Service catalogue
- Scorecards
- Initiatives
- Self-service templates
- Query language
- Eng intelligence
- Integrations layer
- On-call and ownership mapping
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.
Cortex
- A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Height
- An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Height
- Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Height
- Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Height
Height
- A product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has timenot Cortex
- Teams leaving Jira because its configuration and administration cost more attention than the tracking is worthnot Cortex
- A support or intake queue where incoming requests need categorising and deduplicating before anyone can plan themnot Cortex
- Startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat appnot Cortex
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Cortex
- Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
- The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything.
- Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue.
- It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves.
- Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract.
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
Cortex
On request- Cortex$undefined/year
- Service catalogue and ownership mapping
- Scorecards and initiatives
- Self-service templates
Height
FreeNo published plan breakdown. See the Height review.
Which should you pick?
Choose Cortex if
- You need service catalogue.
- You work on Web, API.
- You also want scorecards.
Choose Height if
- You need autonomous triage.
- You want to start without paying.
- You also want duplicate detection.
Questions people ask
- Is Cortex or Height better?
- Neither clearly leads. Cortex starts at On request and Height at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Cortex or Height?
- Height has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Height.
- Does Cortex or Height run on more platforms?
- Cortex runs on Web, API. Height runs on Web.
- Can I use Height for free?
- Yes. Height has a free tier, so you can try it without paying. Cortex starts at On request.
- What is Cortex best used for?
- Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Height is typically brought in for.
- What can Cortex do that Height cannot?
- Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat.
Answered from the vendors’ own pages
Cortex: How is Cortex different from Backstage?
Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.
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.
Cortex: Is pricing published?
No. Cortex requires a sales conversation and prepares a custom proposal.
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.
Cortex: Can it self-host?
It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.
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.
Cortex: What is the main adoption risk?
Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.
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.
Related pages
Other head to heads
- Cortex vs Backstage
- Cortex vs OpsLevel
- Cortex vs Earthly
- Cortex vs Spacelift
- Cortex vs Atlantis
- Cortex vs Depot
- Cortex vs Nix
- Cortex vs SonarQube
- Cortex vs Keycloak
- Cortex vs Ona (formerly Gitpod)
- Cortex vs Vite
- Cortex vs Bazel
- Cortex vs Dagger
- Cortex vs Deep Code
- Cortex vs Deno
- Cortex vs Fig
- Cortex vs Frappe
- Cortex vs Git
- Cortex vs Asana
- Cortex vs ClickUp
- Cortex vs Linear
- Cortex vs Monday.com
- Cortex vs Shortcut
- Cortex vs Coda
- Cortex vs Intercom
- Cortex vs Attio
- Cortex vs Jenkins
- Cortex vs Kubernetes
- Cortex vs Notion
- Cortex vs Figma
- Cortex vs Site24x7
- Cortex vs StatusCake
- Cortex vs Storybook
- Cortex vs WebStorm
- Cortex vs Zabbix Cloud
- Height vs Backstage
- Height vs OpsLevel
- Height vs Earthly
- Height vs Spacelift
- Height vs Atlantis
- Height vs Depot
- Height vs Nix
- Height vs SonarQube
- Height vs Keycloak
- Height vs Ona (formerly Gitpod)
- Height vs Vite
- Height vs Bazel
- Height vs Dagger
- Height vs Deep Code
- Height vs Deno
- Height vs Fig
- Height vs Frappe
- Height vs Git
- Height vs Asana
- Height vs ClickUp
- Height vs Linear
- Height vs Monday.com
- Height vs Shortcut
- Height vs Coda
- Height vs Intercom
- Height vs Attio
- Height vs Jenkins
- Height vs Kubernetes
- Height vs Notion
- Height vs Figma
- Height vs Site24x7
- Height vs StatusCake
- Height vs Storybook
- Height vs WebStorm
- Height vs Zabbix Cloud