Release platform + component exchange
From code to a running app.
Your runtime or ours.
Forest gives application teams one fast release path. Run on Forest Runtime, or deploy to your own infrastructure through a versioned provider—using the same components, policy, pipeline, and release history.
# Adopt the platform team's versioned delivery contract $ forest add acme/service-standard@1.4.0 $ forest validate # Managed Forest Runtime in dev $ forest release create --environment dev # Customer-owned infrastructure behind the production provider $ forest release create --environment prod --pipeline
The destination changes. The application release workflow does not.
One delivery contract, two ways to run
Versioned release capabilities
Package build, deployment, policy, and developer tooling as typed components. Lock exact versions in each application.
Forest Runtime
Take the managed path from a release declaration to a running container service without operating the destination yourself.
Your infrastructure
Keep your clusters, cloud accounts, and spend. Forest providers translate the same release into your target platform.
Private development preview
Forest Runtime and provider-backed releases exist, but neither carries a production hosting guarantee yet. Forest is currently suitable only for trusted internal evaluation on a private network. Native components run with the invoking user's privileges, and runner, provider, artifact, and tenant isolation require further hardening before external use.