Softwr

Developer Tools · head to head

Cortex vs Fly.io

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
Fly.io logo

Fly.io

Cloud

Deploy web applications globally

From
$29/month
Free plan
No

The short version

  • Each has a real cost: 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.; Fly.io egress is priced by destination region, from $0.02 per GB in North America and Europe to $0.12 per GB for Africa and India, so the same traffic costs six times more depending on where users are
  • They diverge on capability: Cortex covers Service catalogue, Fly.io covers Global deployment.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cortex and Fly.io actually diverge.

Attributes where Cortex and Fly.io differ
AttributeCortexFly.io
Starting priceOn request$29/month
Pricing modelquoteusage-based
PlatformsWeb, APIWeb, Api, Docker
CategoryDeveloper ToolsCloud
FoundedUnknown2020

Identical on both: free tier (No), user rating (Not yet rated).

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 Fly.io

  • Global deployment
  • Docker support
  • Postgres databases
  • Redis support
  • Auto-scaling
  • Health checks
  • Backups
  • Monitoring

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

Fly.io

  • Deploying containerised applications close to users across regionsnot Cortex
  • Running full stack apps and databases on managed machinesnot 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.

Fly.io

  • Egress is priced by destination region, from $0.02 per GB in North America and Europe to $0.12 per GB for Africa and India, so the same traffic costs six times more depending on where users are
  • Stopped machines still bill at $0.15 per GB of root filesystem a month, so a paused service is not a free one
  • Volumes are billed on provisioned capacity rather than usage, at $0.15 per GB a month
  • Reservation discounts of 40% require paying a year up front, from $36 to $1,440
  • Fly Kubernetes is a separate $75 a month per cluster
  • Dedicated IPv4 addresses are $2 a month each

Pricing, plan by plan

Cortex

On request
  • Cortex$undefined/year
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

Fly.io

$29/month
  • Pay-as-You-Go$null/mo
    • Micro VMs and persistent storage charged by usage
    • FlyCTL CLI
    • Unlimited users and organizations
  • Serious Support$29/month
    • Access to dedicated engineering team
    • All Pay-as-You-Go features
  • Machine Reservation Blocks$null/mo
    • 40% discount on machine usage
    • Requires upfront payment for savings
  • Compliance Package$99/month
    • HIPAA compliance
    • BAAs
    • SOC2 documentation

Which should you pick?

Choose Cortex if

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

Choose Fly.io if

  • You need global deployment.
  • You work on Web, Api, Docker.
  • You also want docker support.

Questions people ask

Is Cortex or Fly.io better?
Neither clearly leads. Cortex starts at On request and Fly.io at $29/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Fly.io?
Cortex starts at On request and Fly.io at $29/month.
Does Cortex or Fly.io run on more platforms?
Cortex runs on Web, API. Fly.io runs on Web, Api, Docker.
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 Fly.io is typically brought in for.
What can Cortex do that Fly.io cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Fly.io covers Global deployment, Docker support, Postgres databases, Redis support.

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.

Fly.io: Is there a free tier for Fly.io?

Fly.io does not advertise a free tier. The base plan is pay-as-you-go with usage-based pricing for Micro VMs and persistent storage. All users get FlyCTL CLI, unlimited organizations, private networking, SSO, ACLs, and scoped tokens.

Source
Cortex: Is pricing published?

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

Fly.io: How much does Fly.io Serious Support cost?

Serious Support costs 29 USD per month and provides access to a dedicated engineering team while maintaining all pay-as-you-go features for Micro VMs and storage.

Source
Cortex: Can it self-host?

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

Fly.io: What does Fly.io Compliance Package include?

The Compliance Package is 99 USD per month and includes HIPAA compliance, BAAs, and SOC2 documentation for organizations requiring compliance certifications.

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.

Fly.io: Does Fly.io offer discounts for upfront commitment?

Yes, Fly.io offers Machine Reservation Blocks with 40% discount on machine usage. This requires upfront payment but applies savings on infrastructure costs.

Source
Share

Related pages

Other head to heads