Softwr

Developer Tools · head to head

AWS CDK vs Cortex

AWS CDK logo

AWS CDK

Developer Tools

Open source framework for defining AWS infrastructure in programming languages

From
Free
Free plan
Yes
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

The short version

  • AWS CDK is an Apache 2.
  • AWS CDK is free; Cortex prices on request.
  • Only AWS CDK lists construct Library of reusable components; only Cortex lists service catalogue.
  • Where AWS CDK falls short: targets AWS only, so it does not provision resources on other clouds.
  • Prices and features on this page were last checked on 20 November 2026.

How do AWS CDK and Cortex differ?

AWS CDK and Cortex differ on starting price (Free against On request), pricing model (Open-source against Quote) and free tier (Yes against No). Only the attributes on which AWS CDK and Cortex actually diverge.

Attributes where AWS CDK and Cortex differ
AttributeAWS CDKCortex
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsWindows, macOS, LinuxWeb, API

Identical on both: category (Developer Tools).

Which features does each one have?

They share no listed features; 8 appear only for AWS CDK and 8 only for Cortex. 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 AWS CDK

  • Construct Library of reusable components
  • CDK CLI for synthesis and deployment
  • Programmatic CDK Toolkit Library
  • Support for TypeScript, JavaScript, Python, Java, C# and Go
  • Deployment through AWS CloudFormation
  • Custom and shareable constructs
  • Construct Hub registry
  • Open source under Apache 2.0

Only in Cortex

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

What is each one used for?

AWS CDK is most often brought in for defining AWS infrastructure in TypeScript or Python. The jobs each tool is most often brought in to do.

AWS CDK

  • Defining AWS infrastructure in TypeScript or Pythonnot Cortex
  • Reusable internal infrastructure modulesnot Cortex
  • Serverless application stacksnot Cortex
  • Testing infrastructure with unit testsnot Cortex
  • Standardising environments across accountsnot Cortex

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot AWS CDK
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot AWS CDK
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot AWS CDK
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot AWS CDK

Where do AWS CDK and Cortex fall short?

AWS CDK's most cited limit: targets AWS only, so it does not provision resources on other clouds. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

AWS CDK

  • Targets AWS only, so it does not provision resources on other clouds
  • Deploys through CloudFormation, so its resource coverage and limits apply
  • Infrastructure written in code can be harder to review than declarative templates
  • The AWS resources it creates are billed separately at standard AWS rates

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

How much do AWS CDK and Cortex cost?

AWS CDK is free to use; Cortex is priced on request. Plan by plan below, from each vendor's own pricing page.

AWS CDK

Free

No published plan breakdown. See the AWS CDK review.

Cortex

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

Which should you pick?

Choose AWS CDK if

  • You need construct library of reusable components.
  • You want to start without paying.
  • You work on Windows, macOS, Linux.
  • You also want cdk cli for synthesis and deployment.

Choose Cortex if

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

Questions people ask

Is AWS CDK or Cortex better?
Neither clearly leads. AWS CDK starts at Free and Cortex at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, AWS CDK or Cortex?
AWS CDK has a free tier; the other does not. Paid plans start at Free for AWS CDK and On request for Cortex.
Does AWS CDK or Cortex run on more platforms?
AWS CDK runs on Windows, macOS, Linux. Cortex runs on Web, API.
Can I use AWS CDK for free?
Yes. AWS CDK has a free tier, so you can try it without paying. Cortex starts at On request.
What is AWS CDK best used for?
AWS CDK is most often used for defining aws infrastructure in typescript or python, reusable internal infrastructure modules, serverless application stacks, testing infrastructure with unit tests. Of those, defining aws infrastructure in typescript or python and reusable internal infrastructure modules are not what Cortex is typically brought in for.
What can AWS CDK do that Cortex cannot?
AWS CDK covers Construct Library of reusable components, CDK CLI for synthesis and deployment, Programmatic CDK Toolkit Library, Support for TypeScript, JavaScript, Python, Java, C# and Go. Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates.

Answered from the vendors’ own pages

AWS CDK: Which languages does AWS CDK support?

The AWS documentation lists TypeScript, JavaScript, Python, Java, C# and .NET, and Go. Infrastructure is defined as constructs composed into stacks and apps.

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

AWS CDK: How does AWS CDK deploy resources?

CDK apps are synthesised and deployed through AWS CloudFormation. The documentation states this gives predictable, repeatable deployments with rollback on error.

Source
Cortex: Is pricing published?

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

AWS CDK: Is AWS CDK free?

It is open source under the Apache 2.0 licence according to its GitHub repository. The AWS resources you provision with it are charged at their normal rates.

Source
Cortex: Can it self-host?

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

AWS CDK: When was AWS CDK first released?

Wikipedia reports a developer preview announced in 2018 and general availability on 11 July 2019. CDK v2 followed in 2021.

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