Robility Flow

Estimated reading: 3 minutes

This document defines the deployment prerequisites required to install and operate the RobilityFlow Platform in a customer environment. It consolidates the infrastructure, software, network, security, and licensing requirements that must be in place before installation activities begin.

RobilityFlow is Robility’s AI-assisted workflow orchestration platform built on a containerised, cloud-native architecture. It enables business and technical users to visually design, publish, and execute multi-step automated flows that can integrate with enterprise systems, REST APIs, databases, and large-language-model (LLM) services.

Scope covers the two core platform components:

1. RobilityFlow Designer – Browser-based visual canvas for building, testing, and publishing automation flows. Delivered as a containerised application.
2. RobilityFlow Runtime – Backend execution engine that processes published flows, manages state and credentials, and exposes REST and WebSocket APIs. Runs in headless / backend-only mode.

RobilityFlow supports two deployment models:

1. Kubernetes – Recommended for production environments requiring high availability, automated scaling, and multi-zone resilience. Click here to learn more.
2. Virtual Machine (VM) with Docker – Suitable for pilot deployments, resource-constrained environments, or customers who prefer a simpler operational model. Click here to learn more.

Component Architecture Overview

RobilityFlow is a cloud-native, container-first platform. Both the Designer and the Runtime (back-end) are distributed as OCI-compliant container images. All persistent state is externalised to PostgreSQL, Redis, and object storage — the containers themselves are stateless and horizontally scalable.

The platform supports deployment on Kubernetes (orchestrated) and directly on Virtual Machines using Docker Compose (standalone).

Component	Role	Deployment Target
RobilityFlow Designer	Web-based visual workflow design studio. Runs as a containerized React application served through NGINX and provides an intuitive interface for creating, editing, testing, and publishing workflows.	Kubernetes Pod (Deployment) or Docker Container on a Virtual Machine.
RobilityFlow Runtime	Backend execution engine responsible for processing workflow executions, managing runtime state, handling orchestration logic, and exposing REST and WebSocket APIs. Operates in headless/API-only mode.	Kubernetes Pod (Deployment) or Docker Container on a Virtual Machine.
PostgreSQL	Persistent data store for workflow definitions, execution history, variables, configuration settings, metadata, and audit records.	Kubernetes StatefulSet, Managed Cloud Database Service, or Docker Container on a Virtual Machine.
Redis	Provides session caching, real-time publish/subscribe messaging for execution events, distributed locking, and task queue brokering.	Kubernetes StatefulSet, Managed Cache Service, or Docker Container on a Virtual Machine.
Object Storage	Stores uploaded files, workflow exports, generated artifacts, backups, and large payload attachments used by workflows and runtime services.	S3-Compatible Storage Service (AWS S3, Azure Blob Storage, Google Cloud Storage, MinIO, or equivalent).
Ingress / API Gateway	Routes external HTTPS traffic to the Designer and Runtime services, performs TLS termination, load balancing, request routing, and ingress security controls.	Kubernetes Ingress Controller (NGINX, Traefik, Kong, AWS ALB, etc.) or NGINX Reverse Proxy on a Virtual Machine.

Robility Flow

Component Architecture Overview

Robility Flow

CONTENTS