Static IPs
Static IPs are available on Enterprise and Pro plans.
With Static IPs (shared pool), you can access backend services that require IP allowlisting through static egress IPs. It's designed for Pro and Enterprise teams who need static IP functionality without the advanced networking or security features of Secure Compute.
- Connect to databases such as Amazon RDS, Google Cloud SQL, Azure SQL, and MongoDB Atlas
- Connect to APIs such as Auth0, PayPal, Stripe, internal corporate APIs
- Connect to systems such as on-premises databases and services behind firewalls
- Support compliance and business requirements
| Feature | Static IPs (Pro & Enterprise) | Secure Compute (Enterprise only) |
|---|---|---|
| IP type | Static in shared Virtual Private Cloud (VPC) | Static in dedicated VPC |
| Network isolation | Shared VPC for a small group of customers with subnet-level isolation | Dedicated VPC and subnet per customer |
| Use cases | IP allowlisting, database access | IP allowlisting, VPC Peering, full isolation |
| Pricing | $100/month per project, plus Private Data Transfer at $0.15/GB | Custom pricing |
Read our getting started guide to learn how to set up Static IPs.
When you enable Static IPs, you get:
- Shared infrastructure: Each VPC serves a small group of customers
- Static egress: All outbound traffic routes through shared static IP pairs
- Logical isolation: Subnet-level isolation maintains security between customers on the same VPC
- NAT gateway: Traffic exits through a managed NAT gateway for consistent IPs
- Build traffic: Traffic from both deployed functions and builds will route through the static IPs
Static IPs (region-specific) don't apply to middleware (which are deployed at the edge).
- Go to your Team and click the Usage tab
- Scroll down to the Content, Caching & Optimization section. Static IPs data transfer is metered by Private Data Transfer
- Click Private Data Transfer for more detail about direction, regions, and projects
When you configure static IPs in a project, they apply to all the environments set up in this project.
- Choose regions close to your backend services to reduce latency
- Each configured region has its own static IP pair
- Static IP addresses are shared across a small group of customers in the same region
- Project-level configuration: You cannot isolate static IPs to specific deployment environments
Static IPs are priced at $100/month per project for Pro plus Private Data Transfer priced regionally based on regional pricing documentation.
Was this helpful?