Skip to content

Network

Configure network settings for proxied or restricted environments.

HTTP Proxy

Set the HTTPS_PROXY environment variable:

export HTTPS_PROXY=http://proxy.example.com:8080
altimate

Also supports HTTP_PROXY and NO_PROXY:

export HTTPS_PROXY=http://proxy.example.com:8080
export NO_PROXY=localhost,127.0.0.1,.internal.com

Custom CA Certificates

For environments with custom certificate authorities:

export NODE_EXTRA_CA_CERTS=/path/to/ca-bundle.crt
altimate

This is common in corporate environments with TLS inspection.

Firewall Requirements

altimate needs outbound HTTPS access to:

Destination Purpose
Your LLM provider API Model inference (Anthropic, OpenAI, etc.)
Official Altimate Base gateway (embedded in release), or the host set by ALTIMATE_BASE_GATEWAY_URL Altimate Base registration (automatic at startup on any install not yet registered, unless ALTIMATE_BASE_AUTO_REGISTER=0, after logging out of Base, or during the 1–24 h retry backoff after a network error, rate limit or gateway server error) and inference
registry.npmjs.org Package updates
models.dev Model catalog (can be disabled)
Your warehouse endpoints Database connections
eastus-8.in.applicationinsights.azure.com Telemetry (Azure Application Insights)

Disable Model Fetching

If models.dev is unreachable:

export ALTIMATE_CLI_DISABLE_MODELS_FETCH=true

Or provide a local models file:

export ALTIMATE_CLI_MODELS_PATH=/path/to/models.json