Pick the path that fits what you need now.
Start with OSS if you want to test the boundary yourself. Use Studio when more than one person needs to share control. Talk to us when deployment needs are specific.
One control layer, three access paths.
Choose the path that matches the real need you have today.
HELM OSS
Install locally, test one risky workflow, and verify the release trail before you trust it.
HELM Studio
Use the managed path when a team needs shared approvals and one place to run the system.
Enterprise deployment
Use this path when isolation, region, governance, or security needs go beyond the guided managed setup.
Start with the smallest honest step.
Most teams should inspect the system before they ask for anything managed.
Start with OSS.
Use OSS when you need to prove the control layer belongs in your stack.
Use guided access when people share control.
Move up when several people need one place for approvals, records, and daily use.
Use enterprise only for real constraints.
Region, isolation, and governance needs are the reason for a direct deployment conversation.
Read the product, the docs, and the proof first.
That is the shortest path to a useful conversation.
Read quickstart
Understand the shortest path from first install to first governed workflow.
Inspect Explorer
Look at receipts and proof flows before deciding how much managed support you need.
Talk to the team
Reach out when you already know why you need shared controls or a custom deployment.