Home Getting Started System Requirements and Supported Devices

System Requirements and Supported Devices

Last updated on Apr 17, 2026

System Requirements and Supported Devices

KyberGate is designed to work across the full spectrum of devices found in K-12 environments. This article covers platform support, minimum requirements, and network prerequisites for a successful deployment.


Before You Begin

Review this article before purchasing devices or planning a deployment to ensure full compatibility with KyberGate's proxy-based filtering architecture.


Supported Platforms

iPad (iOS/iPadOS)

  • Minimum OS: iPadOS 15.0 or later
  • Enrollment method: MDM profile (PAC file + CA certificate)
  • Supported MDMs: Jamf Pro, Mosyle, Kandji, Apple Business Manager
  • Requirements:
    • Device must be supervised (enrolled in Apple Business/School Manager)
    • MDM must support Global HTTP Proxy or PAC file configuration
    • Wi-Fi connectivity required

Chromebook (ChromeOS)

  • Minimum OS: ChromeOS 100 or later
  • Enrollment method: Chrome extension (force-installed via Google Admin)
  • Requirements:
    • Device must be managed through Google Admin Console
    • Chrome extension force-installed at the OU level
    • Google Workspace for Education account required

macOS

  • Minimum OS: macOS 12 (Monterey) or later
  • Enrollment method: Native KyberGate Agent (.pkg installer)
  • Requirements:
    • Admin privileges for initial installation
    • MDM recommended for silent deployment (Jamf Pro, Mosyle, Kandji)
    • Agent auto-configures proxy and installs CA certificate

Windows

  • Minimum OS: Windows 10 (version 1903) or later / Windows 11
  • Enrollment method: Native KyberGate Agent (.msi installer)
  • Requirements:
    • Administrator privileges for installation
    • .NET Runtime 6.0 or later (bundled with installer)
    • Can be deployed via GPO, SCCM, Intune, or manual installation

Network Requirements

KyberGate uses a cloud proxy architecture with SSL/MITM inspection. Your network must allow the following:

Requirement Details
Outbound HTTPS (443) Required — all filtering traffic flows over HTTPS to KyberGate proxy servers
Outbound HTTP (80) Required — for PAC file delivery and HTTP site inspection
Proxy ports (8080, 8443) Required — KyberGate proxy communication ports
PAC file URL Must be accessible from all devices: https://pac.kybergate.com/proxy.pac
CA Certificate Must be installed as a trusted root on all filtered devices
DNS Standard DNS resolution required; KyberGate does not require custom DNS servers

Proxy Network Regions

KyberGate operates proxy servers in 8 global regions with smart geo-routing via the PAC file:

  1. US East (New York) — Primary for East Coast schools
  2. US West (Los Angeles) — Primary for West Coast schools
  3. US Southeast (Atlanta)
  4. US Midwest (Chicago)
  5. US South (Dallas)
  6. US Northwest (Seattle)
  7. EU West (London)
  8. APAC (Singapore)

The PAC file automatically routes traffic to the nearest available proxy server for optimal performance.

💡 Pro Tip: If your school uses a firewall with outbound filtering, whitelist *.kybergate.com and the proxy IP ranges provided in your admin dashboard under Settings → Network.


Browser Compatibility

Browser Support Level
Google Chrome Full (recommended)
Safari Full (via system proxy on macOS/iOS)
Microsoft Edge Full (Chromium-based)
Mozilla Firefox Partial — requires manual proxy configuration (Firefox uses its own proxy settings)
Brave Full (Chromium-based)

⚠️ Important: Firefox does not honor system-level proxy settings by default. For Firefox to work with KyberGate, you must configure network.proxy.type via GPO or enterprise policy. We recommend using Chrome or Edge for the simplest deployment.


Bandwidth Requirements

KyberGate's proxy adds minimal overhead to your network:

  • Per device: ~50–100 KB/day for proxy metadata and policy sync
  • SSL inspection: Adds ~5–10% latency on first connection to a domain (subsequent connections are cached)
  • Dashboard/reporting: Administrative traffic is negligible

For a school of 500 devices, expect approximately 25–50 MB/day of additional KyberGate management traffic.


MDM Compatibility Matrix

MDM Solution iPad macOS Windows Chromebook
Jamf Pro ✅ Full ✅ Full
Mosyle ✅ Full ✅ Full
Kandji ✅ Full ✅ Full
Google Admin ✅ Full
Microsoft Intune ⚠️ Partial ⚠️ Partial ✅ Full
Jamf School ✅ Full ✅ Full

Troubleshooting

Q: Can I use KyberGate on unmanaged/BYOD devices? A: Yes, but with limitations. Users can manually configure the PAC file and install the CA certificate. However, MDM-managed devices provide the best experience with automatic configuration and tamper protection.

Q: Does KyberGate work on mobile hotspots? A: Yes — KyberGate filtering is proxy-based, not network-based. As long as the device has the PAC file configured and CA certificate installed, filtering works on any network.

Q: What happens if the proxy server is unreachable? A: The PAC file includes failover logic. If the primary proxy is down, traffic routes to the next nearest region. If all proxies are unreachable, the PAC file can be configured to either block all traffic (fail-closed) or allow direct connections (fail-open) based on your policy preference.


Related Articles