Softwr

Developer Tools · head to head

Cortex vs Replicate

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

Replicate

AI

Run AI models in the cloud

From
Free
Free plan
Yes

The short version

  • Replicate starts at $0.000025/mo; Cortex prices on request.
  • Only Cortex lists service catalogue; only Replicate lists model hosting.
  • Where Replicate falls short: private model deployments are billed for all the time instances are online, including setup and idle time, not only for processing.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Cortex and Replicate actually diverge.

Attributes where Cortex and Replicate differ
AttributeCortexReplicate
Starting priceOn requestFree
Pricing modelQuoteUsage-based
Free tierNoYes
PlatformsWeb, APIAPI, Web
CategoryDeveloper ToolsAI

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 Replicate

  • Model hosting
  • Simple API
  • Auto-scaling
  • Custom models
  • REST API
  • Python client
  • JavaScript client
  • Api support

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

Replicate

  • Running open source machine learning models through a hosted API without managing GPUsnot Cortex
  • Deploying and serving a custom or fine tuned model on rented GPU hardwarenot Cortex
  • Per second billed batch image, video and language model inferencenot 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

Replicate

  • Private model deployments are billed for all the time instances are online, including setup and idle time, not only for processing
  • Multi-GPU A100, H100, H200 and L40S capacity beyond the listed configurations is only available with a committed spend contract
  • The pricing page publishes no free tier allowance

Pricing, plan by plan

Cortex

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

Replicate

Free
  • Pay-as-you-goOn request
    • Billed by execution time for public models
    • CPU Small: $0.000025/second ($0.09/hour)
    • 8x Nvidia A100 GPUs: $0.0112/second ($40.32/hour)
  • EnterpriseOn request
    • Dedicated account manager
    • Priority support
    • Higher GPU limits

Which should you pick?

Choose Cortex if

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

Choose Replicate if

  • You need model hosting.
  • You want to start without paying.
  • You work on API, Web.
  • You also want simple api.

Questions people ask

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

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.

Replicate: How much does Replicate cost?

Replicate uses pay-as-you-go pricing based on model execution time and compute type. Costs range from $0.09/hour for CPU (Small) to $40.32/hour for 8x Nvidia A100 GPUs. Some models charge per input/output tokens instead of time.

Source
Cortex: Is pricing published?

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

Replicate: Does Replicate offer a free tier?

Yes, Replicate is free to start with pay-as-you-go pricing. There are no subscription tiers or minimum commitments; you pay only for what you use.

Source
Cortex: Can it self-host?

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

Replicate: What is the difference between public and private models?

Public models are billed by execution time. Private models are billed for all instance uptime including setup, idle, and active processing time, except for fast-booting fine-tunes which are billed only during active processing.

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.

Share

Related pages

Other head to heads