What Genesis can send, and where
Genesis talks to two Genesis Computing hosts. Each kind of data has its own switch.
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 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.
stats.genesiscomputing.ai. Pick the one that fits:
DISABLEDkeeps only the billing counts, in a local database on your install. It is the simplest choice.SQLalso keeps the other metrics in your install’s local metrics database. Choose it if you want your own operators to see them.LOGSwrites 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 toenhancements.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_docsistrue, 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.
Helm
Add these to your values file underconfig.extraEnv. Quote every value. Then run helm upgrade with the same values file.
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.
Docker
Add these lines to~/.genesis/config.env and restart genesis_server.
-e NAME=value options.
Databricks App
Log sharing never runs in a Databricks App, so it needs no setting. Add the metrics setting to theenv list in the App’s app.yaml, then restart the App.
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
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
- Open Config > Advanced Settings. Confirm
support.log_shipping.enabledisfalseandmetrics.modeisDISABLED(orSQL). Values set from the environment show as locked. - Open Settings > Genesis Enhancements > Connectivity & Delivery Settings. Confirm Autosend Enabled is off and Receiver Base URL is empty.
- After the restart, search
logs/app.logforMetrics disabled (metrics.mode=DISABLED). WithSQL, look forMetrics service initialized: SQLinstead. - 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.aior any of its subdomains, includingstats.genesiscomputing.aiandenhancements.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. - If you do see one, find which switch covers that host in the table at the top, and set it.

