> For the complete documentation index, see [llms.txt](https://docs.exavault.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exavault.com/installing-and-upgrading-the-appliance/installation-and-setup/installing-other-software.md).

# Installing Other Software

The ExaVault appliance is provided as a VMware image and through cloud marketplaces such as AWS and Google Cloud. It requires minimal ongoing server maintenance.

You have root access to the virtual machine through its console or SSH and can change the underlying system.

Avoid installing custom software unless an organizational requirement makes it necessary. ExaVault updates and support assume the appliance's supplied system configuration.

If you must install software beyond what is included on the virtual machine, two drawbacks apply.

## Service Dependencies and Environment Stability

The appliance contains a number of services that rely upon a specific system configuration to function predictably. Installing other software can have unforeseen interactions with the ExaVault services. For example, if your custom software interferes with the [required firewall configuration](/installing-and-upgrading-the-appliance/firewall-configuration.md), file transfers can be disrupted.

## Updates and Replacement Images

An update may change system packages, services, firewall rules, or other dependencies on which custom software relies. A non-Premium update also replaces the virtual machine image, so software installed on the system disk must be installed again.

Document every customization and automate its installation where possible. After each appliance update, confirm that the custom software and all ExaVault connection methods still work.