Developer Tools · head to head
Cortex vs Rill Data

Cortex
Developer Tools
Internal developer portal that scores service ownership and maturity rather than just cataloguing services
- From
- On request
- Free plan
- No

Rill Data
Business Intelligence
Local-first BI on DuckDB and ClickHouse with dashboards defined as code
- From
- $20/month
- Free plan
- No
The short version
- Rill Data starts at $20/mo; Cortex prices on request.
- Only Cortex lists service catalogue; only Rill Data lists local development.
- Prices and features on this page were last checked on 31 August 2026.
Where they differ
Only the attributes on which Cortex and Rill Data actually diverge.
Identical on both: free tier (No).
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 Rill Data
- Local development
- Dashboards as code
- Embedded DuckDB
- Bring your own database
- Alerts and scheduled reports
- Embedded analytics
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 Rill Data
- An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Rill Data
- Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Rill Data
- Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Rill Data
Rill Data
- An analytics team that wants dashboard changes to go through code review rather than being edited in a web UInot Cortex
- Interactive exploration of event-scale data where a warehouse round trip per filter click is too slownot Cortex
- Embedding fast slice-and-dice dashboards into a product where the underlying store is already ClickHouse or Druidnot Cortex
- A data engineer prototyping a metrics layer locally on a laptop before committing to any cloud spendnot 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
Rill Data
- The seat price of 20 dollars is misleading as a budget figure: Rill’s own calculator puts a small two-seat project at around 256 dollars a month, with compute making up the great majority
- Dashboards are defined in YAML and SQL, so business users cannot create or change one without a developer and a Git workflow, which stalls self-service adoption
- It is built for the explore-a-metric pattern and does not produce pixel-perfect financial or operational reports, so most organisations still need a second reporting tool
- AI tokens and API calls are quota-limited per seat, with API overage at a cent per call, so programmatic consumers can create an unbudgeted line item
- As a smaller vendor competing against Looker, Tableau and Power BI, the ecosystem of consultants, templates and trained analysts is thin, which raises the cost of hiring for it
Pricing, plan by plan
Cortex
On request- CortexOn request
- Service catalogue and ownership mapping
- Scorecards and initiatives
- Self-service templates
Rill Data
$20/month- Starter$20/mo
- Per seat, up to twenty seats
- Three projects
- Compute at 0.15 USD per compute unit hour
- Growth$30/mo
- Per seat, up to one hundred seats
- Ten projects
- Compute at 0.20 USD per compute unit hour
- EnterpriseOn request
- Annual platform licence with negotiated capacity
- Unlimited seats and projects
- Dedicated infrastructure
Which should you pick?
Choose Cortex if
- You need service catalogue.
- You work on Web, API.
- You also want scorecards.
Choose Rill Data if
- You need local development.
- You work on Web, Linux, macOS, Windows.
- You also want dashboards as code.
Questions people ask
- Is Cortex or Rill Data better?
- Neither clearly leads. Cortex starts at On request and Rill Data at $20/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Cortex or Rill Data?
- Cortex starts at On request and Rill Data at $20/month.
- Does Cortex or Rill Data run on more platforms?
- Cortex runs on Web, API. Rill Data runs on Web, Linux, macOS, Windows.
- 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 Rill Data is typically brought in for.
- What can Cortex do that Rill Data cannot?
- Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Rill Data covers Local development, Dashboards as code, Embedded DuckDB, Bring your own database.
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.
Rill Data: Is Rill open source?
The Rill developer binary is open source and free to run locally; Rill Cloud is the paid product.
Cortex: Is pricing published?
No. Cortex requires a sales conversation and prepares a custom proposal.
Rill Data: How much does it actually cost?
Seats start at 20 USD per month, but hosted compute at 0.15 USD per compute unit hour typically dominates the bill. Bringing your own database removes the usage fee.
Cortex: Can it self-host?
It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.
Rill Data: Can business users build dashboards?
Not directly. Dashboards are YAML and SQL under version control.
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.
Rill Data: Which databases can back a deployed project?
DuckDB, ClickHouse, Druid, Pinot, Snowflake and others.
Related pages
Other head to heads
- Cortex vs GitHub
- Cortex vs Backstage
- Cortex vs OpsLevel
- Cortex vs Earthly
- Cortex vs Spacelift
- Cortex vs Atlantis
- Cortex vs Depot
- Cortex vs Envoy
- Cortex vs Istio
- Cortex vs Nix
- Cortex vs SonarQube
- Cortex vs Ona (formerly Gitpod)
- Cortex vs Tilt
- Cortex vs Vim
- Cortex vs WarpBuild
- Cortex vs Webpack
- Cortex vs Avo
- Cortex vs Azure DevOps
- Cortex vs Lightdash
- Cortex vs Databox
- Cortex vs Hex
- Cortex vs Grow
- Cortex vs DashThis
- Cortex vs Deepnote
- Cortex vs Luzmo
- Cortex vs Klipfolio
- Cortex vs Cyfe
- Cortex vs Reportz
- Cortex vs Evidence
- Cortex vs Fabi
- Cortex vs ChartMogul
- Cortex vs Dundas BI
- Cortex vs Exa
- Cortex vs Glassbox
- Cortex vs Glean
- Cortex vs Hebbia
- Rill Data vs GitHub
- Rill Data vs Backstage
- Rill Data vs OpsLevel
- Rill Data vs Earthly
- Rill Data vs Spacelift
- Rill Data vs Atlantis
- Rill Data vs Depot
- Rill Data vs Envoy
- Rill Data vs Istio
- Rill Data vs Nix
- Rill Data vs SonarQube
- Rill Data vs Ona (formerly Gitpod)
- Rill Data vs Tilt
- Rill Data vs Vim
- Rill Data vs WarpBuild
- Rill Data vs Webpack
- Rill Data vs Avo
- Rill Data vs Azure DevOps
- Rill Data vs Lightdash
- Rill Data vs Databox
- Rill Data vs Hex
- Rill Data vs Grow
- Rill Data vs DashThis
- Rill Data vs Deepnote
- Rill Data vs Luzmo
- Rill Data vs Klipfolio
- Rill Data vs Cyfe
- Rill Data vs Reportz
- Rill Data vs Evidence
- Rill Data vs Fabi
- Rill Data vs ChartMogul
- Rill Data vs Dundas BI
- Rill Data vs Exa
- Rill Data vs Glassbox
- Rill Data vs Glean
- Rill Data vs Hebbia
