Softwr

Developer Tools · head to head

Cortex vs Fabi

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

Fabi

Business Intelligence

AI notebooks combining SQL, Python and no-code for small data teams

From
Free
Free plan
Yes

The short version

  • Fabi starts at $39/mo; Cortex prices on request.
  • Only Cortex lists service catalogue; only Fabi lists smart Reports.
  • Where Fabi falls short: the free and Builder tiers cap AI requests, and the daily cap on Starter is reached quickly during genuine exploratory work.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cortex and Fabi actually diverge.

Attributes where Cortex and Fabi differ
AttributeCortexFabi
Starting priceOn requestFree
Pricing modelQuotePer user per month
Free tierNoYes
PlatformsWeb, APIWeb
CategoryDeveloper ToolsBusiness Intelligence

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 Fabi

  • Smartbooks
  • Smart Reports
  • AI analysis
  • Scheduled runs
  • Database connectors
  • Viewer seats

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

Fabi

  • A single analyst at a startup fielding ad hoc questions faster than dashboards can be built for themnot Cortex
  • An operations team that needs Python for a one-off analysis but has to hand the result to non-technical colleaguesnot Cortex
  • Replacing a set of scheduled Jupyter notebooks that nobody outside the data team can read or rerunnot Cortex
  • Exploratory work against a warehouse where building a semantic model first would cost more than the answer is worthnot 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

Fabi

  • Fabi is an early-stage company with a small team, so the durability risk is real and there is no obvious migration path for Smartbooks if it stops trading
  • There is no meaningful governance layer: no data catalogue, no certified metric definitions and limited lineage, so it does not scale to an organisation that needs a single agreed number
  • The free and Builder tiers cap AI requests, and the daily cap on Starter is reached quickly during genuine exploratory work
  • Connector counts are limited by tier, so the Builder plan at 39 dollars connects to exactly one data source, which is rarely enough in practice
  • It overlaps heavily with what Snowflake, Databricks and Hex now ship natively, so a company already paying for one of those is buying a fourth notebook interface

Pricing, plan by plan

Cortex

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

Fabi

Free
  • StarterFree
    • One builder seat
    • Ten dashboard viewers
    • Five Smartbooks
  • Builder$39/mo
    • Twenty-five Smart Report viewers
    • Ten Smartbooks with workflows
    • One data connector
  • Team$199/mo
    • Four builder seats, extra seats at 39 USD
    • Fifty viewers
    • Premium connector
  • EnterpriseOn request
    • Unlimited builder seats
    • Full connector access
    • Custom security review

Which should you pick?

Choose Cortex if

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

Choose Fabi if

  • You need smartbooks.
  • You want to start without paying.
  • You also want smart reports.

Questions people ask

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

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.

Fabi: Is there a free plan?

Yes, a Starter tier with one builder, ten viewers, five Smartbooks and ten AI requests a day.

Cortex: Is pricing published?

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

Fabi: Do viewers cost money?

Viewers are bundled by tier rather than charged individually; builders are the priced seat.

Cortex: Can it self-host?

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

Fabi: Can I run arbitrary Python?

Yes, Smartbooks include Python cells alongside SQL and no-code steps.

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.

Fabi: How many data connectors does the entry paid plan include?

One. Additional and premium connectors come with the Team tier.

Share

Related pages

Other head to heads