Skip to main content

CrewAI Factory — Network Allowlist

Purpose: This document lists every external domain that a CrewAI Factory installation may contact. Use it to configure firewall rules, proxy allowlists, or egress network policies. Last updated: 2026-04-28

How to Read This Document


1 · Critical Path — Blocks Installation

These domains are contacted during helm install and initial platform bootstrap. Blocking any of them will prevent installation.

2 · Platform Runtime Services

These are first-party CrewAI services the platform communicates with at runtime.

3 · LLM Providers

Allow whichever providers your teams will use. The platform does not hardcode a single provider — customers choose which LLM APIs to connect.
Note: The built-in LLM (BUILT_IN_LLM_PROVIDER) defaults to OpenAI (gpt-4.1-mini). At minimum, allow the provider configured for the built-in LLM.

4 · Search, Scraping & Tool Providers

These are used by CrewAI tool integrations. Allow based on which tools your teams enable.

5 · Vector Databases

Only required if your crews connect to managed vector database services. Allow based on which provider you use.

6 · Authentication & SSO

Allow the domain(s) for your chosen SSO provider. These are customer-specific.

7 · OAuth Integrations (Built-In Connectors)

If you enable built-in OAuth connectors for third-party services, allow the corresponding domains below. The OAuth proxy is served via an ingress path on your application host (see OAuth chart values) — no dedicated subdomain is required.

8 · Cloud Provider Services

Allow based on your deployment cloud. These are for object storage, secrets management, and identity federation from within the cluster.

AWS

Azure

GCP


Quick-Copy Allowlist

For convenience, here is a consolidated flat list of all mandatory + commonly-needed domains for a typical Factory deployment:

Revision History