> 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.15/cortex-xsoar-installation-guide/readme/single-server-installation-overview.md).
# Single Server Installation Overview
Cortex XSOAR 6.15 single server deployment overview with Bolt, Elasticsearch, and high availability.
In a single-server installation, Cortex XSOAR and its database are installed on a single computer. Review the following single-server deployment descriptions to determine which deployment is best for you.
### Installation with the Bolt Database
When installing Cortex XSOAR with the Bolt database, the app server and database are installed on the same machine.
Before beginning your installation with the Bolt database, review the Cortex XSOAR system requirements and then follow the instructions in [Install Cortex XSOAR with Bolt Database](/cortex-xsoar-6-installation-guides/6.14/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-bolt-database.md).
### Installation with the Elasticsearch Database
Elasticsearch is an analytics engine for all types of data. It enables storing, searching, and analyzing large amounts of data quickly and in near real time.
**Maximum indicator capacity and disk usage comparison**
The following table compares the maximum total indicator capacity and disk usage for the Bolt database and Elasticsearch. The maximum indicator capacity value was determined when testing the system.
We recommend using Elasticsearch if you plan to exceed at least one of the following maximum capacities for the Bolt database.
The Cortex XSOAR indicators used to test the sizing requirements did not contain a significant number of additional fields or custom fields. The maximum size of the indicators tested had 20 additional or custom fields and a random string between 1-16 characters. Therefore, the indicator size tested was approximately 0.5KB. If you plan to have additional or custom fields for indicators, the maximum numbers should be reduced.
| Benchmark | BoltDB | Elasticsearch |
| ---------------------------------- | ------------------------------------------------------------------------ | -------------------------------------------------------------------------------- |
| Maximum indicator capacity (total) | 5-7 million
(Requires up to 10 seconds for a complex query)
| 100 million
(Requires approximately 40 seconds for a complex query)
|
| Disk usage | 5 million (\~ 30 GB) | 100 million (\~ 70 GB) |
The following diagram depicts a Cortex XSOAR environment with Elasticsearch.
In order to move to Elasticsearch, you must have Cortex XSOAR v6.1 or above and Elasticsearch installed. We recommend that you install Elasticsearch on a different server than Cortex XSOAR due to the high memory consumption for both services.
When working with Elasticsearch, Cortex XSOAR does not maintain, nor is it responsible for, the following:
* Redundancy
* Backups
* Security
* Elasticsearch clusters
{% hint style="info" %}
Moving data from the Elasticsearch database back to the Cortex XSOAR Bolt database is not supported.
{% endhint %}
Before beginning your installation with the Elasticsearch database, review the system requirements and the Elasticsearch system requirements, and then follow the instructions in [Install Cortex XSOAR with Elasticsearch](/cortex-xsoar-6-installation-guides/6.14/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-elasticsearch.md).
---
# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-installation-guides/6.15/cortex-xsoar-installation-guide/readme/single-server-installation-overview.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.