Softwr

Developer Tools · head to head

Cortex vs Xata

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

Xata

Databases

Apache 2.0 platform for running many Postgres instances on Kubernetes, with copy-on-write branching and scale-to-zero.

From
Free
Free plan
Yes
Visit XataFull review

The short version

  • Xata starts at $1/mo; Cortex prices on request.
  • Only Cortex lists service catalogue; only Xata lists copy-on-write branching.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Cortex and Xata actually diverge.

Attributes where Cortex and Xata differ
AttributeCortexXata
Starting priceOn requestFree
Pricing modelQuoteUsage-based
Free tierNoYes
PlatformsWeb, APIWeb
CategoryDeveloper ToolsDatabases

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 Xata

  • Copy-on-write branching
  • Scale-to-zero compute
  • Compute autoscaling and bin-packing
  • High availability with failover
  • Point-in-time recovery
  • Serverless driver
  • pgroll migrations
  • pgstream replication

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

Xata

  • Giving every pull request or coding agent its own branch of the production database, with real data volumes rather than a seeded fixturenot Cortex
  • Running managed-Postgres economics in your own cloud account where data residency or compliance rules out a third-party control planenot Cortex
  • Consolidating many small, mostly idle Postgres databases onto shared infrastructure where scale-to-zero and bin-packing recover the idle costnot Cortex
  • Testing a destructive migration against a copy of production without waiting for a full restore or paying for a duplicate of the storagenot 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

Xata

  • Self-hosting means operating Kubernetes and CloudNativePG, so the Apache 2.0 licence removes the vendor bill but replaces it with a platform team, and a database platform is not something a part-time operator maintains safely
  • Copy-on-write branches are cheap to create but diverge as they are written to, so a long-lived branch carrying a heavy backfill quietly accumulates real storage and the cost arrives later than the decision that caused it
  • Scale-to-zero means the first connection after an idle period pays a cold start, which is invisible in a busy production database and very visible in a demo, a staging environment or a cron job that runs once an hour
  • The Xata sold before 2025 was a different product, a proprietary API and SDK layered over Postgres, so tutorials, blog posts and SDK examples from that era describe something that no longer exists and existing users had to migrate
  • As a managed service it competes with RDS, Aurora and Cloud SQL, and it is a much smaller company, so procurement, certification coverage and the depth of the support bench behind a 3am corruption incident are all weaker than the incumbent even though the underlying Postgres is the same

Pricing, plan by plan

Cortex

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

Xata

Free
  • Free TrialFree
    • 14 days free
    • No credit card required
  • Usage-Based$1
    • 1,000 branches for $1
    • Scale-to-zero compute model
    • Branches hibernate when idle

Which should you pick?

Choose Cortex if

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

Choose Xata if

  • You need copy-on-write branching.
  • You want to start without paying.
  • You also want scale-to-zero compute.
Xata review

Questions people ask

Is Cortex or Xata better?
Neither clearly leads. Cortex starts at On request and Xata at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Xata?
Xata has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Xata.
Does Cortex or Xata run on more platforms?
Cortex runs on Web, API. Xata runs on Web.
Can I use Xata for free?
Yes. Xata 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 Xata is typically brought in for.
What can Cortex do that Xata cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Xata covers Copy-on-write branching, Scale-to-zero compute, Compute autoscaling and bin-packing, High availability with failover.

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.

Xata: Is it real Postgres or a compatible reimplementation?

Real Postgres. It runs upstream Postgres instances on Kubernetes via CloudNativePG, so extensions, the wire protocol and version upgrades behave as they do anywhere else.

Cortex: Is pricing published?

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

Xata: Can I self-host the whole thing?

Yes. The platform is Apache 2.0 and designed for self-hosting a large number of Postgres instances on your own Kubernetes. Xata Cloud is the same platform run as a service.

Cortex: Can it self-host?

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

Xata: Does branching copy my data?

No. Branches are copy-on-write at the storage layer, so creating one is near-instant regardless of database size and storage is only consumed as the branch diverges from its parent.

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.

Xata: Is this the same Xata I used a couple of years ago?

No. The earlier product was a proprietary database API with its own SDK and search layer. The current product is a Postgres platform, and material written for the old one does not apply.

Xata: What happens to a branch when the parent changes?

A branch is a point-in-time fork. Later changes on the parent are not propagated, so long-lived branches drift and need to be recreated rather than refreshed if you want current data.

Share

Related pages

More on Cortex

More on Xata

Keep looking

Other head to heads