Audiee.ai on a corporate network
Audiee.ai talks to a short list of hosts, all over TLS on port 443. On a managed network, allow the four below; TLS inspection can stay on for all of them except the live transcription stream, which must not be buffered. Speech providers are reached through our gateway, so there is nothing else to allow.
Allow these
| Host | Protocol | What it is for |
|---|---|---|
| ai-gateway.audiee.ai | HTTPS and WebSocket (WSS), TCP 443 | Everything the app needs while you use it: sign-in session, your plan and usage, the live transcription stream (WSS), summaries and the assistant, sharing. The WebSocket carries audio frames and transcript text in real time: allow long-lived connections, and do not buffer or content-scan this host. |
| klxxioveqqpzeuvuvytc.supabase.co | HTTPS, TCP 443 | Sign-in (Supabase Auth): the sign-in page, token refresh, and the encrypted store for the tokens of tools you connect. |
| audiee.ai, releases.audiee.ai | HTTPS, TCP 443 | The sign-in page opens on audiee.ai; app updates are downloaded from releases.audiee.ai. |
| github.com, objects.githubusercontent.com | HTTPS, TCP 443 — once | On the first start the app downloads its Python runtime (about 50 MB, from python-build-standalone on GitHub) into ~/.audiee. Not needed after that. |
Optional, depending on what you use
| Host | Protocol | When |
|---|---|---|
| checkout.stripe.com, billing.stripe.com | In your browser | Only when you buy or manage a plan. |
| accounts.google.com, *.googleapis.com | HTTPS, TCP 443 | Only if you connect Google Calendar or Drive from Settings. |
| api.loops.so | From our servers, not your Mac | Account emails. Nothing to allow on the network. |
TLS inspection (SSL decryption)
Since version 0.1.101 the app trusts the certificates in the Mac's own keychain, so an inspection certificate your IT team has installed is accepted the way Safari accepts it. Two things still matter:
- Do not buffer the transcription stream. The WebSocket to
ai-gateway.audiee.aicarries audio one frame at a time and gets transcript text back the same way. A proxy that holds the response to scan it breaks live transcription — the meeting records, but captions arrive late or the connection drops. Exempt this host from content scanning, or from inspection altogether if your product cannot pass WebSocket frames through unchanged. - Versions before 0.1.101 trust only the public certificate list, so they cannot connect through an inspecting proxy at all. Update.
Proxies
The app itself follows the Mac's proxy settings. Its background service, which carries the transcription stream, connects directly; on a network that only reaches the internet through a proxy, allow direct outbound TCP 443 to ai-gateway.audiee.ai for it. PAC files are not read.
How a blocked network looks
- Sign-in works (it runs in the browser) but a meeting stops within a minute with a notice that Audiee.ai could not reach its transcription service.
- The first start sits on "Setting up the recorder" for a long time: the Python runtime download from GitHub is blocked.
- Audiee.ai works at home or on a phone hotspot and not in the office.
Send this page to your IT team, or send us theirs: hello@audiee.ai. The full list of what leaves your Mac, and why, is on the trust page.