One easy way to configure all your workloads. Everywhere.
Score is a developer-centric and platform-agnostic workload specification. It ensures consistent configuration between local and remote environments. And it's open source.
Why use Score?
Score is loved by developers because they can run the same workload on completely different technology stacks, without needing to be an expert in any one of them.
Developers are forced to become experts in a variety of tech and tools, just do deploy a simple change to their apps.
Features over Ops
Score takes care of configs for developers so they can focus on shipping features instead of fighting with infrastructure.
Multiple config rules, constructs and values across local and remote environments increase the risk of misconfiguration.
Local to prod
With Score you can easily transition from local to to remote environments. Configs stay consistent, everywhere you deploy.
Trying to keep many environment-specific config files in sync leads to repetitive configuration work and YAML bloat.
Score lets you use one specification file as the single source of truth, easily translatable across your delivery setup.
A single spec to rule them all
Easily integrates in your existing workflows
Extendable and customizable
The score.yaml file can be extended and customised according to your needs. The score spec leaves room for environment specific overrides as well as platform specific extensions that allow to list additional properties or requirements.
Declarative by nature
Score lets developers define the resources required by their workloads in a declarative way. You declare once that your workload needs to listen on a port to receive requests - and don’t not need to worry where and how the exact port is defined in e.g. a remote Kubernetes environment. By declaring what the workload needs to run, the “how” becomes an environment specific implementation detail that is taken care of by Score.
Seamless tech stack and workflow integration
Score introduces a single change to your setup by adding a score.yaml file to your workloads’ repo. Everything else stays as is. Once Score is set up, you can continue using it even if the underlying tech stack changes.