For air-gapped environments, Permit.io offers on-premises deployment options that don't require external Git repository access (1) . The on-premises deployment includes all necessary components within your infrastructure, specifically designed for air-gapped environments with no internet connectivity required . This deployment includes the complete Permit Platform (Control Plane) with frontend, backend services, OPAL Server, and a Policy Sync service . The Policy Sync service in the on-premises setup synchronizes authorization policies from an internal Git repository to OPAL . Since this is within your own infrastructure, you can use an internal, air-gapped Git repository rather than an external one . The architecture shows that policies in Rego format (OPA) are synced to OPAL via the Policy Sync service, which then distributes them to your sidecar PDPs . This means the Git repository can be hosted entirely within your air-gapped environment . The on-premises deployment supports Kubernetes/OpenShift and includes air-gapped installation as a core feature . Security features include SSH Key Authentication for secure Git repository access within your infrastructure . ​*Note*​: On-premises deployment is only available to Enterprise customers who have acquired an on-prem license . For more details on setting up this architecture, you can refer to the [On-Premises Deployment guide](https://docs.permit.io

To learn more, see the sources I considered: [[1] On-Premises Deployment](https://docs.permit.io/how-to/deploy/on-prem/landing)