Networking

At the highest level, regardless of deployment:

1. Salesforce needs to talk to your instance of GRAX
2. Your users need to talk to your instance of GRAX
3. Your instance of GRAX needs to talk to Salesforce
4. Your instance of GRAX needs to talk to hq.grax.com
5. hq.grax.com needs to talk to Salesforce
6. Your instance of GRAX needs to talk to your database
7. Your instance of GRAX needs to talk to your storage

GRAX Cloud Network Architecture

Communication Details

Salesforce Talks to GRAX

Lightning Web Components and Embedded Pages are all driven by Salesforce to GRAX traffic. Salesforce publishes their global IP ranges. Allow, at a minimum, the IP ranges for your Salesforce instance region to access the GRAX application API.

Connecting to GRAX from Salesforce requires a Remote Site Setting in SFDC.

Users Talk to GRAX

The GRAX webapp user interface depends on traffic between the browsers of user and GRAX. Allow, at a minimum, your corporate network/VPN to access the GRAX application APIs.

GRAX Talks to Salesforce

To query, update, or insert information in salesforce, GRAX utilizes the REST and Composite APIs. Allow, at a minimum, at least one static IP for your GRAX application to communicate out to Salesforce.

GRAX Talks to GRAX HQ

For software updates, telemetry, and license monitoring, GRAX communicates with GRAX HQ. Allow the GRAX application to access hq.grax.com (3.232.229.75) over HTTPS.

GRAX HQ Talks to Salesforce

For processing of OAuth sessions and logins, GRAX HQ must authenticate against your Salesforce org. Allow hq.grax.com (3.232.229.75) to communicate with your org.

GRAX Talks to Database

For metadata storage, search indexing, and storage optimizations, GRAX uses Postgres. Allow the GRAX application to access your configured Postgres database.

GRAX Talks to Storage

For longterm storage and History Stream, GRAX uses blob storage platforms. Allow the GRAX application to access your chosen blob storage bucket/platform.