# Appliances

The <mark style="color:green;">**Appliances**</mark> <mark style="color:green;"></mark><mark style="color:green;">section</mark> of the <mark style="color:green;">Inopli RPA</mark> module provides full lifecycle management for <mark style="color:green;">**virtual execution environments**</mark>, enabling the distribution of automation workloads across physical servers or cloud-based infrastructures. Each appliance acts as a remote executor for playbooks, tasks, and integrations.

***

### Overview

* <mark style="color:green;">**Virtual Appliance Deployment**</mark>\
  Appliances are provisioned using <mark style="color:green;">**Docker-based images**</mark>, ensuring consistent and lightweight deployments across heterogeneous environments. Installation can be performed on bare-metal servers, virtual machines, or public cloud instances.
* <mark style="color:green;">**Unlimited Scaling**</mark>\
  There is <mark style="color:green;">**no limit to the number of appliances**</mark> that can be registered. Organizations are free to create as many as needed to support distributed automation, high availability, or multi-region operations.
* <mark style="color:green;">**Centralized Control**</mark>\
  All appliances are managed centrally within the Inopli interface. Admins can register, monitor, and remove appliances at any time, with visibility into their operational status and assigned workloads.

***

### Use Cases

* <mark style="color:green;">**Distributed Execution**</mark>\
  Appliances can be installed <mark style="color:green;">**close to the data or systems they need to interact with**</mark>, reducing latency for sensitive automations (e.g., internal AD changes, on-premises security controls).
* <mark style="color:green;">**Workload Isolation**</mark>\
  Different appliances can be dedicated to specific workflows, tenants, or departments — providing <mark style="color:green;">**logical and operational separation**</mark> where needed.
* <mark style="color:green;">**Cloud-Native or On-Prem Ready**</mark>\
  Whether deployed in a <mark style="color:green;">**Kubernetes cluster**</mark>, a <mark style="color:green;">**cloud VM**</mark>, or an <mark style="color:green;">**on-premises appliance**</mark>, the setup process remains the same, using containerized infrastructure with minimal prerequisites.