Softwr

Developer Tools · head to head

Cortex vs Firestore

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

Firestore

Databases

Flexible, scalable NoSQL cloud database from Firebase

From
Free
Free plan
Yes
Visit FirestoreFull review

The short version

  • Firestore is free; Cortex prices on request.
  • Only Cortex lists service catalogue; only Firestore lists document Model.
  • Where Firestore falls short: the no-cost Spark plan caps Standard edition at 50,000 document reads, 20,000 writes and 20,000 deletes per day.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Cortex and Firestore actually diverge.

Attributes where Cortex and Firestore differ
AttributeCortexFirestore
Starting priceOn requestFree
Pricing modelQuoteFreemium
Free tierNoYes
PlatformsWeb, APIWeb, iOS, Android, Flutter
CategoryDeveloper ToolsDatabases

Not yet recorded: 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 Cortex

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

Only in Firestore

  • Document Model
  • Real-time Updates
  • Offline Support
  • ACID Transactions
  • Expressive Queries
  • Multi-region
  • Security Rules
  • Firebase Auth

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

Firestore

  • Storing structured application data with realtime listenersnot Cortex
  • Backing mobile and web apps with a serverless document databasenot Cortex
  • Building offline first apps that sync when connectivity returnsnot 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

Firestore

  • The no-cost Spark plan caps Standard edition at 50,000 document reads, 20,000 writes and 20,000 deletes per day
  • The Spark plan caps storage at 1 GiB and network egress at 10 GiB per month
  • Charging is per document read, so a query returning many documents bills for every one of them
  • Going beyond the free thresholds requires the pay as you go Blaze plan billed at Google Cloud rates with no fixed monthly ceiling

Pricing, plan by plan

Cortex

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

Firestore

Free
  • SparkFree
    • 1GB storage
    • 50K reads/day
    • 20K writes/day
  • BlazeFree
    • Pay as you go
    • Unlimited operations
    • Multi-region

Which should you pick?

Choose Cortex if

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

Choose Firestore if

  • You need document model.
  • You want to start without paying.
  • You work on Web, iOS, Android, Flutter.
  • You also want real-time updates.
Firestore review

Questions people ask

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

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.

Firestore: What are the free limits on Cloud Firestore?

The Spark Plan includes 1 GiB of stored data, 50,000 reads per day, 20,000 writes per day, and 20,000 deletes per day at no cost.

Source
Cortex: Is pricing published?

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

Firestore: What happens when I exceed the Spark Plan free tier?

Exceeding the free tier requires upgrading to the Blaze Plan, which bills based on actual usage through Google Cloud pricing. Charges apply for reads, writes, deletes, and data storage.

Source
Cortex: Can it self-host?

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

Firestore: Can I use Firestore without a credit card?

Yes, you can use the Spark Plan indefinitely without a credit card. To use the Blaze Plan (pay-as-you-go), a credit card is required.

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

Firestore: Is there a trial period for Cloud Firestore?

No trial period is specified. The Spark Plan free tier serves as the trial, with no time limit.

Source
Share

Related pages

More on Cortex

More on Firestore

Keep looking

Other head to heads