FixedmarkAWS NAT Gateway vs Static IP Proxy: Cost
An AWS NAT Gateway with an Elastic IP gives VPC compute a static outbound IP, at $0.045/hr per gateway, $0.045/GB processed, and $0.005/hr per public IPv4 in US East. Two gateways for high availability cost about $73/mo before any traffic, and they only serve compute inside that VPC. Fixedmark is a planned proxy with a dedicated pair from $29/mo that works from any platform; it is in early access.
Fixedmark vs AWS NAT Gateway at a glance
Fixedmark values are planned launch features and pricing. AWS NAT Gateway values are taken from published vendor pages and attributed below. Checked October 2026.
| Fixedmark (planned) | AWS NAT Gateway (published) | |
|---|---|---|
| Hourly charge | None | $0.045/hr per gateway, or per AZ in regional mode (about $32.85/mo each) |
| Data charge | Included up to plan bandwidth (200 GB on Pro) | $0.045/GB processed, plus standard data transfer out |
| Public IPv4 | Included in plan | $0.005/hr per public IPv4 (about $3.65/mo) |
| High availability | IP pair included | One zonal gateway per AZ, or one regional gateway billed per AZ. Two AZs about $73/mo before traffic. |
| Where it works | Any platform: Vercel, Railway, Supabase, Lambda, laptops | Only compute inside the VPC |
| Setup | Set FIXEDMARK_PROXY_URL, route calls through it | VPC, subnets, route tables, Elastic IPs, Lambda VPC config |
| Code changes | Proxy agent on allowlisted calls | None. All egress from routed subnets uses the NAT. |
| Regions | Mumbai, Singapore, Frankfurt, New York, Virginia at launch | Every AWS region |
| Logs | Per-connection destination, SNI, bytes, egress IP | VPC Flow Logs, billed separately |
The arithmetic
AWS bills a NAT Gateway by the hour and by the gigabyte. At $0.045/hr in US East, one gateway costs $0.045 x 730 hours = $32.85 per month. Each public IPv4 address costs $0.005/hr, or $3.65 per month. One gateway with one Elastic IP is $36.50 per month.
A zonal NAT Gateway lives in one availability zone. For high availability you run one per AZ, so two AZs cost about $66/mo in gateway hours plus $7.30 for two public IPv4s, about $73/mo before a single byte moves. AWS added a regional availability mode in November 2025 that spans AZs with one gateway, but it is still billed per AZ per hour, so the total is the same.
Traffic adds $0.045/GB processed. Sending 100 GB through the gateways adds $4.50 in processing, plus standard data transfer out charges. Rates vary by region. Try your own numbers in the NAT gateway cost calculator.
It only works inside the VPC
A NAT Gateway translates traffic from subnets in its own VPC. A Lambda function gets the static IP only after you attach it to the VPC's private subnets. Functions on Vercel, Supabase, Railway, or Cloudflare cannot use it. A proxy works from anywhere that can open an outbound TCP connection.
What a NAT Gateway does better
NAT applies to all traffic from the subnet, so every SDK, driver, and protocol uses the static IP without code changes. It runs in every AWS region and stays inside your AWS account and bill. If your compute already sits in private subnets, the gateway may already exist.
When to choose AWS NAT Gateway instead
A NAT Gateway is the right answer when:
- Your compute already runs in private subnets of a VPC, and the NAT Gateway exists for other reasons.
- You need every protocol and SDK to use the static IP with no code changes.
- Policy requires all egress to stay inside your AWS account.
- You need a static IP today. Fixedmark is in early access.
- You send large volumes where per-GB processing is cheaper than a proxy plan's bandwidth tiers.
When Fixedmark fits better
A static IP proxy is simpler when:
- Only a few calls need a static IP, such as a bank API or a MongoDB Atlas allowlist.
- Your code runs outside AWS, or across several platforms that must share one IP pair.
- You want a dedicated pair from $29/mo instead of about $73/mo in fixed NAT charges.
- You do not want to move Lambda functions into a VPC.
Sources
Checked October 2026. Confirm current details on the vendor's site before you decide. Prices and limits change.
Related guides
- ToolNAT gateway cost calculatorEstimate monthly NAT Gateway cost for your AZs and traffic.
- IntegrationAWS LambdaA fixed IP for Lambda without VPC, subnets, and two NAT Gateways.
- ComparisonGoogle Cloud NATWhat a static outbound IP through Cloud NAT costs and involves on Google Cloud, and when a proxy is simpler.
- Use casePostgres and MySQLAllowlist two IPs on RDS, Cloud SQL, or a self-hosted database and connect through SOCKS5 or a local tunnel.
- ComparisonVercel Static IPsVercel's native $100 per project Static IPs compared with a Fixedmark proxy URL shared across projects and platforms.
- Use caseBank and UPI APIsWhitelist one dedicated IP pair with your bank, UPI partner bank, or GSP, then deploy on Vercel or Railway without re-whitelisting.
Frequently asked questions
How much does an AWS NAT Gateway cost per month?
In US East, one gateway costs $0.045/hr, about $32.85/mo, plus $3.65/mo for its public IPv4 and $0.045/GB processed. Two gateways across two availability zones cost about $73/mo before traffic. Rates vary by region.
Is a regional NAT Gateway cheaper?
Not by itself. A regional NAT Gateway is billed per AZ per hour at the same rate, so spanning two AZs costs the same as two zonal gateways. It mainly simplifies routing and setup.
Do I need a NAT Gateway to give AWS Lambda a static IP?
Natively, yes: attach the function to private subnets that route through a NAT Gateway with an Elastic IP. The alternative is to route only the allowlisted calls through a static IP proxy, with no VPC.
Can a NAT Gateway give Vercel or Supabase a static IP?
No. A NAT Gateway only translates traffic from subnets in its own VPC. Compute on other platforms needs a proxy or the platform's own static IP option.
Make it fixed.
Fixedmark is in early access. Join the list to get dedicated static IPs when your region opens.