On-Premise deployment on Own Machine

This method describes how to manually install and configure all required components for Risk by Context™ on a physical or virtual machine. It is recommended for users who require greater flexibility, customization, or wish to integrate the system into existing infrastructure. asvin provides pre-built docker images for Risk by Context™ to run in containers.

System Requirements

This section contains information about software and hardware requirements for installation of Risk by Context™ solution.

Hardware

  • 4-core CPU

  • 4 GB RAM (Recommended 8 GB or more for smoother performance)

  • 50 GB hard-drive space

Software

To install Risk by Context™ successfully, your machine must meet the following software requirements.

Operating System

  • Ubuntu

    • Ubuntu 22.04, 24.04, or the latest non-LTS version.

    • 64-bit kernel and CPU support for virtualization.

    • KVM virtualization support. To check if the KVM modules are enabled, execute lsmod | grep kvm. You should see KVM related modules.

    • systemd init system

  • Windows

    • WSL version 1.1.3.0 or later.

    • Windows 11 64-bit: Home or Pro version 22H2 or higher, or Enterprise or Education version 22H2 or higher.

    • Windows 10 64-bit: Minimum Home or Pro 22H2 (build 19045) or higher, or Enterprise or Education 22H2 (build 19045) or higher.

    • Enable the WSL 2 feature on your Windows system. For step-by-step guidance, refer to the official Microsoft documentation.

Containerization technology:

Warning

Docker can bypass firewall rules set by ufw or firewalld when exposing container ports. Review Docker’s firewall behavior before installing.

Install Docker Engine or Docker Desktop.

Deployment steps

Note

Check with your IT administrator for network security configuration before the deployment.

Note

Check if docker is installed with docker version & docker compose version and you can run docker run hello-world without errors.

  1. Run RBC containers using RBC CLI, using docker compose or using docker

  2. Verify if containers are running with ./rbc ps, docker compose ps -a or docker ps -a

  3. Access the RBC Portal in your browser at http://localhost:8080