Softwr

Databases · head to head

ClickHouse vs Cortex

ClickHouse logo

ClickHouse

Databases

Fast open-source column-oriented database for real-time analytics

From
Free
Free plan
Yes
Visit ClickHouseFull review
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
Visit CortexFull review

The short version

  • ClickHouse is free; Cortex prices on request.
  • Only ClickHouse lists column-oriented Storage; only Cortex lists service catalogue.
  • Where ClickHouse falls short: limited multi-row atomic transactions and expensive UPDATE/DELETE operations unsuitable for transactional systems.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which ClickHouse and Cortex actually diverge.

Attributes where ClickHouse and Cortex differ
AttributeClickHouseCortex
Starting priceFreeOn request
Free tierYesNo
PlatformsLinux, macOS, WindowsWeb, API
CategoryDatabasesDeveloper Tools

Not yet recorded: pricing model for ClickHouse, founded for Cortex.

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 ClickHouse

  • Column-oriented Storage
  • Real-time Analytics
  • SQL Support
  • Linear Scalability
  • Data Compression
  • Vectorized Query Execution
  • Approximate Calculations
  • Kafka

Only in Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

What people use each for

The jobs each tool is most often brought in to do.

ClickHouse

  • Business intelligencenot Cortex
  • Data warehousingnot Cortex
  • Real-time analyticsnot Cortex
  • Reportingnot Cortex
  • Machine learningnot Cortex

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot ClickHouse
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot ClickHouse
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot ClickHouse
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot ClickHouse

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

ClickHouse

  • Limited multi-row atomic transactions and expensive UPDATE/DELETE operations unsuitable for transactional systems
  • Requires upfront schema design discipline with MergeTree engine choices and sort/partition keys
  • Experimental vector search support, not production-ready for vector operations
  • Different query syntax from standard SQL requiring migration planning
  • Limited JOIN capabilities compared to traditional relational databases
  • Migration complexity with 2-4 weeks estimated for data type mapping and query translation

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

Pricing, plan by plan

ClickHouse

Free

No published plan breakdown. See the ClickHouse review.

Cortex

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

Which should you pick?

Choose ClickHouse if

  • You need column-oriented storage.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want real-time analytics.
ClickHouse review

Choose Cortex if

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

Questions people ask

Is ClickHouse or Cortex better?
Neither clearly leads. ClickHouse starts at Free and Cortex at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, ClickHouse or Cortex?
ClickHouse has a free tier; the other does not. Paid plans start at Free for ClickHouse and On request for Cortex.
Does ClickHouse or Cortex run on more platforms?
ClickHouse runs on Linux, macOS, Windows. Cortex runs on Web, API.
Can I use ClickHouse for free?
Yes. ClickHouse has a free tier, so you can try it without paying. Cortex starts at On request.
What is ClickHouse best used for?
ClickHouse is most often used for business intelligence, data warehousing, real-time analytics, reporting. Of those, business intelligence and data warehousing are not what Cortex is typically brought in for.
What can ClickHouse do that Cortex cannot?
ClickHouse covers Column-oriented Storage, Real-time Analytics, SQL Support, Linear Scalability. Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates.

Answered from the vendors’ own pages

ClickHouse: What is ClickHouse best used for?

ClickHouse is optimized for analytical workloads on large datasets. It excels at fast aggregations and queries, being 10-100x faster than PostgreSQL on large aggregations.

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

ClickHouse: Does ClickHouse support transactions?

ClickHouse has limited transaction support and expensive UPDATE/DELETE operations. It is not suitable for transactional workloads requiring strict ACID guarantees.

Source
Cortex: Is pricing published?

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

ClickHouse: How does ClickHouse compare to PostgreSQL?

ClickHouse is 10-100x faster for analytics but PostgreSQL is better for transactional workloads. Many teams use both: PostgreSQL for writes via MaterializedPostgreSQL replication to ClickHouse for analytics.

Source
Cortex: Can it self-host?

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

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

More on ClickHouse

More on Cortex

Keep looking

Other head to heads