Ask for platform access.
Start here when a team needs shared approvals, policy rollout, and saved proof.
- Platform access is reviewed, not self-serve.
- Most teams should test OSS first.
- Enterprise review is only for real deployment limits.
Pick the right path.
Most teams should request platform access. Use enterprise review only for region, isolation, or governance limits.
Managed control plane
Use this when your team needs shared approvals, policy rollout, operator workflow, and evidence retention.
Scoped deployment path
Use this only when region, isolation, governance, or deployment needs go beyond the shared environment.
Request platform access.
Use this when the team knows it needs shared approvals, operator workflow, or policy rollout.
Request access to HELM Platform
Use this when your team needs shared approvals, policy rollout, operator workflow, or retained evidence around the managed control plane.
Ask for enterprise review.
Use this only when the shared environment is the wrong fit for deployment, region, or policy reasons.
Request an enterprise deployment review
Use this path only when region, isolation, governance, or deployment requirements go beyond the shared managed environment.
Use the public path first.
Open source, proof, and docs should answer most questions before an access request.
Run HELM OSS first
Install the OSS release and route one risky workflow through the boundary.
Check public proof
Use the proof pages to see what survives the run.
Read the short docs
Use docs when you want the fastest path from install to first governed action.