Scripts can be a quick and powerful source of automation, tying together systems, performing pre/post processing validations, or performing useful services. 

Traditionally however, scripts are difficult to secure and provide uniform access to, lack centralized audit trails, are usually written with logic that may not be easily understood when staff changes, and once linked to dependencies, pose a risk to operations. 

The OneFuse Platform provides a single source for your IT staff to create or re-use scripts of any language for Windows, Linux and SSH-enabled devices, deliver them as a service across tools and platforms, enabling rich content such as Terraform or Ansible as a service.  

With OneFuse any team can bring scripts into the spotlight, creating useful, repeatable API-based services, gaining the same intended usefulness packaged as a safe, trackable service. 

Script Deployments in OneFuse

OneFuse Scripting with vRA Cloud Assembly

OneFuse Scripting with Terraform

OneFuse Makes vRA Better

Learn More


Scripts simplified

Define scripts to execute templated, dynamic script content for provision and deprovision lifecycles

Artificial intelligence - user
Lightweight and agentless

Execute scripts on target resources without the need for a third-party agent

Big-data-sheet icon
Centralized Visibility

View the active deployment representing the outputs and relevant data of each policy execution

Blockchain icon

Features and Capabilities

  • Drive from any tool, e.g. vRealize Automation, Terraform, Ansible, ServiceNow, CloudBolt CMP or directly via the API
  • Create API-based services using templated, policy-based scripts  
  • Standardize API outputs and inventory capture based on customizable, JSON-based script outputs
  • SSH-based, no agents 
  • 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 script or over-allocating permissions to users to downstream systems.  
  • Each policy defines the automation use case – specific provisioning and deprovisioning script templates with launch command and success exit codes. 
  • Added flexibility of having the requester influence all use cases dynamically via templated fields 
  • Multiple Scripting Policies (each specifying a Target Host) can safely co-exist, allowing for isolated testing and promotion without disruption