Networking requirements Preview
Fusion requires outbound HTTPS access to several endpoints depending on your usage. This page describes each requirement and provides guidance for enterprise environments that restrict outbound traffic.
The following table summarizes all endpoints. See each section below for details.
| Loading table... |
Adapter drivers
The Fusion binary does not bundle database drivers. Instead, Fusion automatically downloads the correct ADBC driver for your data platform the first time you run a dbt command (such as dbt run, dbt debug, or dbt compile). Fusion detects which driver you need based on your profiles.yml configuration and downloads it from the dbt Labs CDN. Fusion distributes all checksums with the binary itself to guarantee authenticity of the downloaded drivers.
Adapter driver downloads require outbound HTTPS access to the dbt CDN:
| Loading table... |
Fusion handles driver download automatically on first use. The dbt system install-drivers command downloads all supported drivers (Snowflake, BigQuery, Postgres, Databricks, Redshift, DuckDB, and Salesforce) at once. This is useful if you work across multiple data platforms and want to pre-cache every driver before going offline or switching projects.
Enterprise proxy considerations
Adapter drivers are native shared libraries (.dylib on macOS, .so on Linux, .dll on Windows). Some enterprise proxy filters and security tools classify these file types as executables and may block the download — even if you allowlist public.cdn.getdbt.com at the domain level.
If your organization's proxy blocks adapter driver downloads, work with your IT team to ensure both:
- You allowlist the domain
public.cdn.getdbt.com. - Content inspection rules permit downloading native library file types (
.dylib,.so,.dll) from that domain.
If you cannot change your proxy configuration, see Restricted network installation.
Restricted network installation
If your environment cannot access public.cdn.getdbt.com for adapter driver downloads, you can pre-build a bundle of the Fusion binary and the adapter drivers into a single .tar.gz or Docker image and host it on an internally approved fileshare.
For supported adapters, refer to Fusion requirements.
Telemetry
Fusion sends anonymous usage telemetry to help improve the product. If the telemetry endpoint is unreachable (for example, blocked by a firewall or proxy), Fusion logs errors on each invocation.
| Loading table... |
To suppress these errors without allowlisting the URL, disable anonymous telemetry by setting the environment variable:
export DBT_SEND_ANONYMOUS_USAGE_STATS=false
You can also add this to your .env file in your project root:
DBT_SEND_ANONYMOUS_USAGE_STATS=false
For more details on .env file usage, refer to Environment variables.
Manifest downloads (dbt platform only) enterprise
For dbt platform customers using Fusion locally, Fusion downloads production manifests from dbt platform to enable features like deferral and cross-project references. The cloud storage provider hosting your dbt platform cell serves these manifests via pre-signed URLs.
The specific hostnames depend on your dbt platform deployment region and the underlying cloud provider. To ensure Fusion can download manifests, allowlist the appropriate storage domain for your region:
| Loading table... |
Because pre-signed URLs contain region and account-specific hostnames that may change over time, we recommend allowlisting the base storage domain for your cloud provider rather than individual URLs:
- AWS —
s3.*.amazonaws.com - Azure —
*.blob.core.windows.net - GCP —
storage.googleapis.com
Was this page helpful?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
