Softwr

Developer Tools · head to head

Cortex vs TensorBoard

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
T

TensorBoard

Machine Learning

Local visualisation for training runs, reading event files written to a directory

From
Free
Free plan
Yes

The short version

  • TensorBoard is free; Cortex prices on request.
  • Only Cortex lists service catalogue; only TensorBoard lists scalar dashboards.
  • Prices and features on this page were last checked on 20 November 2026.

How do Cortex and TensorBoard differ?

Cortex and TensorBoard differ on starting price (On request against Free), pricing model (Quote against Open-source) and free tier (No against Yes). Only the attributes on which Cortex and TensorBoard actually diverge.

Attributes where Cortex and TensorBoard differ
AttributeCortexTensorBoard
Starting priceOn requestFree
Pricing modelQuoteOpen-source
Free tierNoYes
PlatformsWeb, APIWeb
CategoryDeveloper ToolsMachine Learning

Which features does each one have?

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

  • Scalar dashboards
  • Run comparison
  • Graph visualisation
  • Histograms and distributions
  • Embedding projector
  • Image, audio and text panels
  • Hyperparameter view
  • Profiler

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

TensorBoard

  • Watching a training run in progress on a workstation or a remote box, to decide whether to stop it earlynot Cortex
  • Diagnosing why a model is not learning, by looking at gradient and weight histograms rather than only the loss curvenot Cortex
  • Profiling a slow training loop to find out whether the bottleneck is the data pipeline or the acceleratornot Cortex
  • Working in an environment with no outbound network access, where a hosted tracking service is not an optionnot Cortex

Where do Cortex and TensorBoard fall 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

TensorBoard

  • There is no authentication of any kind, so putting it on a shared host exposes every run, every metric and every logged sample image to anyone who can reach the port, and adding access control means building and maintaining a reverse proxy
  • Event files grow without limit and the interface loads runs into memory, so a directory holding hundreds of runs or a script logging scalars every step becomes slow to start and unpleasant to navigate well before the disk fills
  • It shows only what the training loop chose to write, so nothing connects a curve back to the code commit, the data set version or the environment unless the engineer logged those explicitly, which means the reproducibility problem is left entirely to you
  • TensorBoard.dev, the hosted service for sharing a run by link, was shut down at the end of 2023, so results now travel between colleagues as screenshots or through a deployment somebody on the team has to operate
  • Comparing runs is done by ticking boxes in a run list, which is fine for ten runs and useless for a thousand, and that threshold is precisely where teams start paying for MLflow, Weights and Biases or Neptune instead

How much do Cortex and TensorBoard cost?

Cortex is priced on request; TensorBoard is free to use. 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

TensorBoard

Free
  • TensorBoard (open source, Apache 2.0)Free

Which should you pick?

Choose Cortex if

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

Choose TensorBoard if

  • You need scalar dashboards.
  • You want to start without paying.
  • You also want run comparison.

Questions people ask

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

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.

TensorBoard: Does it work with PyTorch?

Yes. PyTorch includes a SummaryWriter that emits the same event file format, and Lightning wires it up by default. Nothing about the tool requires TensorFlow at run time.

Cortex: Is pricing published?

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

TensorBoard: Do I have to install TensorFlow to use it?

No. The tensorboard package installs on its own. Some plugins expect TensorFlow to be present, but the scalar, histogram and image dashboards do not.

Cortex: Can it self-host?

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

TensorBoard: Is it an experiment tracker?

No, and treating it as one is the common mistake. It visualises whatever a run wrote to disk. It does not store hyperparameters, code versions, artefacts or results in a way that survives someone deleting the log directory.

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.

TensorBoard: How do I share a dashboard with a colleague?

Host it yourself behind your own authentication, or send screenshots. The hosted sharing service was retired at the end of 2023.

TensorBoard: What does it cost?

Nothing. It is Apache 2.0 licensed and runs on your own machine.

Share

Related pages

Other head to heads