Managed runtime

The managed runtime hosts your services. It scales them to demand — including to zero — and resolves their configuration and resource bindings at deploy time, so a running revision gets exactly the config and connections it declared.

How a service runs is declared in infra/runtime.json (see Deploy & hosting); what config it resolves comes from its config schema plus per-environment values.

Scaling & scale-to-zero

{ "scaling": { "min": 0, "max": 2, "concurrency": 500 } }
  • min: 0 scales to zero when idle; the next request cold-starts an instance.
  • min: 1 keeps one instance warm.
  • concurrency is the requests per instance before the platform scales out toward max.

Config & bindings

Configuration is data, resolved by the platform — not baked into the image.

Concern How
Declare config keys a config schema in the project
Set per-environment values conf/env.<env>.yaml + putnami cloud publish-config
Inspect resolved config putnami cloud config
Manage secrets putnami cloud secrets

Resource bindings (a database, a bucket) are resolved by the platform and injected into the runtime, so application code connects to what it declared without carrying credentials in config.

Inspect and operate

Want to… Do this
Inspect the resolved config putnami cloud config --env <env>
Inspect the published schema putnami cloud config --schema --env <env>
See declared secret keys without values putnami cloud config --secret-keys --env <env>
List or update secrets putnami cloud secrets --env <env>

Next