Get Kaholo

Kaholo has several deployment models to choose from:

  • Kaholo-hosted software-as-a-service (SaaS)
  • Trial deployment in virtual machine (VM)
  • On-site deployment in Kuberentes
  • Hybrid SaaS + on-site deployment

Kaholo SaaS

By far the easiest way to get Kaholo is Kaholo-hosted Software-as-a-Service (SaaS). Leave the deployment to us!


Kaholo SaaS benefits include:

  • Get started immediately with a free trial account
  • No compute resources required – all is provided by Kaholo in the cloud
  • No Kubernetes expertise required
  • Simple monthly subscription fee
  • Scales effortlessly and automatically as usage grows
  • Automated upgrade and backup managed by Kaholo
  • Monitored for faults 24×7 by Kaholo’s network operation center
  • Comes with highest level of service and support

Visit our Sign Up Page and start automating in minutes with a free 30-day trial of Kaholo SaaS.

Trial deployment in VM

Set up your own virtual machine and deploy Kaholo on your own terms. This model works in any VM – either onsite or in the cloud. It is most useful for product evaluations, test/training systems, and development workstations. The deployment is automated using Ansible.


To deploy a trial system in a VM you will need:

  • A Virtual Machine with
    • Minimum of 2vCPU and 4GB RAM
    • Recommended 4vCPU and 8GB RAM for better performance
    • 50 GB available disk space
    • Ubuntu 22 LTS operating system
    • Network access from the VM to devices and systems you wish to automate with Kaholo
  • A client machine that can run command ansible playbook
  • SSH key with access to VM as user “ubuntu” with sudo privileges
  • FQDN that publicly resolves in DNS to the VM’s public IP address, e.g.
  • From Kaholo
    • A Docker Hub personal access token (dckr_pat) to pull the kaholo images during deployment, and
    • A license file to use Kaholo after deployment
  • The kaholo-ansible Ansible playbook found in GitHub

To get your Docker Hub personal access token and Kaholo trial license, pleasecontact us!

Download or Git clone the playbook and view for detailed instructions how to deploy Kaholo in the VM.


Trial deployment in VM benefits include:

  • Convenient and efficient deployment for short-term Kaholo deployment
    • Trial/Evaluation
    • Test/Dev
    • Training
  • Good for light-weight workloads
  • No Kuberentes resources or skills required – Ansible does it for you
  • VM can be easily shut down and restarted as needed

On-site Deployment with Kubernetes

On-site deployment in Kubernetes is for production use where SaaS is for whatever reason not feasible, for example due to onerous regulatory requirements or corporate policy. The main difference from SaaS is that On-site is self-managed by your Kubernetes administrator, the compute resources used are an additional operational cost, and service and support may also incur additional cost over SaaS.

Specific requirements vary widely on a case-by-case basis so an on-site deployment plan requires cooperation between your Kubernetes administrator and Kaholo. Please contact us to arrange for a free consultation.

The general concept is the same as for any Kaholo deployment – a helm chart is used to deploy Kaholo on a Kubernetes cluster. However the deployment may require adjustment depending on which hardware and/or vendor’s cloud infrastructure is used, and depending on agent requirements.

On-site Deployment with Kubernetes benefits include:

  • Provides highly scalable production-quality level of service, as good as SaaS
  • On-site is the only production-class option if SaaS is for whatever reason eliminated
  • Useful in ring-fenced high-security environments where access from outside is categorically denied
  • Co-locating Kaholo with users and other integrated systems may provide a performance improvement

Hybrid SaaS + On-site Deployment

A Hybrid solution is one where SaaS is the primary provider of platform services, but the actual pipeline executions run on agents that are on-site. This can be helpful or even necessary for several reasons, including special software/hardware requirements, corporate security policy, regulatory requirements, geographically distributed workloads, and many other potential reasons.

If a hybrid deployment seems ideal for your use case please contact us to arrange for a free consultation.