Skip to content

Network Infrastructure Requirements

This document outlines the network requirements for devices connected to the PhyStack platform. It includes information about offline support, IP whitelisting, and domain-specific configurations based on your tenant’s data residency.

For Screen Apps, devices must connect to the internet at least once to download content and assets. All apps, assets, and web resources will be downloaded on first launch and will function offline once the content has been downloaded. Internet-based functionality will be suspended until the device is connected again. A sync will take place to update according to the console when the device reconnects to the internet after being offline.

For devices running PhyOS v1.0.3 or higher, whitelist the following IP addresses based on tenant’s data-residency to establish connectivity to the PhyStack platform.

IP AddressPortProtocolDescription
20.103.183.92443TCP & UDPProvisioning
20.211.138.232443TCP & UDPPost-provisioning
IP AddressPortProtocolDescription
20.103.183.92443TCP & UDPProvisioning
20.126.185.169443TCP & UDPPost-provisioning
IP AddressPortProtocolDescription
20.103.183.92443TCP & UDPProvisioning
20.219.43.36443TCP & UDPPost-provisioning
IP AddressPortProtocolDescription
20.103.183.92443TCP & UDPProvisioning
20.233.13.206443TCP & UDPPost-provisioning
IP AddressPortProtocolDescription
20.103.183.92443TCP & UDPProvisioning
20.121.94.131443TCP & UDPPost-provisioning

For devices running PhyOS v2 or higher, whitelist the following IP addresses based on tenant’s data-residency to establish connectivity to the PhyStack platform.

IP AddressPortProtocolDescription
20.240.22.238443TCPProvisioning
4.147.66.95443TCPPost-provisioning
IP AddressPortProtocolDescription
20.240.22.238443TCPProvisioning / Post-provisioning
IP AddressPortProtocolDescription
20.240.22.238443TCPProvisioning
20.244.60.6443TCPPost-provisioning
IP AddressPortProtocolDescription
20.240.22.238443TCPProvisioning
20.203.114.39443TCPPost-provisioning
IP AddressPortProtocolDescription
20.240.22.238443TCPProvisioning
20.237.18.225443TCPPost-provisioning

For employee devices that work with the PhyStack/PhyGrid productivity and clienteling tools, the following domains need to be whitelisted in your firewall.

DomainDescription
api.omborigrid.com
api.phygrid.com
api.phystack.com
PhyStack API
screen.omborigrid.com
screen.phygrid.com
screen.phystack.com
PhyStack Screen Apps
queue-us.ombori.comEmployee Queue Web UI US Region
tasks-us.ombori.comEmployee Task Web UI US Region
realtime-us.omborigrid.com
realtime-us.phygrid.com
realtime-us.phystack.com
PhyStack Realtime Channel
analytics.omborigrid.com
analytics.phygrid.com
analytics.phystack.com
Analytics Service
DomainDescription
api.omborigrid.com
api.phygrid.com
api.phystack.com
PhyStack API
screen.omborigrid.com
screen.phygrid.com
screen.phystack.com
PhyStack Screen Apps
queue-eu.ombori.comEmployee Queue Web UI EU Region
tasks-eu.ombori.comEmployee Task Web UI EU Region
realtime-eu.omborigrid.com
realtime-eu.phygrid.com
realtime-eu.phystack.com
PhyStack Realtime Channel
analytics.omborigrid.com
analytics.phygrid.com
analytics.phystack.com
Analytics Service
DomainDescription
api.omborigrid.com
api.phygrid.com
api.phystack.com
PhyStack API
screen.omborigrid.com
screen.phygrid.com
screen.phystack.com
PhyStack Screen Apps
queue-au.ombori.comEmployee Queue Web UI AU Region
tasks-au.ombori.comEmployee Task Web UI AU Region
realtime-au.omborigrid.com
realtime-au.phygrid.com
realtime-au.phystack.com
PhyStack Realtime Channel
analytics.omborigrid.com
analytics.phygrid.com
analytics.phystack.com
Analytics Service
DomainDescription
api.omborigrid.com
api.phygrid.com
api.phystack.com
PhyStack API
screen.omborigrid.com
screen.phygrid.com
screen.phystack.com
PhyStack Screen Apps
queue-uae.ombori.comEmployee Queue Web UI UAE Region
tasks-uae.ombori.comEmployee Task Web UI UAE Region
realtime-uae.omborigrid.com
realtime-uae.phygrid.com
realtime-uae.phystack.com
PhyStack Realtime Channel
analytics.omborigrid.com
analytics.phygrid.com
analytics.phystack.com
Analytics Service
DomainDescription
api.omborigrid.com
api.phygrid.com
api.phystack.com
PhyStack API
screen.omborigrid.com
screen.phygrid.com
screen.phystack.com
PhyStack Screen Apps
queue-in.ombori.comEmployee Queue Web UI IN Region
tasks-in.ombori.comEmployee Task Web UI IN Region
realtime-in.omborigrid.com
realtime-in.phygrid.com
realtime-in.phystack.com
PhyStack Realtime Channel

For devices such as Tizen, Android, third-party digital signage systems, or any other device utilizing PhyStack Screen applications within a web browser, the following firewall configurations are necessary:

DomainDescription
app.omborigrid.com
app.phygrid.com
app.phystack.com
PhyStack App Releases
storage.googleapis.comGoogle Workbox
media.omborigrid.com
media.phygrid.com
media.phystack.com
PhyStack Media
tts-proxy.northeurope.cloudapp.azure.comTTS Service
o190418.ingest.sentry.ioSentry Error Reporting
analytics.omborigrid.com
analytics.phygrid.com
analytics.phystack.com
Analytics Service
api.omborigrid.com
api.phygrid.com
api.phystack.com
PhyStack API
qr.runURL Shortener Service
installations-service.omborigrid.com
installations-service.phygrid.com
installations-service.phystack.com
PhyStack Installations Service
tizen.omborigrid.com
tizen.phygrid.com
tizen.phystack.com
PhyStack Tizen Supervisor
gridhealth.blob.core.windows.netScreenshot and device status service
realtime-au.omborigrid.com
realtime-au.phygrid.com
realtime-au.phystack.com
PhyStack Signals - Realtime events
realtime-eu.omborigrid.com
realtime-eu.phygrid.com
realtime-eu.phystack.com
PhyStack Signals - Realtime events
realtime-in.omborigrid.com
realtime-in.phygrid.com
realtime-in.phystack.com
PhyStack Signals - Realtime events
realtime-uae.omborigrid.com
realtime-uae.phygrid.com
realtime-uae.phystack.com
PhyStack Signals - Realtime events
realtime-us.omborigrid.com
realtime-us.phygrid.com
realtime-us.phystack.com
PhyStack Signals - Realtime events

Advanced Scenario: Firewall Openings for Internal System Integration

Section titled “Advanced Scenario: Firewall Openings for Internal System Integration”

In advanced scenarios where PhyStack needs to communicate with internal retailer systems, such as querying inventory and product information APIs, you may need to open specific firewall ports to allow inbound traffic from PhyStack. This is not our standard approach for integration and should only be used when necessary. In these cases, you should whitelist the following IP addresses, based on your tenant’s Data Residency.

Global (required for all data residencies)

Section titled “Global (required for all data residencies)”
IP Address
20.91.176.195
20.240.8.184
20.103.188.246
20.103.191.105
IP Address
20.193.43.178
20.193.43.210
IP Address
20.240.25.169
20.240.25.198
IP Address
20.207.65.55
20.204.234.88
IP Address
20.203.77.64
20.203.77.62
IP Address
20.232.86.63
20.121.248.244

Please note that the specific ports and protocols used will vary depending on your internal system requirements. Consult your internal IT team for the appropriate configuration.