Networking
RunMat Desktop and the runmat CLI make outbound HTTPS connections only, on port 443 with TLS. They open no listening ports on the user's computer.
What Desktop and the CLI connect to
| Destination | Used for |
|---|---|
| Your RunMat server: RunMat Cloud, or your organization's own server | Sign-in, projects, live collaboration, the agent and remote runs |
| File storage the server points them to | Uploading and downloading large files through short-lived signed links |
| RunMat's update host | Desktop updates |
Sign-in opens the system browser, which must reach the server and your organization's identity provider.
Code runs on the user's computer unless they send it to a cluster. Local runs need no network connection. Remote runs are encrypted on the user's computer before they leave it.
Firewall rules
On RunMat Cloud, allow outbound HTTPS from workstations to RunMat's domains. With a self-hosted server, allow outbound HTTPS to your server and its file storage; nothing needs to leave your network. Enterprise customers receive the full list of hosts and settings with the deployment guide.