Outbound access
The hosts a self-hosted Skilder calls, and from which service.
Pilot release. Self-hosting Skilder is a pilot.
A default install reaches the internet in two places: your host clones the release files and pulls the images. Every other call happens when a member uses a feature or you configure one, so allow a host only if you use the feature behind it. The services talk to each other on the Compose network and need nothing from outside.
On every install
| Host | Made by | Trigger |
|---|---|---|
github.com, on port 443 with a token or port 22 with a deploy key | git on your host | Cloning the release files or fetching a later release (Get the compose files). |
ghcr.io and pkg-containers.githubusercontent.com; Docker Hub: registry-1.docker.io, auth.docker.io and production.cloudflare.docker.com | Docker on your host | docker compose up or pull. The four Skilder images come from ghcr.io/skilder-ai, or from the mirror in SKILDER_REGISTRY. nginx, NATS, Dgraph and Garage come from Docker Hub. |
When members use a feature
| Host | Made by | Trigger |
|---|---|---|
api.github.com, raw.githubusercontent.com | backend | A member imports a skill from GitHub or installs one from Community in the new skill dialog. Anonymous unless you set PRIVATE_GITHUB_IMPORT_TOKEN. |
skills.sh | backend | A member opens Community in the new skill dialog, or asks for skill suggestions for a role. |
registry.npmjs.org | main-runtime | A member installs or starts an MCP server published on npm. The runtime runs it with npx and downloads it again after the container is recreated. |
pypi.org, files.pythonhosted.org; releases.astral.sh for a server that needs another Python | main-runtime | A member installs or starts an MCP server published on PyPI (run with uvx), or runs a Python script that declares dependencies. When a server's package does not support the runtime's Python, uvx downloads an interpreter that does. Scripts only use the runtime's Python. |
| The URL of the MCP server | main-runtime, and backend for OAuth | A member adds a remote MCP server, from the catalog or by its address. Skilder calls that address. |
| The MCP server's authorization server, as the MCP server names it | backend, and main-runtime for its metadata | A member signs in to a remote MCP server with OAuth. The backend discovers the authorization server, registers Skilder as a client and exchanges and refreshes tokens there, and refuses addresses on private networks. The runtime reads the same metadata when the MCP server refuses a request without a valid token. |
The client_id URL of an MCP client, and the jwks_uri its document names | backend | An MCP client that identifies itself by an https URL starts an OAuth sign-in. The backend fetches the document at that URL. A client that signs its token requests also has its public keys fetched from the document's jwks_uri. |
Google: *.googleapis.com. Microsoft: login.microsoftonline.com, graph.microsoft.com, and your SharePoint or OneDrive host for file downloads. Zoho CRM: accounts.zoho.com, www.zohoapis.com, or your data center's domain. Infomaniak: api.infomaniak.com | main-runtime, and backend for the Google, Microsoft and Zoho sign-in and token refresh | A workspace installs one of these bundled MCP servers from the catalog and a member uses it. |
registry.modelcontextprotocol.io, and any page URL a member pastes | backend | A member generates an MCP server configuration with AI. It needs an AI provider. |
An MCP server the runtime starts with npx or uvx then reaches whatever its own upstream is, from main-runtime. Those hosts are the server's, not Skilder's: check its documentation. A skill script runs in main-runtime with the same network access, and reaches whatever hosts its own code calls.
When an authorization server supports client metadata documents, it also fetches <PUBLIC_URL>/api/oauth/client-metadata.json, so your reverse proxy keeps that path public (What your proxy must do).
When you configure it
| Host | Made by | Trigger |
|---|---|---|
| The SMTP host you configure | backend | EMAIL_PROVIDER=smtp. A connection check at boot and every 5 minutes, and each email. |
| Google, GitHub or Microsoft sign-in hosts | backend, and members' browsers for the redirect | The matching *_SIGNIN_CLIENT_ID and *_SIGNIN_CLIENT_SECRET. The backend exchanges the sign-in code at oauth2.googleapis.com, github.com or login.microsoftonline.com, and reads a GitHub account's profile and email addresses from api.github.com. |
Your OIDC identity provider, at the issuer you set, or login.microsoftonline.com for Microsoft Entra ID | backend, and members' browsers for the redirect | Single sign-on, on the enterprise image. The backend reads the provider's discovery document and keys, and exchanges the sign-in code. For Entra it calls no other Microsoft host. |
api.openai.com, api.anthropic.com, generativelanguage.googleapis.com, api.infomaniak.com, inference.at-vie-2.exoscale-cloud.com, bedrock.<region>.amazonaws.com and bedrock-runtime.<region>.amazonaws.com, or the URL you enter | backend; remote-mcp and main-runtime for delegation | A workspace admin adds an AI provider. The app's AI features, Studio among them, then call it from the backend. The sub-agents that an agent or a skill script delegates to call it from remote-mcp or main-runtime. The platform-managed Skilder provider makes no call: it needs credentials Skilder holds. |
eu.i.posthog.com, eu-assets.i.posthog.com | frontend | POSTHOG_KEY. Members' browsers send their analytics to your frontend, which forwards them. Unset, the browser sends nothing. |
Through an outbound proxy
With an outbound proxy set, each host above is reached as follows:
- On every install:
gitand Docker on your host do not read.env. Give them their own proxy settings, or allow these hosts directly. - When members use a feature: the calls of Skilder's services go through the proxy. That includes
npx,uvxand the Python scripts inmain-runtime. The backend's OAuth calls also need local DNS (OAuth and DNS). An MCP server's calls to its own upstream go through the proxy when its HTTP client reads the proxy variables. A Node server'sfetchandhttp(s)do. - When you configure it: the AI providers, the sign-in providers and the SSO identity provider go through the proxy. The SMTP host and PostHog do not: allow them directly. An identity provider on your own network is usually listed in
NO_PROXYand reached directly (An identity provider on your network). - Members' browsers: they use their own network, not Skilder's proxy.
A host listed in NO_PROXY is reached directly, without the proxy.
Members' browsers
Members' browsers load every script, style and font from your PUBLIC_URL, and call no other host, apart from the redirects to a sign-in provider or an authorization server. The app's content security policy allows one exception: images from any https host.

