Softwr

Developer Tools · head to head

Cortex vs Trunk Code Quality

Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Free plan
No
Trunk Code Quality logo

Trunk Code Quality

Developer Tools

Metalinter that runs and manages linters, formatters and security scanners

From
Free
Free plan
Yes

The short version

  • Trunk Code Quality is free; Cortex prices on request.
  • Only Cortex lists service catalogue; only Trunk Code Quality lists version pinning through trunk.yaml.
  • Where Trunk Code Quality falls short: private repositories with more than five active committers need a paid licence.
  • Prices and features on this page were last checked on 20 November 2026.

How do Cortex and Trunk Code Quality differ?

Cortex and Trunk Code Quality differ on starting price (On request against Free), pricing model (Quote against Freemium) and free tier (No against Yes). Only the attributes on which Cortex and Trunk Code Quality actually diverge.

Attributes where Cortex and Trunk Code Quality differ
AttributeCortexTrunk Code Quality
Starting priceOn requestFree
Pricing modelQuoteFreemium
Free tierNoYes
PlatformsWeb, APImacOS, Linux, Windows

Identical on both: category (Developer Tools).

Not yet recorded: founded for Cortex.

Which features does each one have?

They share no listed features; 8 appear only for Cortex and 8 only for Trunk Code Quality. 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 Trunk Code Quality

  • Installs and runs over 100 linters and formatters
  • Version pinning through trunk.yaml
  • Hold the Line checks on new changes only
  • Background daemon that precomputes results
  • VS Code and Neovim editor integration
  • GitHub integration for pull request checks
  • Security scanning tools such as trivy and gitleaks
  • Runs in any CI environment

What is each one used for?

Trunk Code Quality is most often brought in for running one lint command across a polyglot repository. 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 Trunk Code Quality
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Trunk Code Quality
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Trunk Code Quality
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Trunk Code Quality

Trunk Code Quality

  • Running one lint command across a polyglot repositorynot Cortex
  • Gradually fixing legacy code with Hold the Linenot Cortex
  • Pinning linter versions across a teamnot Cortex
  • Enforcing the same checks locally and in CInot Cortex
  • Adding security scanners to pull requestsnot Cortex

Where do Cortex and Trunk Code Quality fall short?

Trunk Code Quality's most cited limit: private repositories with more than five active committers need a paid licence. 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

Trunk Code Quality

  • Private repositories with more than five active committers need a paid licence
  • Paid Team and Enterprise prices are not published; quotes come from sales
  • Core CLI is closed source, with only plugins and the GitHub Action under MIT
  • Results depend on the underlying linters, so rule coverage is not Trunk's own

How much do Cortex and Trunk Code Quality cost?

Cortex is priced on request; Trunk Code Quality is free to use. Plan by plan below, from each vendor's own pricing page.

Cortex

On request
  • CortexOn request
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

Trunk Code Quality

Free
  • Free (up to 5 active committers on private repos)Free
  • Team (per seat)On request
  • Enterprise (annual site licence)On request

Which should you pick?

Choose Cortex if

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.

Choose Trunk Code Quality if

  • You need installs and runs over 100 linters and formatters.
  • You want to start without paying.
  • You work on macOS, Linux, Windows.
  • You also want version pinning through trunk.yaml.

Questions people ask

Is Cortex or Trunk Code Quality better?
Neither clearly leads. Cortex starts at On request and Trunk Code Quality at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Trunk Code Quality?
Trunk Code Quality has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Trunk Code Quality.
Does Cortex or Trunk Code Quality run on more platforms?
Cortex runs on Web, API. Trunk Code Quality runs on macOS, Linux, Windows.
Can I use Trunk Code Quality for free?
Yes. Trunk Code Quality 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 Trunk Code Quality is typically brought in for.
What can Cortex do that Trunk Code Quality cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Trunk Code Quality covers Installs and runs over 100 linters and formatters, Version pinning through trunk.yaml, Hold the Line checks on new changes only, Background daemon that precomputes results.

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.

Trunk Code Quality: What does Trunk Code Quality do?

It is a metalinter that installs, pins and runs third party linters, formatters and security scanners from one CLI. A background daemon precomputes results for editor annotations.

Source
Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

Trunk Code Quality: Is Trunk Code Quality free?

Public and open source repositories have no stated usage limit, and private repositories with five or fewer active committers can use the CLI at no cost. Larger private teams need a paid licence.

Source
Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

Trunk Code Quality: Which operating systems are supported?

The launcher supports macOS and Linux. Windows is supported from CLI version 1.13.0, using git-bash, msys2 or a PowerShell launcher.

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

Trunk Code Quality: How many linters does it support?

The supported linters page claims over 100 linters and formatters. They cover many languages plus infrastructure, security, SQL and Markdown tooling.

Source
Share

Related pages

Other head to heads