> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/security-hardening/network-security-hardening/allowlist-guide.md).

# The "Allowlist" Guide

Firewall and proxy allowlist domains and URLs required for We360.ai connectivity.

Client connections to We360-hosted services use **HTTPS or WSS on TCP port 443**. Confirm the required destinations and ports for on-premises servers, including installation and maintenance traffic, with We360.

**The wildcard rules and host list below describe We360-hosted services.** For on-premises deployments, see [On-premises deployments](#on-premises-deployments).

**Wildcard rules (strongly recommended):**

| Domain pattern  | Notes                                                                        |
| --------------- | ---------------------------------------------------------------------------- |
| `*.we360.ai`    | Covers all <code class="expression">space.vars.company\_name</code> services |
| `*.in.we360.ai` | India-region endpoints                                                       |

**Individual URL fallback list** (use if your firewall does not support wildcards):

| URL                              | Purpose                                                                                                                                                                                                                                                                                                                                                                  |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `https://portal.we360.ai`        | Admin portal; delivers installers and agent updates                                                                                                                                                                                                                                                                                                                      |
| `https://assets.we360.ai`        | Configuration bundles                                                                                                                                                                                                                                                                                                                                                    |
| `https://assets.v2.we360.ai`     | Configuration bundles (v2)                                                                                                                                                                                                                                                                                                                                               |
| `https://origin.in.we360.ai`     | Tenant discovery / bootstrap: returns tenant + device manifests (API gateway and auth-server addresses) and version metadata. Carries tenant/device identifiers and install telemetry only — no captured user data. **Optional when devices are pre-provisioned with `zs-origin.json` — may then be blocked entirely (see&#x20;*****Pre-Provisioned Origin Data*****).** |
| `https://origin.global.we360.ai` | Tenant discovery / bootstrap (see above); same pre-provisioning exemption applies                                                                                                                                                                                                                                                                                        |
| `https://api.in.we360.ai`        | Primary API endpoint: REST (HTTPS) and real-time livestream (WSS), both on port 443                                                                                                                                                                                                                                                                                      |
| `https://auth.in.we360.ai`       | Issues and refreshes authentication tokens for agent-to-backend communication                                                                                                                                                                                                                                                                                            |
| `https://<base_domain>.we360.ai` | Customer admin console (e.g., `acme.we360.ai`)                                                                                                                                                                                                                                                                                                                           |
| `https://support-edge.we360.ai`  | Support ticket fallback: keeps "Raise a ticket" and the public support form working when the main API is unavailable (see *Support system* below)                                                                                                                                                                                                                        |

#### Support system

Support tickets are raised from the admin console (**Help → Raise a ticket**) and from the public support page at `https://portal.we360.ai/support`, which works without signing in. These are browser connections from your users' machines, not agent traffic.

| URL                                 | Purpose                                                                                                                                                            |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `https://portal.we360.ai`           | Public support page (`/support`) and ticket status links in support emails                                                                                         |
| `https://origin.in.we360.ai`        | Receives tickets from the public support page                                                                                                                      |
| `https://api.in.we360.ai`           | Receives tickets raised from inside the admin console                                                                                                              |
| `https://support-edge.we360.ai`     | **Fallback intake.** If the main API is unreachable, tickets are sent here instead so they are never lost. Allow it for full availability of the support system.   |
| `https://challenges.cloudflare.com` | Cloudflare Turnstile human-verification check shown on the public support page. This host is **outside `we360.ai`**, so a `*.we360.ai` wildcard does not cover it. |

The `*.we360.ai` wildcard already covers every support endpoint except `challenges.cloudflare.com`. If `support-edge.we360.ai` is blocked, support still works normally; only the fallback during an outage is lost. If `challenges.cloudflare.com` is blocked, the public support page cannot submit tickets, though tickets raised from inside the admin console are unaffected.

#### On-premises deployments

Use the exact destinations and ports confirmed for your deployment rather than assuming the hosted addresses above apply:

* **API and authentication:** allow your deployment's API and authentication addresses. Proxies and firewalls must support secure WebSocket connections for real-time features.
* **Portal, configuration, installers, and updates:** allow the locations confirmed for your deployment; some may remain We360-hosted.
* **Screenshots and recordings:** allow the configured media-upload destinations, including storage host names where direct uploads are used.

Block public origin access from devices only after deploying and validating the supported pre-provisioned configuration. See [Pre-Provisioned Origin Data](https://docs.we360.ai/deployment-and-it-ops/security-hardening/network-security-hardening/pre-provisioned-origin-data). On-premises hosting alone doesn't remove this requirement.

Use the deployment-specific destinations and ports supplied by We360 for licensing, server-side dependencies, installation, and maintenance. See [On-Premise and BYOC](https://docs.we360.ai/deployment-and-it-ops/deploy/infrastructure-management-on-premise#network-and-ingress).

#### Screen recording & screenshot uploads

Screenshots and recordings use the upload route configured for your deployment. Uploads may pass through your deployment's API endpoint or go directly to object storage using short-lived, pre-signed links. For direct uploads, use the storage host names supplied for your deployment; these may be outside `we360.ai`.

* As with all agent traffic, **exclude these uploads from SSL/TLS inspection**. The upload links are cryptographically signed and a proxy that alters the request will cause the upload to be rejected.
* If a media upload fails, tracking continues normally and the file is kept for retry; a blocked direct upload may fall back to the data relay. Files that remain on the device without uploading for 30 days are pruned.

#### Cloudflare IP addresses for We360-hosted endpoints

<code class="expression">space.vars.company\_name</code> sits behind Cloudflare. Domain-based rules are preferred; the IPs below are provided as a supplementary reference for environments where only IP-based rules are possible.

The Cloudflare addresses below apply to We360-hosted endpoints. For on-premises endpoints, use the destination addresses confirmed for your deployment; these Cloudflare ranges aren't automatically required.

| IP              | Notes      |
| --------------- | ---------- |
| `104.26.15.125` | Cloudflare |
| `104.26.14.125` | Cloudflare |
| `172.67.72.141` | Cloudflare |

These addresses may change through Cloudflare anycast re-routing. To future-proof your rules, allow all Cloudflare proxy ranges. The authoritative and machine-readable lists are maintained at:

* **Human-readable:** <https://www.cloudflare.com/ips/>
* **IPv4 list:** <https://www.cloudflare.com/ips-v4>
* **IPv6 list:** <https://www.cloudflare.com/ips-v6>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.we360.ai/deployment-and-it-ops/security-hardening/network-security-hardening/allowlist-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
