Network pricing
The VPC or VNet itself is free on every cloud. The fixed cost is NAT, which the customer pays on their own cloud bill.
Alien lists the Network as a free resource on Pricing.
Prices on this page are AWS list prices as of October 2026 in us-east-1. Official pricing: AWS VPC, Google Cloud VPC and Cloud NAT, Azure Virtual Network and Azure NAT Gateway.
Cost components
| Component | Applies when | Notes |
|---|---|---|
| NAT Gateway or Cloud NAT | create mode, and use-default on Azure | Usually the largest fixed network cost for a small deployment. Billed per hour and per GB processed. |
| Public IP addresses | NAT gateways and public load balancers | Varies by cloud and region. |
| Load balancers | Containers with public ports | Billed with the Container, but they sit in the Network. |
| Data processing | NAT, load balancing, cross-zone traffic | Per GB, per cloud. |
| Data transfer | Internet egress and cross-region traffic | Per GB, by destination. |
By mode
| Mode | Network resources billed | Notes |
|---|---|---|
create | Yes | Alien creates the VPC or VNet, subnets, NAT, routing, and firewall rules. |
use-default | AWS and GCP: no. Azure: yes. | AWS and GCP use the cloud's default network and no NAT. Azure has no default VNet, so Alien creates a VNet and NAT Gateway. |
byo-vpc-aws, byo-vpc-gcp, byo-vnet-azure | No | Costs stay with the customer's existing network. |
Example: one AWS deployment in create mode
A deployment created from the setup template has one NAT Gateway.
| Item | Price | Monthly |
|---|---|---|
| NAT Gateway, 730 hours | $0.045 per hour | $32.85 |
| NAT data processing, 100 GB | $0.045 per GB | $4.50 |
| Public IPv4 address for the NAT, 730 hours | $0.005 per hour | $3.65 |
| Total | $41.00 |
Internet egress is billed on top at standard data transfer rates.
For many small, low-traffic deployments, the hourly NAT charge dominates. use-default avoids it in development, and BYO modes reuse NAT the customer already pays for.
Cost control
- Use BYO modes when the customer already has central NAT, inspection, or egress controls.
- Use
createwhen the deployment should own its network and its cleanup. - Review NAT and egress costs before deploying many small environments.
- Public containers add load balancer and data processing charges on top of the network baseline.