Guide for admins
This guide is for the owners and admins of an organization in Patalyze, and for the IT team that works with them. It covers the addresses your network has to allow and how you control the apps your members build.
Network requirements#
Many companies route their traffic through a proxy or a firewall that only lets known addresses through. If yours does, Patalyze needs the addresses below to work in the browser and in the desktop app. The simplest way to get there is to hand this section to your IT team.
Addresses to allow#
All of these addresses are reached on port 443, and every connection to them is encrypted.
| Address | Used for |
|---|---|
patalyze.com | The web app, the website and these docs. |
ws.patalyze.com | Loading your research and keeping it up to date, over a WebSocket. |
api.patalyze.com | Sign-in in the desktop app, the models of agents that run in your browser or in the desktop app, and the Patalyze MCP server. |
patents.patalyze.com, data.patalyze.com | Full texts, PDFs and figures of patents, the titles of their classifications, the Data API and the Patents (by Patalyze) MCP server. |
assets.patalyze.com, images.patalyze.com, logos.patalyze.com | Images, map data, profile pictures and organization logos. |
*.patalyze.app | Apps built in Patalyze, each at a subdomain of its own. |
releases.patalyze.com | Updates of the desktop app. |
storage.googleapis.com | Files you upload or download, e.g. attachments and images. |
*.r2.cloudflarestorage.com | The patents, scientific papers and technical standards in your research. |
*.browserbase.com, *.cloudfront.net | The live view and recordings of the browsers that agents use. |
js.stripe.com, *.stripe.com, *.stripe.network | Payments in the web app. |
If your members sign in with Google or Apple, their browser also reaches accounts.google.com or appleid.apple.com. And if they add their own Anthropic, OpenAI or Gemini API key, agents that run in the browser or in the desktop app reach that provider directly, at api.anthropic.com, api.openai.com or generativelanguage.googleapis.com. A Claude or ChatGPT subscription in the desktop app runs through Claude Code or Codex, which need their own addresses.
App addresses#
Every app built in Patalyze runs at a subdomain of its own, e.g. https://k3j4h5g6f7.patalyze.app, and every new app gets a new one. So allow the wildcard *.patalyze.app instead of single addresses. Also make sure your proxy doesn't put a warning page in front of an app or rewrite its address, since either one breaks the app.
WebSockets#
Patalyze loads your research and keeps it up to date over a WebSocket to ws.patalyze.com. If your proxy inspects encrypted traffic, make sure it doesn't break WebSocket connections, because Patalyze can't load any research without one.
Desktop updates#
The desktop app downloads its updates from releases.patalyze.com. Allow it wherever your team uses the desktop app, so it stays up to date.
Apps#
As an owner or admin, you find every app of your organization under Settings > Apps, and you can delete any of them there.
To turn apps off for the whole organization, simply set Apps to Disable under Settings > Policies. Agents then can't build apps, and every existing app stops running until you set Apps back to Allow. You can read more about apps on the Apps page.
Related topics