When installing YugabyteDB Anywhere on-premises or on a public cloud (AWS, GCP, and Azure), you install YugabyteDB Anywhere onto a virtual machine server with a Linux operating system (OS).
To meet the hardware and software prerequisites for YugabyteDB Anywhere, create a VM that satisfies the following requirements.
## Hardware requirements
The server for YugabyteDB Anywhere must meet the following hardware requirements:
- 4 cores
- 8 GB memory
- 215 GB disk space
- x86 (Intel, AMD) architecture
## Software requirements
YugabyteDB Anywhere has the following software requirements:
- x86 Linux operating system
- License
- Python
- Sudo root permissions for installation
### Linux OS
You can install YugabyteDB Anywhere onto any [x86 Linux operating system](../../../reference/configuration/operating-systems/) supported by YugabyteDB. YugabyteDB Anywhere can't be installed on ARM architectures (but can be used to deploy universes to ARM-based nodes).
YugabyteDB Anywhere may also work on other Linux distributions; contact your YugabyteDB support representative if you need added support.
### License
Installation requires a license file. To obtain your license, contact your sales representative. If you are not yet a customer and want to try YugabyteDB Anywhere, [book a demo](https://www.yugabyte.com/demo/).
### Python for YugabyteDB Anywhere
Python v3.10 to v3.12 (v2025.2.2.0 and later) or v3.10 to v3.11 (V2025.2.0-2025.2.1) must be pre-installed.
Both python and python3 must symbolically link to Python 3. One way to achieve this is to use alternatives. For example:
```sh
sudo yum install @python311 -y
sudo alternatives --config python
# choose Python 3.11 from list
sudo alternatives --config python3
# choose Python 3.11 from list
python -V
# output: Python 3.11.0
python3 -V
# output: Python 3.11.0
```
### Permissions
YBA Installer supports installation using sudo, and [non-sudo installation](../../install-yugabyte-platform/install-software/installer/#non-sudo-installation).
If you are using sudo and your sudo permissions are limited, add the following commands to the sudoers file:
```sh
/usr/bin/yba-ctl clean
/yba-ctl clean
/usr/bin/yba-ctl createBackup
/yba-ctl generate-config
/usr/bin/yba-ctl help
/yba-ctl help
/yba-ctl install
/usr/bin/yba-ctl license
/yba-ctl license
/usr/bin/yba-ctl log-bundle
/usr/bin/yba-ctl preflight
/yba-ctl preflight
/usr/bin/yba-ctl reconfigure
/yba-ctl replicated-migrate
/usr/bin/yba-ctl replicated-migrate
/usr/bin/yba-ctl restart
/yba-ctl restart
/usr/bin/yba-ctl restoreBackup
/usr/bin/yba-ctl start
/yba-ctl start
/usr/bin/yba-ctl status
/yba-ctl status
/usr/bin/yba-ctl stop
/yba-ctl stop
/yba-ctl upgrade
/usr/bin/yba-ctl version
/yba-ctl version
```
Where path-to-yba-ctl is the location where you will [install YBA Installer](../../install-yugabyte-platform/install-software/installer/#download-yba-installer).
## High availability deployments
If you plan to deploy YBA in active-passive [high-availability](../../administer-yugabyte-platform/high-availability/) mode, you need two VMs (identical in hardware and software); one for the active YBA instance, and another for the standby YBA instance.