---
title: Installation and Deployments
slug: litmusedge/quickstart-guide/installation-and-deployments
description: Review the different options for installing Litmus Edge based on your specific needs and setup. 
docTags: 
createdAt: 2022-03-30T21:23:09.000Z
---

The Litmus Edge operating system can be deployed in several ways.

# Litmus Edge Deployment Models

![](https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/UDWFHX-Io-377aGRJKoHO_image.png "Litmus Edge Deployment Models")

Litmus Edge is most commonly installed:

- On a physical hardware device such as an IPC (Industrial PC)
- As a VM (virtual machine). You can install as a VM using the following virtual environments:
  - Oracle VirtualBox
  - VMWare ESXi
  - VMware Workstation Player
  - QEMU Emulator KVM
  - Windows Hyper-V
- On Docker
- On Kubernetes

To determine the best approach for installation, determine how you will use Litmus Edge.

# Collect Data for an Asset or Line Base

If Litmus Edge is used to collect data on an asset or line base, the most common form of deployment is an installation on a physical device such as an IPC (Industrial PC) device.

If you'll use Litmus Edge to collect data on an asset or line base, the most common form of deployment is an installation on a physical device such as an IPC (Industrial PC) device.

The IPC is installed close to the asset or line, often within the same cabinet as the data source, such as a PLC (Programmable Logic Controller), CNC (Computer Numerical Control), robotic system, or DCS (Distributed Control System).

It is connected through one of its network cards to the VLAN of the asset or line. The second network card connects the device to the plant OT (Operational Technology) network and allows for access using the Web UI (User Interface).

# Collect Data For a Section or Plant

If Litmus Edge is used to collect data for a section or plant level that includes several lines or assets, consider deploying it as a virtual system.

This is usually done using managed virtual environments such as VMWare ESXi. The virtual machine runs inside the virtualized environment and connects to the data sources through the plant OT network.

This requires routing that allows the VM to reach every data source located within isolated VLANs.

# Development System

The installation as virtual machine using Oracle VirtualBox is another option. This is usually a development system. For example, in a PoV (proof of value) project, or where many stakeholders test the system and it is not feasible to provide a physical device to everyone.

# Mixed Installation

It is also possible to use a mixed installation. This combines the deployment of physical devices on an asset or line basis and the deployment of a virtualized system as a consolidation layer.

See [Verified VM Versions](docId\:BMdKuS5X6Uj8Fa-4c5uQI)  and [Validated Gateway Devices](docId\:cjKzwEtLboJtc-A5aMm4c) for more information.

# Next Steps

- [OVA Installation on Virtual Machine](docId\:G1k-LrOJE5u2z3mB-772f) 
- [ISO Installation on Virtual Machine](docId\:DWzONQkDiDn4SnSz2FPSL) 
- [Physical Gateway Installation](docId\:blDXZrjtg_SGSXjgYT2sk) 
- [Docker Installation](docId\:xH3VHlG7P12KTlzHEzOnD) 
- [Zerotouch Installation](docId\:sVg4vhfY3-S26SCaFFvFZ) 
- [Kubernetes Installation](docId\:Io2DlrZlL2Oo0W1qI7u8N) 
- [Raspberry Pi Installation](docId\:HbYcLaGNvSGjXr5NQo4XA)
- [License Server Installation](docId\:Ko7wFLqRmWv3wg_QZJzTY)