Using the OneFuse vRealize Automation module, it’s easy to create API-based, blueprints-as-a-service to drive solutions from upstream automation tools or scripts. 

OneFuse eliminates the security risk of requiring direct access to a vRealize automation, enabling least-privilege access for specific use cases via policy-based services, versus exposing the full vRealize Automation API or micro-managing permissions. Each policy defines the automation use case, organization, cloud template and optional input parameters – with the added flexibility of having the requester influence all use cases dynamically via templated fields.

vRA Policy in OneFuse

vRA Deployments in OneFuse

vRA Module with vRA Cloud Assembly

vRA Module with Terraform
OneFuse Makes vRA better feature capabilities chart small

OneFuse Makes vRA Better

Discover how OneFuse can help fill some vRA gaps!

Learn More


Consume VMware vRealize Automation Cloud Templates

via API, scripts or supported Upstream Platforms

Document icon
Drive “Blueprints-as-a-Serivce" dynamically

Specify Cloud Template/Blueprint by name, version, input parameters and which user will own the deployed resources

Brain icon
Centralized Visibility

View the active deployment representing the resource(s) and relevant data of each policy execution

Blockchain icon
The Truth About First Gen CMP_eBook Image
Industry Insights Report

VMware vRealize Automation

Discover how 200+ vRA Customers are using vRA and handling the upcoming migration to vRA 8.

Read Report

Features and Capabilities

  • Drive from any tool, e.g. vRealize Automation, Terraform, Ansible, ServiceNow, CloudBolt CMP or directly via the API
  • OneFuse enables least-privilege access wherein each policy serves as an API-based service, restricted to the specific use cases defined in the policy, without exposing the full vRealize Automation API 
  • Each policy defines the automation use case, organization, cloud template and optional input parameters 
  • Ability to dynamically assign the owner for vRA-deployed resources provisioned using the policy 
  • Multiple vRealize Automation Policies (each specifying a vRealize Automation Endpoint) can safely co-exist, allowing for isolated testing and promotion without disruption