> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/welcome/elastic-compute/networking/bandwidth/08-comparison.md).

# Billing Method Comparison

One page comparing the three ZEC public-network billing methods. Use it to pick the right one quickly; follow the links into the per-method pages for the reasoning.

## Comparison table

| Billing Method        | Location / Scope              | Services Covered  | Billing Items                                                                  |
| --------------------- | ----------------------------- | ----------------- | ------------------------------------------------------------------------------ |
| **Flat Rate**         | — (per instance)              | One instance      | Fixed bandwidth size (Mbps)                                                    |
| **Data Transfer**     | — (per instance)              | One instance      | Data transfer package (GB) + overages (GB)                                     |
| **Bandwidth Cluster** | Opted-in ZEC EIPs in one city | Ideal at 50+ EIPs | Bandwidth commitment (Mbps, if you have one) + burstable 95th bandwidth (Mbps) |

The three rows are arranged from narrowest scope (one instance) to widest (all EIPs in a Bandwidth Cluster). Cost generally drops as scope widens, because aggregation discounts more peaks.

***

## Differences that actually matter when picking

**What's being metered.** Data Transfer is the only one that counts gigabytes. The other two count Mbps, differing in *which* Mbps — a fixed cap for Flat Rate, the monthly 95th of combined Mbps for Bandwidth Cluster.

**How wide the meter runs.** Flat Rate and Data Transfer are *per-EIP* — one instance, one meter. Bandwidth Cluster pools the opted-in ZEC EIPs in a city into one 95th calculation. This is the single biggest driver of total cost at fleet scale.

**Where the commitment lives.** Flat Rate is straightforward — the cap you select is what you pay for. Data Transfer has no commitment, just a prepaid package. Bandwidth Cluster has an explicit commitment floor plus a burst-on-top.

**What the bandwidth cap does.** For Data Transfer and Bandwidth Cluster, the cap is a separate upper bound — defaults to 10 Gbps on EIP creation, can be lowered to protect a budget or raised for headroom. For Flat Rate, the cap *is* the billing — you pay for the bandwidth you select. See [Bandwidth Cap](/welcome/elastic-compute/networking/bandwidth/07-bandwidth-cap.md).

***

## Quick-pick cheat sheet

| Situation                                                       | Pick                                                                                     |
| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| One EIP, bursty traffic, predictable monthly volume             | [Data Transfer](/welcome/elastic-compute/networking/bandwidth/03-data-transfer.md)       |
| One EIP, steady and high throughput                             | [Flat Rate](/welcome/elastic-compute/networking/bandwidth/04-flat-rate.md)               |
| 50+ EIPs with peaks uncorrelated, want one aggregated 95th bill | [Bandwidth Cluster](/welcome/elastic-compute/networking/bandwidth/05-aggregated-95th.md) |
| Need a hard ceiling regardless of meter                         | Set a [Bandwidth Cap](/welcome/elastic-compute/networking/bandwidth/07-bandwidth-cap.md) |