Developer Tools · head to head
AWS CDK vs Split

AWS CDK
Developer Tools
Open source framework for defining AWS infrastructure in programming languages
- From
- Free
- Free plan
- Yes

Split
Testing
Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME
- From
- On request
- Free plan
- No
The short version
- AWS CDK is an Apache 2.
- AWS CDK is free; Split prices on request.
- Only AWS CDK lists construct Library of reusable components; only Split lists feature flags with targeting.
- 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 Split differ?
AWS CDK and Split 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 Split actually diverge.
Which features does each one have?
They share no listed features; 8 appear only for AWS CDK and 8 only for Split. 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 Split
- Feature flags with targeting
- Metrics impact engine
- Guardrail metrics
- Statistical significance testing
- Event ingestion
- SDKs and streaming updates
- Audit and approvals
- Harness platform integration
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 Split
- Reusable internal infrastructure modulesnot Split
- Serverless application stacksnot Split
- Testing infrastructure with unit testsnot Split
- Standardising environments across accountsnot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot AWS CDK
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot AWS CDK
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot AWS CDK
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot AWS CDK
Where do AWS CDK and Split 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
Split
- Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
- Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
- The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
- Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
- As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product
How much do AWS CDK and Split cost?
AWS CDK is free to use; Split is priced on request. Plan by plan below, from each vendor's own pricing page.
AWS CDK
FreeNo published plan breakdown. See the AWS CDK review.
Split
On request- Harness FreeFree
- Harness Open Source and community support
- Intended for individuals and small teams
- Feature management capability limited at this tier
- Harness EssentialsOn request
- Bundled DevOps modules including CI, CD, IaC and security testing
- Standard support
- Pricing requires contacting sales
- Harness EnterpriseOn request
- Mix and match from 15 or more modules including Feature Management and Experimentation
- Premier support with a dedicated account manager
- Higher pipeline concurrency and organisation limits
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 Split if
- You need feature flags with targeting.
- You work on Web, API, iOS, Android, Windows.
- You also want metrics impact engine.
Questions people ask
- Is AWS CDK or Split better?
- Neither clearly leads. AWS CDK starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, AWS CDK or Split?
- AWS CDK has a free tier; the other does not. Paid plans start at Free for AWS CDK and On request for Split.
- Does AWS CDK or Split run on more platforms?
- AWS CDK runs on Windows, macOS, Linux. Split runs on Web, API, iOS, Android, Windows.
- Can I use AWS CDK for free?
- Yes. AWS CDK has a free tier, so you can try it without paying. Split 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 Split is typically brought in for.
- What can AWS CDK do that Split 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. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
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.
SourceSplit: Is Split still called Split?
It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.
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.
SourceSplit: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
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.
SourceSplit: What does it do that a plain flag service does not?
It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.
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.
SourceSplit: Do we need a lot of traffic?
Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.
Related pages
Other head to heads
- AWS CDK vs Terraform
- AWS CDK vs HCP Terraform
- AWS CDK vs Atlantis
- AWS CDK vs Pants Build
- AWS CDK vs Frappe
- AWS CDK vs Spacelift
- AWS CDK vs Backstage
- AWS CDK vs Jitsu
- AWS CDK vs Notepad++
- AWS CDK vs Steampipe
- AWS CDK vs AI SDK
- AWS CDK vs Gitea
- AWS CDK vs GitLab
- AWS CDK vs Buildkite
- AWS CDK vs Eclipse
- AWS CDK vs Sublime Text
- AWS CDK vs Bazel
- AWS CDK vs GitLab CI/CD
- AWS CDK vs GrowthBook
- AWS CDK vs Kameleoon
- AWS CDK vs Eppo
- AWS CDK vs Katalon
- AWS CDK vs Selenium
- AWS CDK vs Sauce Labs
- AWS CDK vs TestRail
- AWS CDK vs Applitools
- AWS CDK vs CloudBees Smart Tests
- AWS CDK vs QA Wolf
- AWS CDK vs CircleCI
- AWS CDK vs BrowserStack
- AWS CDK vs BugHerd
- AWS CDK vs SoapUI
- AWS CDK vs Playwright
- AWS CDK vs GitHub Actions
- AWS CDK vs Cypress
- AWS CDK vs Appium
- Split vs Terraform
- Split vs HCP Terraform
- Split vs Atlantis
- Split vs Pants Build
- Split vs Frappe
- Split vs Spacelift
- Split vs Backstage
- Split vs Jitsu
- Split vs Notepad++
- Split vs Steampipe
- Split vs AI SDK
- Split vs Gitea
- Split vs GitLab
- Split vs Buildkite
- Split vs Eclipse
- Split vs Sublime Text
- Split vs Bazel
- Split vs GitLab CI/CD
- Split vs GrowthBook
- Split vs Kameleoon
- Split vs Eppo
- Split vs Katalon
- Split vs Selenium
- Split vs Sauce Labs
- Split vs TestRail
- Split vs Applitools
- Split vs CloudBees Smart Tests
- Split vs QA Wolf
- Split vs CircleCI
- Split vs BrowserStack
- Split vs BugHerd
- Split vs SoapUI
- Split vs Playwright
- Split vs GitHub Actions
- Split vs Cypress
- Split vs Appium
