# On-Premises Integrations

Arnica provides 2 deployment options for on-premises SCMs.

## SaaS

Customers with on-premises SCM deployments that can allow network traffic between Arnica's SOC2 Type 2 certified environment and the SCMs can use this option.

### Ingress traffic

Arnica ingests data from SCMs via API and git commands - all over TLS 1.2 and above. The following source IP addresses need to be able accessing the SCMs:

#### Arnica US

* 18.221.115.1
* 3.14.104.231
* 3.14.211.193
* 3.23.28.237
* 13.58.11.157
* 3.143.46.92
* 18.221.211.0
* 3.23.227.208

#### Arnica EU

* 18.199.13.52
* 3.126.241.142
* 52.59.152.69

### Egress traffic

In order to enable real-time scanning capabilities, all traffic to `https://api.app.arnica.io/` or `https://api.app.eu.arnica.io/` (Based on the Arnica region) needs to be allowed over TLS 1.2 and above.

{% hint style="info" %}
For more information about how Arnica handles your data, please visit the [Data Handling page](/arnica-documentation/security/data-handling.md).
{% endhint %}

## On-Premises

Arnica supports on-prem deployments in Kubernetes. Please [contact us](mailto:contact@arnica.io) for more information.


---

# 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.arnica.io/arnica-documentation/getting-started/on-premises-integrations.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.