# Deployment

## Overview

Once you’ve obtained an Onum account, just a few steps are needed to complete the installation, depending on the type of deployment you require. Onum supports flexible deployment options, including both on-premises and cloud environments. 

In case you have any question regarding the deployment and installation process, please [contact us](/support/support.md).

{% hint style="warning" %}
**Supported browsers**

Onum supports the following browsers:

* Google Chrome
  {% endhint %}

### Cloud deployment

For cloud-based installations, CrowdStrike or a partner will activate Onum access within the Falcon platform. All the necessary infrastructure will be set up based on estimated usage metrics.

The deployment process is fully automated, ensuring quick and streamlined provisioning and configuration.

{% hint style="warning" %}
**Cloud Listeners**

Note that the Listener configuration process is slightly different if you are using a Cloud deployment. Learn more [in our Listeners articles](/the-workspace/listeners/listener-integrations.md).
{% endhint %}

{% hint style="warning" %}
**Outbound IPs**

You might need to whitelist our IPs for some of our pull-based Listeners. For Falcon-based cloud Onum deployements, our outbound IPs are:

* `54.76.153.190`
* `52.209.110.159`
* `3.255.0.156`

For other cloud-based deployments, please contact Customer Sucess to gather information about the outbound IPs.
{% endhint %}

### On-premises deployment

In on-premises deployments, either either a CrowdStrike team or a partner will set up the new account. Appropriate access permissions are granted to allow Onum to perform the installation.

A validation script is run to confirm all prerequisites are met and connectivity is established, ensuring a smooth installation process. Once installed, you can access your tenant, start ingesting data, invite users, and take full advantage of Onum’s capabilities.

You must allocate the disk space to `/opt` on the installation machine.

{% hint style="info" %}
**Dependencies:**

* Docker
* Packages:
  * `gpg`
  * `curl`
  * `ipvsadm`
  * `ca-certificates`
* SIEM access
* Access to sources
  {% endhint %}

## Hardware requirements

Hardware (per Virtual Machine):

* Distribution: Linux (Debian or Red Hat)
* Server Hardware: 16GB RAM and 8 CPU
* Disk Storage: At least 500GB

## Access

In case of upcoming system maintenance, we kindly seek permission to access the customer infrastructure. We aim to ensure seamless operations and address any potential issues promptly.


---

# Agent Instructions: 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:

```
GET https://docs.onum.com/getting-started/deployment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.