Executive Summary
A new connectivity feature has been released, allowing customers to route their project's build-time traffic through their dedicated Static IPs. This enables secure connections to IP-restricted resources, such as external APIs or headless CMSs, during the build process. This opt-in feature is available now for all teams using Static IPs, and its usage will count towards Private Data Transfer billing.
Key Takeaways
* New Capability: Users can now force build-time traffic to originate from their provisioned Static IPs.
* Use Case: Simplifies connecting to IP-whitelisted external data sources (APIs, CMSs, databases) during the build and deployment process.
* Activation: The feature is enabled via a new toggle in Project Settings → Connectivity named "Use static IPs for builds."
* Unified Traffic: When enabled, both build traffic and serverless function traffic will route through the same Static IPs.
* Billing: Data transferred via this feature will be metered as "Private Data Transfer usage."
* Availability: The feature is immediately available to all customers on plans that include the Static IPs add-on.
Strategic Importance
This update enhances platform security and control, allowing enterprise customers to enforce consistent network policies across both their build and runtime environments.