> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genesiscomputing.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Restricted networks: sending no data to Genesis

> Run a self-hosted Genesis so that it sends nothing to Genesis Computing. Settings for Helm, Docker and Databricks Apps, a network deny rule, and how to check it.

Some installs must not send any data to a vendor. Examples are regulated healthcare data and networks with strict egress rules. This page shows how to run a self-hosted Genesis so that it sends nothing to Genesis Computing.

It covers installs you run yourself: Docker, the Genesis Helm chart on any Kubernetes cluster, and a Databricks App.

## What Genesis can send, and where

Genesis talks to two Genesis Computing hosts. Each kind of data has its own switch.

| What | Host | Default | How to stop it |
| - | - | - | - |
| Server log sharing | `enhancements.genesiscomputing.ai` | Off by default. Runs only in Docker or Helm installs where an administrator turned it on. Never runs in a Databricks App. | `support.log_shipping.enabled` = `false` |
| Usage metrics | `stats.genesiscomputing.ai` | On, in every deployment. | `metrics.mode` = `DISABLED` or `SQL` |
| Support and enhancement reports | `enhancements.genesiscomputing.ai` | Nothing is sent until an administrator turns on auto-send, or a person confirms sending one report. | Empty **Receiver Base URL** in the Genesis Enhancements settings |

The sections below explain each one.

### Server log sharing

Log sharing is **off by default**. A Docker or Helm install shares its server log (`logs/app.log`, `INFO` and above) with Genesis support only after an administrator turns it on. Secrets and email addresses are removed before the log leaves the install. The install also says who runs it and where. See [Logs sent to Genesis Computing](https://docs.genesiscomputing.com/docs/deployments/Docker/Genesis-Container-Distribution.md#logs-sent-to-genesis-computing) for the full list.

To keep it off for good, set `GENESIS__SUPPORT__LOG_SHIPPING__ENABLED` to `false` in the environment, as shown below. The value is then locked in **Config > Advanced Settings**, so no one can turn it on from the UI. Anything logged while it is off is never sent, even if it is turned on later.

### Usage metrics

`metrics.mode` is `BRIDGE` by default. In that mode Genesis uploads to `stats.genesiscomputing.ai` about once an hour:

* usage counts that Genesis Credits are priced on,
* activity counts,
* diagnostic counts, such as LLM calls and tokens with the model name, and tool call counts,
* facts about the install: the operating-system user and machine name, cloud account, region and instance, the type and host of data connections, and the email domain and a hash of the address for people who signed in.

It never sends prompts, answers or SQL. See [Metrics](https://docs.genesiscomputing.com/docs/Setup/Metrics.md) for the counts.

Any other mode uploads nothing to `stats.genesiscomputing.ai`. Pick the one that fits:

* `DISABLED` keeps only the billing counts, in a local database on your install. It is the simplest choice.
* `SQL` also keeps the other metrics in your install's local metrics database. Choose it if you want your own operators to see them.
* `LOGS` writes metrics to the server log instead.

### Support and enhancement reports

A person can file a support or enhancement report from Genesis. The report can include a server log or a thread export. It is sent to `enhancements.genesiscomputing.ai` only in two cases: an administrator turned on auto-send, or the person confirmed sending that one report. Auto-send is off by default.

To block sending entirely, an administrator opens **Settings > Genesis Enhancements**, then **Connectivity & Delivery Settings**, clears **Receiver Base URL** and saves. With no URL, Genesis refuses to send a report and marks it as failed to send. Reports stay on your install. You can still export them offline from the same page.

This setting is stored in your install's enhancement store. It is not an environment variable. Setting it needs the configuration panel permission, which only the administrator role has by default.

## What stays inside your network

* **Licenses.** Genesis checks a license against a public key built into the product. It does not call Genesis Computing.
* **Models.** Requests go to the LLM provider you configure, such as your own Azure OpenAI, Bedrock, Databricks or an internal LiteLLM proxy. Nothing is routed through Genesis Computing.
* **Updates.** Genesis does not check for new versions. You pull the image or chart from your own registry when you choose to upgrade.
* **OpenTelemetry.** Tracing and metrics export go only to the OTLP endpoint you set. The default endpoint is `localhost`. Trace content such as prompts is off by default.
* **In-app help.** Help links stay inside your install while `docs.use_internal_docs` is `true`, which is the default.

## Settings to copy

Every setting is a Genesis configuration key. To set one as an environment variable, write the key in capitals, use `__` between the parts, and start with `GENESIS__`. For example, `support.log_shipping.enabled` becomes `GENESIS__SUPPORT__LOG_SHIPPING__ENABLED`. A value set this way wins over a value saved in the UI, and **Config > Advanced Settings** shows it as locked.

| Key | Environment variable | Value |
| - | - | - |
| `support.log_shipping.enabled` | `GENESIS__SUPPORT__LOG_SHIPPING__ENABLED` | `false` |
| `metrics.mode` | `GENESIS__METRICS__MODE` | `DISABLED` (or `SQL`) |
| Receiver Base URL (Genesis Enhancements settings) | none, set in the UI | empty |

### Helm

Add these to your values file under `config.extraEnv`. Quote every value. Then run `helm upgrade` with the same values file.

```yaml theme={null}
config:
  extraEnv:
    GENESIS__SUPPORT__LOG_SHIPPING__ENABLED: "false"
    GENESIS__METRICS__MODE: "DISABLED"
```

Do not change `GENESIS_DISTRIBUTION`. The chart sets it, and the log sharing switch above is the way to turn sharing off. See the [Helm Chart Values Reference](https://docs.genesiscomputing.com/docs/deployments/Helm-Chart-Values-Reference.md).

### Docker

Add these lines to `~/.genesis/config.env` and restart `genesis_server`.

```env theme={null}
GENESIS__SUPPORT__LOG_SHIPPING__ENABLED=false
GENESIS__METRICS__MODE=DISABLED
```

If you start the container yourself, pass the same two as `-e NAME=value` options.

### Databricks App

Log sharing never runs in a Databricks App, so it needs no setting. Add the metrics setting to the `env` list in the App's `app.yaml`, then restart the App.

```yaml theme={null}
env:
  - name: GENESIS__METRICS__MODE
    value: "DISABLED"
```

A Databricks App keeps a local pool of Genesis Credits. Turning metrics off does not remove the pool. See [Genesis on Databricks](https://docs.genesiscomputing.com/docs/deployments/Databricks/Genesis-On-Databricks.md).

### Then clear the Receiver Base URL

The last setting is not an environment variable. After the install is running, sign in as an administrator, open **Settings > Genesis Enhancements > Connectivity & Delivery Settings**, clear **Receiver Base URL** and save.

## Block the hosts as a second layer

A setting can be changed back by an administrator. A network rule cannot. Deny egress from the Genesis pods or containers to:

* `*.genesiscomputing.ai`

Genesis works with these hosts blocked. Nothing in startup needs them. Every connection to them is optional: a blocked send is logged as a warning, and the install keeps running. Your image and chart come from your own registry, and your LLM provider is on a different host.

> [!NOTE]
>
> The settings above are the switch. The deny rule is a safety net. With the rule in place and the settings on, you should see no blocked connections at all. A blocked connection means a setting is missing.

## Check it

1. Open **Config > Advanced Settings**. Confirm `support.log_shipping.enabled` is `false` and `metrics.mode` is `DISABLED` (or `SQL`). Values set from the environment show as locked.
2. Open **Settings > Genesis Enhancements > Connectivity & Delivery Settings**. Confirm **Autosend Enabled** is off and **Receiver Base URL** is empty.
3. After the restart, search `logs/app.log` for `Metrics disabled (metrics.mode=DISABLED)`. With `SQL`, look for `Metrics service initialized: SQL` instead.
4. Watch your firewall, proxy or DNS logs for an hour or more. Metrics used to upload about once an hour. You should see no lookups or connections from Genesis (the Helm pods, the Docker container or the Databricks App) to `genesiscomputing.ai` or any of its subdomains, including `stats.genesiscomputing.ai` and `enhancements.genesiscomputing.ai`. Match on the domain suffix, not the exact name. If your firewall logs show only IP addresses, resolve those hosts first and check for their addresses.
5. If you do see one, find which switch covers that host in the table at the top, and set it.

## See also

* [Metrics](https://docs.genesiscomputing.com/docs/Setup/Metrics.md)
* [Support and Enhancements](https://docs.genesiscomputing.com/docs/Setup/Support-And-Enhancements.md)
* [Genesis Container Distribution](https://docs.genesiscomputing.com/docs/deployments/Docker/Genesis-Container-Distribution.md)
* [Helm Chart Values Reference](https://docs.genesiscomputing.com/docs/deployments/Helm-Chart-Values-Reference.md)
