Softwr

Developer Tools · head to head

Cortex vs Dependabot

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
Dependabot logo

Dependabot

Developer Tools

GitHub's automated dependency alerts and update pull requests

From
Free
Free plan
Yes

The short version

  • Dependabot is a GitHub feature.
  • Dependabot starts at $4/mo; Cortex prices on request.
  • Only Cortex lists service catalogue; only Dependabot lists security update pull requests.
  • Where Dependabot falls short: runs through GitHub repositories only; code hosted elsewhere needs a different tool.
  • Prices and features on this page were last checked on 20 November 2026.

How do Cortex and Dependabot differ?

Cortex and Dependabot 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 Dependabot actually diverge.

Attributes where Cortex and Dependabot differ
AttributeCortexDependabot
Starting priceOn requestFree
Pricing modelQuoteFreemium
Free tierNoYes
PlatformsWeb, APIWeb

Identical on both: category (Developer Tools).

Which features does each one have?

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

  • Dependabot alerts for vulnerable dependencies
  • Security update pull requests
  • Version update pull requests
  • Grouped updates
  • dependabot.yml configuration
  • Auto-triage rules
  • GitHub Actions workflow updates
  • Notifications and weekly email digest

What is each one used for?

Dependabot is most often brought in for patching vulnerable npm or pip packages automatically. 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 Dependabot
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Dependabot
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Dependabot
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Dependabot

Dependabot

  • Patching vulnerable npm or pip packages automaticallynot Cortex
  • Keeping GitHub Actions versions currentnot Cortex
  • Scheduled dependency refreshes for application repositoriesnot Cortex
  • Triaging security alerts across an organisationnot Cortex

Where do Cortex and Dependabot fall short?

Dependabot's most cited limit: runs through GitHub repositories only; code hosted elsewhere needs a different tool. 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

Dependabot

  • Runs through GitHub repositories only; code hosted elsewhere needs a different tool
  • Alerts scan the default branch only and skip archived repositories
  • Assigning alerts needs a GitHub Code Security or Advanced Security licence
  • Security updates cannot fix a dependency if the change would break the dependency graph
  • Updates pause automatically when maintainers stop interacting with Dependabot pull requests

How much do Cortex and Dependabot cost?

Cortex is priced on request; Dependabot has a free plan, with paid plans from $4/mo. 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

Dependabot

Free
  • FreeFree
  • Team$4/mo
  • Enterprise$21/mo

Which should you pick?

Choose Cortex if

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

Choose Dependabot if

  • You need dependabot alerts for vulnerable dependencies.
  • You want to start without paying.
  • You also want security update pull requests.

Questions people ask

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

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.

Dependabot: What does Dependabot do?

It has three features: alerts about vulnerable dependencies, security updates that open pull requests to fix them, and version updates that keep dependencies current. Version updates are configured in a dependabot.yml file.

Source
Cortex: Is pricing published?

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

Dependabot: Is Dependabot free?

GitHub's pricing page lists Dependabot security and version updates in the Free, Team and Enterprise plans, priced at $0, $4 and $21 per user per month respectively. Custom auto-triage rules are included in Team and Enterprise only.

Source
Cortex: Can it self-host?

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

Dependabot: Which package ecosystems does Dependabot support?

GitHub's reference lists ecosystems including npm, pip, Maven, Gradle, Cargo, Go modules, Docker, NuGet, Composer, Bundler, Helm charts and GitHub Actions. The visible list was cut off, so check the reference for the full set.

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.

Dependabot: Where did Dependabot come from?

The dependabot-core repository says it began as Bump and Bump Core, created by two developers while they worked at GoCardless. It states that Dependabot became part of GitHub in 2019.

Source
Share

Related pages

Other head to heads