Overview
Platform Hub provides two types of templates that help you standardize and share your deployment configuration across spaces.
Process templates are reusable sets of deployment steps. Instead of copying and pasting deployment processes across projects, you define the steps once and share them. Teams can opt into using a process template within their deployment process, and can remove it if it no longer fits their needs.
Project templates give platform engineering teams a way to define a golden path for how projects are structured. The deployment process is defined by the template and can’t be modified in projects based on it. Through parameters exposed by the platform team, project teams can deploy using their own packages, accounts, worker pools, and target tags, while the underlying process stays consistent across every project based on the template. Project templates are currently in Alpha, see the installation guide to get started.
Both template types use parameters to expose configurable inputs, letting you define what a project must supply while keeping the core template consistent across teams and spaces.
Prerequisites
Before creating any template, you must configure a Git repository in Platform Hub. This repository stores your templates as code (OCL files) and is the single source of truth for all template changes.
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Friday, March 6, 2026