Softwr

Developer Tools · head to head

Cortex vs HashiCorp Vault

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
Full reviewWebsite
HashiCorp Vault logo

HashiCorp Vault

Cybersecurity

Manage secrets and protect sensitive data

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Only HashiCorp Vault 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.; HashiCorp Vault policies are written in HCL with no graphical user interface for policy management or editing
  • They diverge on capability: Cortex covers Service catalogue, HashiCorp Vault covers Secret storage.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cortex and HashiCorp Vault actually diverge.

Attributes where Cortex and HashiCorp Vault differ
AttributeCortexHashiCorp Vault
Starting priceOn requestFree
Pricing modelquoteopen-source
Free tierNoYes
PlatformsWeb, APILinux, Windows, Mac, Api
CategoryDeveloper ToolsCybersecurity
FoundedUnknown2014

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 HashiCorp Vault

  • Secret storage
  • Dynamic secrets
  • Encryption as a service
  • Identity-based access
  • Audit logging
  • Leasing and renewal
  • Secret engines
  • Auth methods

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

HashiCorp Vault

  • Secrets managementnot Cortex
  • Database credentialsnot Cortex
  • API keysnot Cortex
  • SSH accessnot Cortex
  • PKI and certificatesnot 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.

HashiCorp Vault

  • Policies are written in HCL with no graphical user interface for policy management or editing
  • Unsealing requires managing multiple key shares and coordinating a quorum of operators
  • Community Edition lacks enterprise features like namespaces and disaster recovery replication
  • Requires additional monitoring solutions for alerting and observability

Pricing, plan by plan

Cortex

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

HashiCorp Vault

Free
  • Open SourceFree
    • Secrets management
    • Encryption
    • Community support
  • Vault Enterprise$6000/year
    • Replication
    • HSM support
    • Advanced audit

Which should you pick?

Choose Cortex if

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

Choose HashiCorp Vault if

  • You need secret storage.
  • You want to start without paying.
  • You work on Linux, Windows, Mac, Api.
  • You also want dynamic secrets.
HashiCorp Vault review

Questions people ask

Is Cortex or HashiCorp Vault better?
Neither clearly leads. Cortex starts at On request and HashiCorp Vault at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or HashiCorp Vault?
HashiCorp Vault has a free tier; the other does not. Paid plans start at On request for Cortex and Free for HashiCorp Vault.
Does Cortex or HashiCorp Vault run on more platforms?
Cortex runs on Web, API. HashiCorp Vault runs on Linux, Windows, Mac, Api.
Can I use HashiCorp Vault for free?
Yes. HashiCorp Vault 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 HashiCorp Vault is typically brought in for.
What can Cortex do that HashiCorp Vault cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. HashiCorp Vault covers Secret storage, Dynamic secrets, Encryption as a service, Identity-based access.

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.

HashiCorp Vault: Does HashiCorp Vault have a free version?

Yes. The open-source Community Edition is completely free and includes core secrets management, dynamic secrets, and encryption as a service. It is self-hosted with no licensing fees or secret count limits, but lacks enterprise features like namespaces, disaster recovery replication, and Sentinel policies.

Source
Cortex: Is pricing published?

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

HashiCorp Vault: Can I use HashiCorp Vault in production?

The Community Edition is suitable for non-production environments and small teams. For production deployments, organizations typically use HCP Vault Dedicated (managed cloud service starting at approximately 22 USD per month) or Vault Enterprise with custom pricing that includes disaster recovery, performance replication, and 24/7 support.

Source
Cortex: Can it self-host?

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

HashiCorp Vault: What are the main integrations available?

Vault integrates with AWS, Azure, Google Cloud, Active Directory, Okta, and 80+ other platforms. It supports dynamic credential generation for cloud providers, database systems, and identity services, enabling centralized secret management across multi-cloud infrastructure.

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.

HashiCorp Vault: Does Vault work offline?

Vault requires network connectivity to function as it is a centralized secrets management server. However, it can be deployed on-premises for air-gapped environments, and clients can cache short-lived tokens for temporary offline access once authenticated.

Source
Share

Related pages

More on Cortex

More on HashiCorp Vault

Keep looking

Other head to heads