Network and firewall
The public hosts EasyCode, the desktop app and your harnesses reach, so they work behind a firewall or proxy.
EasyCode itself only makes outbound connections on port 443: HTTPS, and secure WebSockets (wss://) for live
co-editing. Nothing on your machine has to accept connections from outside. Allow the hosts below on your firewall or
proxy.
EasyCode
| Host | What uses it | Why |
|---|---|---|
app.easycode.studio | Browser, desktop app | The web app, sign-in, the API the desktop app and its runner talk to, and the desktop update feed |
downloads.easycode.studio | Desktop app | Installers and update files |
relay.easycode.studio | Browser, desktop app | Live co-editing of documents, library drafts and studio boards, over a secure WebSocket |
*.easycode.run | Browser, desktop app | Studio artifacts and shared pages. Code you didn't write runs here, never on easycode.studio |
easycode.studio | Browser | The public site and the changelog |
docs.easycode.studio | Browser | These docs |
A host on easycode.run looks like a-… or m-… followed by an ID, so allow the whole *.easycode.run wildcard.
Your proxy must let secure WebSockets through to relay.easycode.studio: allow the upgrade from HTTPS and keep the
connection open. If it doesn't, live editors can't connect.
Signing in
You sign in to EasyCode with one of these. Allow the ones your team uses:
| Host | For |
|---|---|
accounts.google.com | Sign in with Google |
login.microsoftonline.com | Sign in with Microsoft |
github.com | Sign in with GitHub |
Email sign-in needs no extra host: the link arrives in your inbox.
GitHub
Your sessions clone, push and open pull requests with your own git and gh, and admins install the EasyCode
GitHub App on GitHub. Allow:
github.comfor git, sign-in and the App's install pagesapi.github.comforghand pull requests
If your git remotes use SSH, git also needs port 22 to github.com.
Your harnesses
Each harness talks to its own vendor on your own login. EasyCode adds no host of its own to that traffic. Allow what your vendor documents for the harnesses your team uses; each harness page links to its documentation.
Installing and updating a harness also needs its installer's host:
claude.ai (the install script)Optional hosts
These make the app better, and it still works without them:
| Host | What it does | If you block it |
|---|---|---|
raw.githubusercontent.com | The runner refreshes model prices for usage costs | Costs use the prices built into the app |
api-eu.mixpanel.com | Product analytics, only if you agreed to them | No analytics are sent |
*.de.sentry.io | Error reports, in Sentry's EU region | Errors aren't reported to EasyCode |
mcp.linear.app, mcp.atlassian.com | The Linear and Atlassian MCP servers, if you connect them | Your harness can't read tickets |
The desktop app's built-in browser opens whatever sites you test, and searches from its address bar with
duckduckgo.com.
On your own machine
The runner listens on 127.0.0.1 only and checks every request's host and origin. It is never reachable from
another machine, so you don't open any inbound port. If a local firewall asks whether EasyCode may accept incoming
connections, you can deny it.
Behind a TLS-inspecting proxy
If your proxy re-signs HTTPS traffic, your harnesses and git need its certificate too. Set it up as each vendor's
documentation describes.
Next
- Security and privacy: what leaves your machine and where data lives.
- Troubleshooting
Something wrong or missing? Suggest a change