# radius-project/radius

Radius is a cloud-native, portable application platform that makes app development easier for teams building cloud-native apps.

Repository: https://github.com/radius-project/radius
Canonical: https://ross.abutalabs.com/products/radius
Homepage: https://radapp.io
Language: Go
License: Apache-2.0
License Family: permissive
Last push: 2026-08-26T19:46:30+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 99, longevity 100
- inputs: {"age_days": 2021, "days_push": 7, "days_rel": 7, "gap_med": 27, "n_releases_24m": 26}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1665, forks 135 (observed 2026-08-28T04:05:19.079990+00:00)

## What it is
Radius is an open-source, cloud-native application platform that lets developers model an entire application—its services and the infrastructure they depend on—as a single portable definition. Platform engineers supply swappable Recipes (Terraform/Bicep templates) that provision that infrastructure with built-in cost, operations, and security compliance across Kubernetes, Azure, AWS, and on-premises environments.

## Use cases
- deploy cloud-native applications across multiple clouds from one definition
- give developers self-service provisioning of databases, caches, and message queues
- enforce organizational infrastructure policy with reusable Recipes
- visualize an application's services and dependencies as an application graph
- standardize golden-path deployment workflows between developers and platform engineers
- run the same app definition on local Kubernetes, Azure, AWS, and on-prem
- integrate Dapr microservice building blocks into application deployments

## When to choose
- your teams deploy Kubernetes apps with backing infrastructure like databases and message brokers across multiple environments
- you want platform engineers to govern infrastructure while developers self-serve
- you need portable application definitions that avoid cloud vendor lock-in
- you want an explicit application model and dependency graph on top of Kubernetes

## When to avoid
- you only deploy simple stateless containers without infrastructure dependencies
- your organization is committed to a single cloud's native tooling like Azure ARM or AWS CDK
- you need a fully mature GA product rather than a CNCF sandbox project
- you don't use Kubernetes as your deployment substrate

## Facets
- artifact type: application
- maturity: active
- function: deployment, infrastructure-as-code, configuration-management, developer-tools, microservices, workflow-automation
- domain: cloud-computing, infrastructure-as-code, microservices, developer-tools, self-hosted
- platform: go, cli, cloud, windows
- tags: application-platform, recipes, application-graph, multi-cloud, dapr, platform-engineering, bicep, terraform, cncf-sandbox, portable-applications, devops, containers, kubernetes, docker, linux, macos

## Member repositories
- radius-project/radius (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:19.079990+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:44:27.018560+00:00, confidence not recorded.
  - readme: https://github.com/radius-project/radius (fetched 2026-08-28T04:05:19.079990+00:00, sha eeb9c181a080)
  - homepage: https://radapp.io (fetched 2026-08-29T11:16:32.544399+00:00, sha c2d13cb1b7fc)
  - site_page: https://docs.radapp.io (fetched 2026-08-29T11:16:32.556024+00:00, sha 87a75e4c440c)
  - site_page: https://docs.radapp.io/getting-started (fetched 2026-08-29T11:16:32.558064+00:00, sha 35f4dba6e30f)
- Data as of 2026-08-30T08:39:29.467469+00:00.