> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/guides/installing-lucy/system-requirements.md).
# System Requirements
### Supported Operating Systems
Lucy Docker deployments are supported on Ubuntu 22.04 LTS and later.
### Supported Linux Distributions
* **Ubuntu**: 20.04 LTS (Legacy), 22.04 LTS, 24.04 LTS
* **Debian**: 9.x, 10.x (Legacy)
* **Red Hat/CentOS**: 9.x
Other Operating Systems
Virtualization platforms such as VMware or VirtualBox are compatible with most common operating systems. Users are encouraged to refer to their specific vendor's documentation for detailed compatibility information.
**Compatibility with Operating Systems and Platforms:**
Docker containers support a wide range of environments, including but not limited to:
* Amazon EC2
* Arch Linux
* CentOS
* CRUX Linux
* Fedora
* FrugalWare
* Gentoo
* IBM SoftLayer
* Install on Joyent Public Cloud
* Mac OS X
* Microsoft Azure platform
* Oracle Linux
* Rackspace Cloud
* Red Hat Enterprise Linux
* openSUSE and SUSE Linux Enterprise
* Ubuntu
* Windows
### Supported Browsers
Lucy's phishing and awareness templates are designed to function seamlessly across a wide range of desktop and mobile browsers, including:
* Chrome
* Firefox
* Edge
* Opera
* Safari
***
### Hardware Requirements
#### Small Campaigns (up to 2000 recipients)
* **RAM**: 8 GB
* **CPU**: 4 Core
* **Hard Disk**: 100 GB
#### Medium Campaigns (up to 50,000 recipients)
* **RAM**: 16 GB
* **CPU**: 8 Core
* **Hard Disk**: 300 GB
#### Large Campaigns (up to 100,000 recipients)
* **RAM**: 32 GB
* **CPU**: 16 Core
* **Hard Disk**: 500 GB
Hardware Recommendations
* **Initial Setup:** Ensure that your initial hardware setup meets the minimum requirements for your expected campaign size. It's better to allocate more resources upfront to avoid performance bottlenecks.
* **Storage Planning:** Given the potential need for additional templates and the data generated by campaigns, planning for ample storage from the beginning is wise. Consider future expansion when selecting your hard disk size.
* **Use Built-in Tools:** Regularly utilize LUCY's [performance testing ](/application-reference/support/system-tests/performance-test.md)and [monitoring tools](/application-reference/support/status/system-monitoring.md) to keep your system running efficiently. These tools can provide valuable insights into how well your hardware is coping with the demands of your campaigns.
* **Flexible Scaling:** If you are hosting your LUCY instance on a VPS, take advantage of the ability to scale your resources as needed. This can be particularly useful for handling peak loads during large campaigns.
**VPS Hosting**
For users opting for a Virtual Private Server (VPS) hosted by LUCY:
* **Dynamic Resource Scaling.** LUCY provides the capability to automatically scale computing resources, including CPU and RAM, to meet the demands of your campaign. This feature ensures optimal performance of campaigns by adjusting resources in real time, eliminating the need for manual adjustments. In case of hardware limitations, users are encouraged to contact the[ support department](/contact-us.md) for assistance in scaling their Virtual Private Server (VPS).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.lucysecurity.com/guides/installing-lucy/system-requirements.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.