Softwr

Developer Tools · head to head

Cortex vs turbopuffer

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

turbopuffer

Databases

Closed-source vector and full-text search service built directly on object storage, with cold queries measured in seconds rather than milliseconds.

From
$16/month
Free plan
No

The short version

  • turbopuffer starts at $16/mo; Cortex prices on request.
  • Only Cortex lists service catalogue; only turbopuffer lists object storage architecture.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Cortex and turbopuffer actually diverge.

Attributes where Cortex and turbopuffer differ
AttributeCortexturbopuffer
Starting priceOn request$16/month
Pricing modelQuoteSubscription
PlatformsWeb, APIWeb
CategoryDeveloper ToolsDatabases

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 turbopuffer

  • Object storage architecture
  • Namespaces
  • Vector search
  • Full-text search
  • Attribute filtering
  • Documented limits
  • Configurable consistency
  • Durable writes

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

turbopuffer

  • A product with one search index per customer and thousands of customers, most of whose data is idle on any given daynot Cortex
  • Very large corpora where holding every vector in memory is the dominant cost and occasional cold-query latency is acceptablenot Cortex
  • Hybrid retrieval combining BM25 and vector search where running and synchronising two separate systems is the problem being solvednot Cortex
  • Retrieval for agent and assistant products where indexes are created and destroyed frequently and per-index overhead must be near zeronot 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

turbopuffer

  • A cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second
  • Queries are eventually consistent by default, and after roughly 128 MiB of outstanding writes new data is invisible until indexed, which the vendor puts at tens of seconds for small namespaces and tens of minutes for large ones, so a bulk re-index is not immediately queryable
  • It is closed source with no community edition, so single-tenant or bring-your-own-cloud deployment is a commercial negotiation rather than a deployment choice, and there is no path to running it yourself if the relationship ends
  • Per-namespace ceilings, roughly 10,000 writes per second, 32 MB/s and 500 million documents per shard, mean a single enormous index has to be sharded across namespaces by your application rather than by the service
  • It is a search engine, not a database: there are no joins, no cross-document transactions and no SQL, so it sits beside a primary datastore and keeping the two in step is work that belongs to you

Pricing, plan by plan

Cortex

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

turbopuffer

$16/month
  • Launch$16/mo
    • All database features
    • Multi-tenancy deployment
    • SOC2 & GDPR-ready DPA
  • Scale$256/mo
    • Everything in Launch
    • HIPAA-ready BAA
    • Single Sign-On (SSO)
  • Enterprise$4,096/mo
    • Everything in Scale
    • Single-tenancy & BYOC deployment options
    • Private networking

Which should you pick?

Choose Cortex if

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

Choose turbopuffer if

  • You need object storage architecture.
  • You also want namespaces.

Questions people ask

Is Cortex or turbopuffer better?
Neither clearly leads. Cortex starts at On request and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or turbopuffer?
Cortex starts at On request and turbopuffer at $16/month.
Does Cortex or turbopuffer run on more platforms?
Cortex runs on Web, API. turbopuffer runs on Web.
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 turbopuffer is typically brought in for.
What can Cortex do that turbopuffer cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

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.

turbopuffer: Can I self-host turbopuffer?

There is no open source or community edition. Single-tenant and bring-your-own-cloud deployments exist as commercial arrangements, but there is no way to run it independently of the vendor.

Cortex: Is pricing published?

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

turbopuffer: How fast is it really?

Warm queries perform comparably to in-memory search engines. Cold queries, where data is not cached, have a documented p90 around 1,214 ms on a million documents. Write p90 is around 248 ms for a 512 KB upsert because writes go straight to object storage.

Cortex: Can it self-host?

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

turbopuffer: Is it consistent?

Eventually consistent by default, with the vendor reporting that over 99.8% of queries return consistent data. Strong consistency can be requested per query at a latency cost. Large write bursts have a longer visibility delay while indexing catches up.

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.

turbopuffer: What is it best at?

Large numbers of namespaces where most are idle. The architecture makes cold data cheap to keep, which is exactly the shape of a multi-tenant product with a long tail of inactive customers.

turbopuffer: What are the hard limits?

Up to 128 billion documents and 256 TB per namespace, 500 million documents per shard, 64 MiB per document, 10,752 dense vector dimensions, roughly 10,000 writes per second per namespace and a maximum result set of 10,000.

Share

Related pages

Other head to heads