> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-installation-guides/6.14/cortex-xsoar-installation-guide/readme/installation-overview.md).
# Installation Overview
This document provides instructions and information for installing Cortex XSOAR.
Before installing, review the following and determine the type of installation to perform based on your requirements:
* **Deployment**
* **Single server** deployment are designed for small and mid-sized customers and provides an all-in-one XSOAR experience.
* **Multi-tenant** deployments are designed for MSSPs (managed security service providers) and enterprises that require strict data segregation, but also need the flexibility to share and manage critical security practices across tenant accounts.
* **Database**
Select the database based on your predicted data usage.
* For the **Bolt** database, we recommend a limit of 1 million indicators for the development environment and 5-7 million indicators for the production environment. If you will exceed this limit, we recommend using **Elasticsearch**.
* If you have a High Availability deployment requirement, you must use **Elasticsearch**.
The following shows the key differences in the different Cortex XSOAR installation architectures. Additional information for these architectures can be found in the reference links in the last row of the table.
| | Standalone | Multi-Tenant | High Availability |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| |  |  |  |
| **Audience** | Small and mid-sized customers. | Managed Security Service Providers (MSSPs) or similar. | Customers with high demand in availability. |
| **Benefits** | Provides an all-in-one Cortex XSOAR experience. | Segregation of data per tenant combined with central management. | Maximized availability. |
| **Database** | Bolt database or Elasticsearch. | Bolt database or Elasticsearch. | Elasticsearch. |
| **Operating System** | - RedHat
- Centos
- Ubuntu
- Oracle Linux
| - RedHat
- Centos
- Ubuntu
- Oracle Linux
| - RedHat
- Centos
- Ubuntu
- Oracle Linux
|
| **Requirements** | One server with:
- 16 CPU
- 32GB RAM
- 1TB SSD storage
| Main server and each tenant server with:
- 16 CPU
- 32GB RAM
- 1TB SSD storage
| Each app server with the following and a 3 node Elasticsearch cluster:
- 16 CPU
- 32GB RAM
- 500 GB SSD with minimum 3k dedicated IOPS
|
| **Limitations** | Recommendation for Bolt database: 1 million indicators for the development environment and 5-7 million indicators for the production environment. If you will have more indicators, we recommend using Elasticsearch. | Recommendation for Bolt database: 1 million indicators for the development environment and 5-7 million indicators for the production environment. If you will have more indicators, we recommend using Elasticsearch. | - Remote repositories is not supported in Dev environments.
- Cannot be configured with Bolt database, only with Elasticsearch.
- Requires a shared file system for storing artifacts.
|
| **Performance** | - Bolt database - 1,384 incidents per hour.
- Elasticsearch - 1,679 incidents per hour.
| --- | 5,686 incidents per hour (based on 4 app servers). |
| **Additional Information** | [Single Server Installation Overview](/cortex-xsoar-6-installation-guides/6.14/cortex-xsoar-installation-guide/readme/single-server-installation-overview.md) | [Multi-Tenant Installation Overview](/cortex-xsoar-6-installation-guides/6.14/cortex-xsoar-installation-guide/readme/multi-tenant-installation-overview.md) | [High Availability Overview](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/high-availability/high-availability-overview.md) |
After you determine the type of installation that is required, review the applicable content in the following sections for additional information and instructions.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-installation-guides/6.14/cortex-xsoar-installation-guide/readme/installation-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.