Portfolio 05 · network bill graph

AI data transfer and egress cost calculator

Aggregate each directed flow monthly, apply its native free allowance and piecewise tiers, and keep source, destination, and fixed connectivity charges visible.

Decision this answers: Which architecture and direction avoids a hidden second bill while preserving provider-native GB or GiB units?

Scenario

Decision summary

Source egress

$1062.20exact-derived

Piecewise source-side charge after free allowance.

[2]

Destination processing

$120.00model estimate

Separate second-side scenario meter.

[4]

Fixed connectivity

$120.00negotiated

Monthly floor independent of bytes moved.

[3]

Two-sided route total

$1302.20exact-derived

Source, destination, and fixed terms reconciled.

[2][4][3]

Direct-labeled result profile

Source egress Destination processing Fixed connectivity Two-sided route total

The tables below are the accessible source of truth; bar lengths never carry identity alone.

Direction-specific route ledger

Direction-specific route ledger
Candidate	Volume	Source charge	Scope	Reason	Evidence
Google Cloud to public internet	12000 GB	$1422.28	Monthly aggregate	Source egress shown; destination/fixed terms separate	exact-derived[1]
AWS to public internet	12000 GB	$1062.20	Monthly aggregate	Source egress shown; destination/fixed terms separate	exact-derived[2]
Azure to public internet	12000 GB	$1028.26	Monthly aggregate	Source egress shown; destination/fixed terms separate	exact-derived[3]
Databricks serverless private connectivity	12000 GB	Unknown · not ranked	Monthly aggregate	Source egress shown; destination/fixed terms separate	unknown[4]

Official surface versus this site

Google Cloud VPC network pricing

Use the official surface to confirm native prices, counting rules, limits, and product eligibility.

This offline workbench

Official pages price one provider and direction at a time. This workbench places both sides of a multi-cloud AI flow in one ledger and leaves unsupported routes visibly unknown.

Sources and methodology

Every result-affecting reference is visible here without JavaScript and is retained in the JSON export.

[1] Google Cloud VPC network pricing

Authority: Google Cloud
Native identifier: internet data transfer
Region: us
Unit: USD/GB
Evidence: published list
Price kind: list
As of: 2026-08-01
Effective from: 2026-08-01
Retrieved: 2026-08-01
Freshness: fresh
Normalization: Illustrative tier rows preserve the documented direction and monthly boundaries; verify the selected geography.

Open the authoritative source

[2] AWS EC2 data transfer pricing

Authority: Amazon Web Services
Native identifier: EC2 Data Transfer Out
Region: US
Unit: USD/GB
Evidence: published list
Price kind: list
As of: 2026-08-01
Effective from: 2026-08-01
Retrieved: 2026-08-01
Freshness: fresh
Normalization: The opening route applies its free allowance once and then exact ascending tier boundaries.

Open the authoritative source

[3] Azure bandwidth pricing

Authority: Microsoft
Native identifier: inter-region and internet egress
Region: Zone 1
Unit: USD/GB
Evidence: published list
Price kind: list
As of: 2026-08-01
Effective from: 2026-08-01
Retrieved: 2026-08-01
Freshness: fresh
Normalization: The route keeps source direction and tier region explicit; fixed connectivity is an editable override.

Open the authoritative source

[4] Databricks networking cost management

Authority: Databricks
Native identifier: serverless network connectivity
Unit: cloud-dependent meter
Evidence: unknown
As of: 2026-08-01
Retrieved: 2026-08-01
Freshness: reference
Normalization: Unsupported or cloud-pass-through meters remain unknown rather than zero.

Open the authoritative source

Limits and non-claims

The cheapest priced opening route is $1028.26; that is a bill comparison, not an availability or architecture recommendation.
Rates vary by geography, product path, contract, and effective date; refresh the local snapshot before use.
Taxes, exchange-rate effects, and traffic not represented as a directed edge are excluded.