Softwr

Developer Tools · head to head

Cortex vs ESLint

Cortex logo

Cortex

Developer Tools

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

From
On request
Rated
-
ESLint logo

ESLint

Developer Tools

Find and fix problems in JavaScript code

From
Free
Rated
-

The short version

  • Only ESLint 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.; ESLint slow performance on large codebases compared to newer tools like Oxlint and Biome
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cortex and ESLint actually diverge.

Attributes where Cortex and ESLint differ
AttributeCortexESLint
Starting priceOn requestFree
Pricing modelquoteUnknown
Free tierNoYes
PlatformsWeb, APIBrowser-based JavaScript, Node.js, Any JavaScript environment
FoundedUnknown2019

Identical on both: user rating (Not yet rated), category (Developer Tools).

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 ESLint

Nothing recorded that Cortex does not also cover.

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 ESLint
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot ESLint
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot ESLint
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot ESLint

ESLint

  • Statically analysing JavaScript and JSX to find problems before runtimenot Cortex
  • Automatically fixing issues with syntax-aware rewritesnot Cortex
  • Enforcing a consistent code style across a teamnot Cortex
  • Running as a CI step to block non-conforming codenot Cortex
  • Writing custom rules for project-specific conventionsnot 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.

ESLint

  • Slow performance on large codebases compared to newer tools like Oxlint and Biome
  • Complexity in configuration from scratch, particularly for TypeScript support
  • Limited built-in TypeScript support, requiring separate parsers and coordination with new TypeScript features

Pricing, plan by plan

Cortex

On request
  • Cortex$undefined/year
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

ESLint

Free

No published plan breakdown. See the ESLint review.

Which should you pick?

Choose Cortex if

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

Choose ESLint if

  • You want to start without paying.
  • You work on Browser-based JavaScript, Node.js, Any JavaScript environment.

Questions people ask

Is Cortex or ESLint better?
Neither clearly leads. Cortex starts at On request and ESLint at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or ESLint?
ESLint has a free tier; the other does not. Paid plans start at On request for Cortex and Free for ESLint.
Does Cortex or ESLint run on more platforms?
Cortex runs on Web, API. ESLint runs on Browser-based JavaScript, Node.js, Any JavaScript environment.
Can I use ESLint for free?
Yes. ESLint 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 ESLint is typically brought in for.
What can Cortex do that ESLint cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates.

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.

ESLint: Does ESLint automatically fix code issues?

Many problems ESLint finds can be automatically fixed via the --fix flag. ESLint fixes are syntax-aware so you won't experience errors introduced by traditional find-and-replace algorithms.

Source
Cortex: Is pricing published?

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

ESLint: How much does ESLint cost?

ESLint is completely free and open-source software maintained by the OpenJS Foundation. The project accepts voluntary donations from sponsors.

Source
Cortex: Can it self-host?

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

ESLint: Can I write custom ESLint rules?

Yes. You can develop custom rules that work alongside built-in functionality through ESLint's plugin system, allowing complete customization for your project needs.

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.

Share

Related pages

Other head to heads