> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# System Requirements

> Hardware and software requirements for deploying OpenOps on-premises

The open source version of OpenOps is meant to be deployed on-premises and is distributed as a Docker Compose specification.

## Hardware

Hardware requirements vary depending on your use case. There are two primary groups of use cases:

* **Exploring OpenOps and building automations**. For these purposes, 2 CPU cores, 8GB RAM, and 50GB storage should be sufficient.
* **Production use and running your automations**. For this scenario, aim at 4 CPU cores, 16GB RAM, and 100GB storage.

## Operating systems

OpenOps can be deployed on the following operating systems:

* **Linux**: Ubuntu 20.04 LTS or later, Debian 11 (Bullseye) or later, Fedora 35 or later.
* **macOS**: macOS Big Sur (11.x) or later.
* **Windows**: Windows 10 version 2004 (build 19041) or later, or Windows 11.

## Docker

OpenOps is distributed as a Docker Compose file. Here are Docker version requirements by operating system:

* On Linux: **Docker Engine v20.10+ and Docker Compose v2.x**.
* On macOS: **Docker Desktop 4.11 or later**. If you're running macOS on an Apple Silicon processor (M1 or M2), open Docker Desktop settings, and in the *General* tab, scroll down to the *Virtual Machine Options* section. Once there, make sure that:
  1. *Apple virtualization framework* is selected for *Virtual Machine Manager*.
  2. The *Use Rosetta for x86/amd64 emulation on Apple Silicon* option is enabled.
* On Windows: **Docker Desktop 4.11 or later**. In your Docker Desktop settings, in the *General* tab, enable the *Use the WSL 2 based engine* option.

If you're using an alternative Docker client such as OrbStack or Colima, make sure that the version of your Docker client includes Docker Engine v20.10+ and Docker Compose v2.x.

## Browser

You can access OpenOps using any modern browser. However, viewing the full set of workflow templates in the OpenOps [template catalog](/workflow-management/workflow-templates/) requires signing in to OpenOps Cloud, which comes with additional requirements.

<Note>
  You may not be able to connect to OpenOps Cloud and see additional templates if:

  * Your browser is configured to block third-party cookies. Allow third-party cookies ([Chrome](https://support.google.com/chrome/answer/95647), [Safari](https://help.apple.com/safari/mac/8.0/en.lproj/sfri11471.html), [Firefox](http://support.mozilla.org/en-US/kb/third-party-cookies-firefox-tracking-protection)) for your OpenOps installation’s URL.
  * You're using an OpenOps installation served over HTTP in Safari. Consider enabling HTTPS for your installation by following the instructions for [AWS](/getting-started/deployment/aws-ec2#enabling-tls), [Azure](/getting-started/deployment/azure-vm#enabling-tls), or [GCP](/getting-started/deployment/gcp-vm#enabling-tls) deployments.
</Note>