Per-TB pricing usually fits low, irregular, or project-based transfer volume; a monthly subscription fits steadier volume when the included allowance and contract match actual use. The underlying choice is who absorbs variance. Metering sends usage risk to the buyer. A fixed subscription sends more of it to the vendor. Hybrid plans divide it.
There is no universally cheaper structure. Compare each offer using the same bytes, recipients, retention, regional terms, and high-usage scenario—and read the meter definition before comparing headline prices.
What each structure buys
Pure per-TB or per-GB pricing tracks actual volume. A buyer with no transfer in a quiet month may owe little usage cost, while a deadline spike creates a larger invoice. It is easy to compare only when the unit and counted events are explicit.
Monthly subscription trades some utilization efficiency for a known recurring amount. It works well when volume is steady and the included allowance is regularly used. A light buyer can pay for unused capacity; a very heavy buyer may encounter fair-use, overage, or negotiation terms.
Included allowance plus overage sets a budget baseline and prices exceptional usage separately. It reduces the vendor's tail risk while giving the buyer more predictability than pure metering.
Prepaid credits let a buyer commit to a volume block and draw it down across projects. They can smooth invoices, but the buyer should check expiry, refunds, rollover, currency, and whether a credit represents GB, GiB, upload, or download.
Base fee plus usage separates ongoing service access from variable transfer. This can reflect operational features independently of bytes, but it creates two billing concepts to explain.
Negotiated volume fits large, steady workloads that justify region, commitment, term, support, and rate discussions. It gives up retail simplicity for a contract aligned to the actual pattern.
Units and events come first
“One TB” can mean 1,000,000,000,000 bytes, while one TiB is 1,099,511,627,776 bytes—about 9.95% more. Some vendors use decimal GB for network transfer while cloud storage capacity may be billed in binary units. A rate comparison can be wrong before price enters the spreadsheet.
Ask what the service meters:
- uploaded bytes, downloaded bytes, or both;
- bytes accepted before compression or bytes sent on the wire;
- each recipient and redownload separately;
- retries or only successful delivery;
- storage beyond a retention window;
- decimal GB/TB or binary GiB/TiB;
- monthly usage, prepaid burndown, or committed volume; and
- tax, currency conversion, support, or minimum term.
The contract and usage record should answer these questions. A headline “per TB” number cannot.
Use dated market examples carefully
MASV's public page, accessed August 10, 2026, listed a pay-as-you-go offer with 15 GB per month included and then $0.25 USD/GB when data exits the platform. Each upload included five days of storage; listed extended storage was $0.07 USD/GB-month. MASV also described subscription, pre-purchase, and enterprise alternatives.
Those are vendor list terms at one date, not TeraAirlift pricing or evidence of MASV's margin. Account, package, subscription, pre-purchase, enterprise, currency, tax, and negotiated terms can change the effective price.
Underlying cloud cost is also tiered. On Azure's USD list page accessed August 10, 2026, premium-network internet egress from North America/Europe was listed at $0.087/GB for the first paid 10 TB band after 100 GB free, then $0.083/GB for the next 40 TB, $0.07 for the next 100 TB, and $0.05 for the next 350 TB. Region, routing preference, destination, service, tax, and agreement matter.
This helps explain why a vendor may offer volume bands without proving what that vendor pays. Public cloud list price is not an audited cost base.
Compare with scenarios, not one crossover
Consider four illustrative offers:
- $0.20 per decimal GB, pure metering;
- $999 per month, flat;
- $999 including 5 TB, then $0.15/GB overage; and
- a 20 TB prepaid block at $0.17/GB, costing $3,400.
These invented numbers demonstrate plan shape only. They are not market averages, quotes, or TeraAirlift prices.
| Monthly delivered volume | Metered | Flat | Allowance + overage | Prepaid value consumed | |---:|---:|---:|---:|---:| | 1 TB | $200 | $999 | $999 | $170 | | 5 TB | $1,000 | $999 | $999 | $850 | | 10 TB | $2,000 | $999 | $1,749 | $1,700 | | 25 TB | $5,000 | $999 | $3,999 | block exhausted |
The table does not declare a winner. Pure metering is efficient at low volume and exposes spikes. Flat pricing is inefficient at low use and attractive at high use—if the agreement truly covers it. Allowance plus overage sits between those curves. Prepayment trades cash and commitment for a lower modeled rate.
Run at least three scenarios: a quiet month, the expected month, and a plausible deadline spike. Add recipients, because one package downloaded five times may meter five times the bytes of one download. Then model a quarter or year; a single crossover month can hide unused subscriptions or exhausted credits.
A buyer decision checklist
Choose per-TB when volume is sparse or highly project-based, you can tolerate variable invoices, and the meter is transparent. Choose a subscription when delivered volume is stable, procurement needs a fixed commitment, and the allowance is neither mostly wasted nor routinely exceeded.
Prefer allowance plus overage when you need a predictable baseline with burst capacity. Consider prepaid credits when project starts are known but monthly timing is uneven. Seek negotiated volume when usage is both large and forecastable enough to support a commitment.
Before signing, ask:
- What were delivered bytes for the last six to twelve months?
- How far does each month vary from the median?
- How many recipients download each package?
- Can budget owners approve overages quickly?
- Do alerts arrive before a threshold?
- What happens to unused allowances or credits?
- Are retention and retrieval separate?
- Can usage records be reconciled to individual deliveries?
Use the transfer-time calculator to size real jobs and the shipping-versus-transfer calculator for large one-off alternatives.
Where TeraAirlift fits
TeraAirlift's final billing model is not announced. Current approved wording says plans start with a 10 TB included allotment, packages can be any size, and volume above the allotment is overage. It does not define currency price, metering unit, included-download treatment, cadence, or overage rate. Those choices remain under evaluation and details are confirmed on a demo.
Sources
- MASV pricing — published usage, temporary-storage, and plan options; accessed August 10, 2026.
- Azure Bandwidth pricing — dated USD tiered egress context and qualifications; accessed August 10, 2026.
- Azure Blob Storage pricing — binary capacity units and storage-side meters; accessed August 10, 2026.
- NIST — Prefixes for binary multiples — GB/GiB and TB/TiB definitions.
- Stripe usage-based billing — metering, usage records, thresholds, and credits; accessed August 10, 2026.
