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

# Network Requirements

> Hostnames, ports, and firewall rules a gateway needs, for IT review

This page lists the network access a gateway needs, for IT teams approving a deployment.

## Summary

* **Outbound only, HTTPS on port 443.** All communication with Atomscale uses TLS. There is no HTTP fallback.
* **No inbound access from the internet.** The gateway opens no internet-facing ports.
* **Local inbound exceptions**, each limited to the local subnet: UDP from GigE Vision RHEED cameras, and TCP to a [Connection Sharing](https://docs.atomscale.ai/gateway/connection-sharing.md) Hub if you use one.
* **Integrations don't connect to Atomscale.** They hand data to the desktop app, which makes every upload. A RHEED camera integration receives its camera's stream and sends read-only camera discovery queries on the local network.
* **System proxy settings are respected** in the default **Normal** connection mode.

## Hostnames

Allow HTTPS (TCP 443) to these hostnames. If your proxy or firewall supports exact hostnames, use them; the gateway doesn't need wildcard access. A Connection Sharing Hub relays only these hostnames.

### Atomscale Platform

| Hostname | Purpose |
| - | - |
| `api.atomscale.ai` | Atomscale API: gateway status and commands, clock measurement, tool log and timeseries uploads, and upload coordination |
| `app.atomscale.ai` | Atomscale web application |
| `clerk.atomscale.ai`, `accounts.atomscale.ai` | Sign-in and session management |

### File Storage (Amazon S3, us-east-1)

RHEED frames, large files, and integration downloads go directly to Amazon S3 using short-lived signed URLs. Each bucket is reached at both `<bucket>.s3.amazonaws.com` and `<bucket>.s3.us-east-1.amazonaws.com`.

| Bucket | Purpose |
| - | - |
| `prod-rheed-stream` | Live RHEED frame uploads |
| `prod-rheed-staging` | File uploads |
| `prod-rheed-raw`, `prod-rheed-processed` | Viewing stored and processed data in the app |
| `prod-atomscale-reference-data` | Reference data used by the app |
| `prod-atomscale-adapters` | Integration downloads and updates |

### Desktop App Updates

| Hostname | Purpose |
| - | - |
| `atomscale-desktop-updates.s3.us-east-1.amazonaws.com` | Desktop app update checks and downloads |

### Sign-In and Supporting Services

| Hostname | Purpose |
| - | - |
| `clerk.com`, `clerk.dev`, `clerk.accounts.dev`, `img.clerk.com`, `clerk-telemetry.com` | Sign-in provider |
| `challenges.cloudflare.com` | Bot protection on the sign-in page |
| `fonts.googleapis.com`, `fonts.gstatic.com` | Interface fonts |
| `browser-intake-datadoghq.com` | Application diagnostics (see [Diagnostic Data](#diagnostic-data)) |

Social and SSO sign-in open in the computer's default browser, so your identity provider's hostnames must be reachable from the browser rather than from Atomscale.

## Ports

| Port | Direction | Purpose |
| - | - | - |
| TCP 443 | Outbound | All communication with Atomscale. Every gateway, or only the Hub for Outposts. |
| TCP 8484 (configurable, 1024 to 65535) | Inbound from the local subnet | Hub only: Outposts connecting through the Hub. |
| UDP, camera stream port | Inbound from the local subnet | Gateways with a GigE Vision RHEED camera: camera frames. |
| UDP 3956 (GVCP) | Outbound to the local subnet | Gateways with a GigE Vision RHEED camera: read-only camera discovery (**Detect**). |

## Windows Firewall Rules

The desktop app installs per user, without administrator rights. A few features need an inbound firewall rule, and each asks for administrator approval once.

| Rule name | Created when | Scope |
| - | - | - |
| `Atomscale Adapter rheed-gentl (<integration ID>) (UDP)` | A RHEED camera integration first starts without admin access, for example with **Standard (GenTL)** | UDP, local subnet, that integration's program only |
| `Atomscale Connection Sharing (TCP)` | Hub mode is first turned on at the computer | TCP, local subnet, the Atomscale program only |
| `Atomscale Elevated RHEED (Atomscale:<integration ID>) (UDP)` | An integration starts with [Integration admin access](https://docs.atomscale.ai/gateway/admin-access.md), such as RHEED with **Network (GVSP Tap)**. Created by the protected launcher, with no prompt. | UDP, local subnet, the protected copy of that integration only. Removed when admin access is turned off. |

If approval is declined, the app continues without the rule and shows a warning. You can instead create equivalent rules through your own policy. Installations that turned on admin access with an older desktop app may also have an `Atomscale-Elevated-Adapter Application (TCP)` rule; it is no longer created, and is removed when admin access is turned off.

> [!NOTE]
>
> The integration and Connection Sharing rules are not removed when an integration or the app is
> uninstalled. To clean them up, remove the rules whose names start with `Atomscale` in Windows
> Defender Firewall, or with PowerShell as an administrator.

```powershell theme={null}
Get-NetFirewallRule -DisplayName "Atomscale*" | Select-Object DisplayName, Enabled
```

## Credentials and Integration Programs

* **Integrations hold no credentials.** Each integration runs as a separate local process and hands its data to the desktop app. Uploads are authenticated with short-lived tokens tied to the signed-in user.
* **Sign-in session.** To keep you signed in across restarts, the app stores your session on disk, encrypted with Windows DPAPI.
* **Device secret.** A random secret created for each installation, under `%APPDATA%\Atomscale\gateway\`, identifies the computer to Atomscale. See [Files and Logs](https://docs.atomscale.ai/gateway/reference/files-and-logs.md).
* **Verified downloads.** Integration programs download from Atomscale over HTTPS and are checked against a SHA-256 checksum before they're installed.

## Long-Lived Connections

The gateway keeps a long-lived HTTPS connection to `api.atomscale.ai` to receive remote commands as server-sent events. Proxies must pass this stream through without buffering. If a proxy buffers or cuts it, the gateway still works and picks up commands on its regular 10-second status report, only more slowly.

## Diagnostic Data

To help Atomscale support troubleshoot, the desktop app sends application logs to Datadog (`browser-intake-datadoghq.com`). These logs include:

* The computer name, the Windows user name, and the device ID.
* The signed-in Atomscale user and organization IDs, and the email of whoever sent a remote command.
* The app version and operating system.
* Integration events and errors, including each integration's configuration when it is applied, such as folder paths and camera addresses.
* Sign-in connection diagnostics, such as whether sign-in is reached directly or through a proxy and network error codes, without URLs or proxy addresses.

Logs don't include the instrument data itself. The same logs are also written locally; see [Files and Logs](https://docs.atomscale.ai/gateway/reference/files-and-logs.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.