Why choose Radius? - highlights #1702
Description
What content needs to be created or modified?
Create a new "Why Radius" documentation page that compares Radius with leading cloud-native tools on the market, including AZD CLI, Terraform, Pulumi, Kubernetes-native (Helm/Kustomize), Crossplane, Backstage (with scaffolding plugins), and cloud-specific solutions (Azure deployment stacks/Bicep, AWS CDK, etc.).
Describe the solution you'd like
The content should clearly articulate why development and platform teams should choose Radius over alternatives, focusing on:
- Developer Experience (DX): Simpler workflows and abstractions, improved onboarding, less boilerplate, and seamless inner/outer loop integration.
- Policy/Governance: Built-in support for enforcing policies, organizational controls, and compliance at deployment or runtime, in contrast to the limitations or complexity of alternatives.
- Multi-Cloud: Native abstraction for cloud-agnostic deployment, easy movement between Azure, AWS, and other providers, and avoiding vendor lock-in. Highlight Radius’s unique capabilities over traditional tools.
Content should be honest, actionable, and evidence based.
Where should the new material be placed?
As a new dedicated page: /docs/why-radius.md or equivalent in the main site navigation, easily discoverable for users evaluating Radius vs. other solutions.
The associated pull request from the Radius code repo, if applicable
N/A
Additional context
Comparisons should address both direct feature differences and overall value proposition, especially for developers and platform engineers. Competitors to include: AZD CLI, Terraform/Pulumi, Helm/Kustomize, Crossplane, Backstage, cloud-specific tools. Prioritize clarity and actionable differentiation above marketing claims.