● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement and reviews are still being built.
KubeEra
S

Score

SandboxApp Definition & Delivery
Open source · CNCF · CNCF Sandbox · Apache-2.0

Score is a developer-facing workload specification — a YAML file format that describes how a containerized workload should run without tying that description to a specific runtime. You write one score.

updated 2026-07-01

What it is

Score is a developer-facing workload specification — a YAML file format that describes how a containerized workload should run without tying that description to a specific runtime. You write one score.yaml per workload, and separate CLI tools ("score-implementations") translate that spec into platform-specific configs: Docker Compose, Kubernetes manifests, Helm values, or other target formats. The core idea is decoupling "what my app needs" (env vars, resources, dependencies, ports) from "how my platform expresses that" (Kubernetes Deployment YAML, Compose files, whatever).

It's not a runtime, not an orchestrator, and not a replacement for Helm or Kustomize. It sits upstream of those tools as an abstraction layer aimed at reducing the YAML burden on application developers who don't want to own Kubernetes-specific config.

Who builds it and why

Score originated at Humanitec, a platform engineering vendor, as part of their push toward standardizing developer-facing workload definitions separate from platform implementation details. It's now a CNCF Sandbox project. The GitHub repo shows 18 contributors and 8,057 stars — a moderate but not massive community, consistent with a spec-plus-tooling project rather than a full platform. Commit activity is active (last commit June 2026), suggesting the project isn't dormant, though contributor count staying flat over time is typical for spec-driven projects where most of the ecosystem work happens in downstream implementations rather than the core repo.

The motivation is straightforward: platform teams want developers to stop hand-writing Kubernetes manifests, and Score gives them a simpler, portable format to hand developers instead.

Production readiness signal

CNCF Sandbox status means this is early-stage — Sandbox is the lowest maturity tier, requiring far less proof of adoption or governance rigor than Incubating or Graduated. Version 0.4.x indicates the spec itself is still pre-1.0 and subject to breaking changes. 18 contributors is thin for something meant to be a cross-ecosystem standard; healthy specs (OpenAPI, CloudEvents) typically show broader multi-org contribution at this stage.

Treat this as: usable for greenfield internal tooling, not yet something to bet a platform's core developer experience on without a fallback plan. The spec format has been stable enough for Humanitec's own platform and a handful of implementations, but expect breaking changes before 1.0.

Who should use this

Platform engineering teams building internal developer platforms (IDPs) who want a vendor-neutral input format for developer-submitted workload definitions. Teams already using Humanitec or evaluating it, since Score is native to that ecosystem. Organizations that want to abstract Kubernetes specifics away from app developers but don't want to build a custom DSL from scratch.

Who should NOT use this

Teams looking for a Helm alternative — Score doesn't manage releases, rollbacks, or templating logic at that level; it's a different layer entirely. Teams that need a mature, widely-adopted standard today — Sandbox status and a sub-1.0 version number mean you're an early adopter, not a consumer of an established spec. Organizations without a platform engineering function — if developers are already comfortable writing Kubernetes YAML or using Helm charts directly, Score adds an abstraction layer with no clear payoff. Anyone needing GitOps-native reconciliation — Score produces static output for a CI step; it doesn't reconcile drift like Flux or Argo CD.

Alternatives

  • Helm — the incumbent Kubernetes packaging/templating tool; far more mature, much larger ecosystem, but couples developers more tightly to Kubernetes concepts.
  • KubeVela — a CNCF project offering a similar "app-centric abstraction" goal but bundled with its own control plane and OAM model, more opinionated and heavier.
  • Humanitec Workload Profiles / custom internal DSLs — many platform teams just build their own thin YAML abstraction in-house instead of adopting a still-maturing external spec.

Pricing

Score is fully open source under Apache-2.0. No paid tier, no commercial product wrapping the spec itself — cost considerations come from whatever platform or CI tooling you build around it, not from Score.

Frequently asked

What is Score?+
Score is a developer-facing workload specification — a YAML file format that describes how a containerized workload should run without tying that description to a specific runtime. You write one score.
Who builds Score?+
Score originated at Humanitec, a platform engineering vendor, as part of their push toward standardizing developer-facing workload definitions separate from platform implementation details. It's now a CNCF Sandbox project.
Is Score production ready?+
CNCF Sandbox status means this is early-stage — Sandbox is the lowest maturity tier, requiring far less proof of adoption or governance rigor than Incubating or Graduated. Version 0.4.x indicates the spec itself is still pre-1.0 and subject to breaking changes.
Who should use Score?+
Platform engineering teams building internal developer platforms (IDPs) who want a vendor-neutral input format for developer-submitted workload definitions. Teams already using Humanitec or evaluating it, since Score is native to that ecosystem.
Who should not use Score?+
Teams looking for a Helm alternative — Score doesn't manage releases, rollbacks, or templating logic at that level; it's a different layer entirely. Teams that need a mature, widely-adopted standard today — Sandbox status and a sub-1.0 version number mean you're an early adopter, not a consumer of an established spec.
What are the alternatives to Score?+
Helm — the incumbent Kubernetes packaging/templating tool; far more mature, much larger ecosystem, but couples developers more tightly to Kubernetes concepts. KubeVela — a CNCF project offering a similar "app-centric abstraction" goal but bundled with its own control plane and OAM model, more opinionated and heavier.
How much does Score cost?+
Score is fully open source under Apache-2.0. No paid tier, no commercial product wrapping the spec itself — cost considerations come from whatever platform or CI tooling you build around it, not from Score.