Usage metrics

Every figure Gigadrive Network meters, what it measures, the unit it is stored in, and what makes it go up.

Gigadrive Network meters your organization against the following metrics, and those same metrics produce your invoice. Most of them carry an included allowance from your plan, and only the part above that allowance is charged.

Billable metrics

Metric	Key	What it measures	Stored unit	Shown as	What drives it up
Edge requests	`edge_requests`	Requests served at the edge, including cached and dynamic responses.	count	count	All traffic, including responses served straight from the CDN cache.
Function invocations	`function_invocations`	Requests that invoked one of your Functions.	count	count	Traffic that misses the cache or was never cacheable.
Data transfer	`egress_bytes_cdn`	Response bytes sent by applications, excluding File Storage delivery.	bytes	GB	Response size multiplied by traffic. Caching at the visitor and compression cut it.
Image optimizations	`image_optimizations`	Images served through the built-in image optimization pipeline.	count	count	Every optimized image served, from the CDN cache or from origin. Errors do not count.
Active CPU	`function_active_cpu_ms`	CPU consumed while your Function code executes.	ms of CPU	CPU·h	CPU-bound work: rendering, parsing, crypto. Waiting on a database or an API is free.
Provisioned memory	`function_in_flight_memory_mb_ms`	Memory reserved while your Functions stay warm, including idle time.	MiB·ms	GiB·h	Configured memory times residency. Always-warm and long-lived connections hold it up.
Runtime cache reads	`runtime_cache_reads`	Cache entry reads by Next.js runtime caching, including misses.	count	count	Cached data fetches in a Next.js application. A miss still counts as a read.
Runtime cache writes	`runtime_cache_writes`	Cache entry writes and tag revalidations by Next.js runtime caching.	count	count	Revalidation. A tag revalidation is billed as a write.
Storage data transfer	`storage_egress_bytes`	Bytes delivered from Gigadrive File Storage.	bytes	GB	Downloads of stored objects, including public bucket URLs.
Storage at rest	`storage_bytes_hours`	Logical File Storage bytes retained over time.	byte-hours	GB·mo	How much you store and for how long. Deleting an object stops it accruing.
Build compute	`build_sandbox_seconds`	Sandbox time used to build and package deployments.	seconds	min/hrs	Build duration times deployment count. A warm build cache shortens it.
Build cache overage	`build_cache_overage_bytes_hours`	Retained build-cache capacity above the included plan allowance.	byte-hours	GiB·mo	Only accrues once an admin has enabled paid build-cache overage.
AI Gateway	`ai_gateway_cost_eur_micros`	Model usage routed through the Gigadrive AI Gateway.	EUR micros	currency	Tokens and the model you chose. Billed at cost, one euro per euro of model usage.

Active CPU is measured while your code is on a CPU, so an idle Function accrues none of it. That is the figure to look at when a page is slow because of work you are doing. Provisioned memory is the opposite: it accrues on the clock while the Function is resident, whether or not it is busy. Memory and CPU covers how the setting maps to both.

Image optimizations count serves, not distinct transforms, so a popular image that is optimized once and then served from the CDN a thousand times counts a thousand times. The bytes those serves send are already counted under Data transfer. See Image optimization.

Units

Each metric is stored in a base unit and converted only for display. The base unit is what invoices and allowances are expressed in, and it is what the CSV export writes, so an export reconciles against an invoice without inverting any conversion.

Three conversions are worth knowing because they change the magnitude of the number:

One CPU-hour is 3,600,000 ms of active CPU.
One GiB-hour of provisioned memory is 1,024 MiB held for 3,600,000 ms.
One unit of storage at rest, shown as GB·mo, is one GiB held for 730 hours.

Metered but never billed

Deletes from File Storage are free, and so is inbound transfer: only what leaves is priced. Build cache hit and miss counters, and the bytes restored and written by the cache, are recorded to show how well the cache is working and are never charged. Total retained build-cache storage appears on the usage page for the same reason. The only billable build-cache figure is build_cache_overage_bytes_hours, and it is produced only after someone turns paid overage on.

How usage is aggregated

Usage is aggregated hourly, so a figure can take up to an hour to appear.

An hour's figure then keeps moving for a few hours after it, because CDN delivery logs arrive with a lag of an hour or two. Thirty-six hours after the hour it covers, the figure is final and can never change again. The monthly invoice is generated on the second of the following month, by which time every figure in the period is frozen.

Allowances

An allowance is pooled across the whole organization rather than split between applications or members. On a seat-licensed plan it scales linearly with purchased seats, so a second seat doubles the pool.

Cost accrues only once cumulative usage in the period passes the allowance. That is why the daily spend chart can show zero for the first three weeks of a month and then jump: a day's cost is the increment of the running charge, not that day's usage priced on its own. A metric reads as near its limit at 80% of the allowance, and metrics that have no allowance at all are labelled as metered instead.

Starter shows quantities, not cost

On a plan that does not bill usage overage, the usage page shows every quantity and allowance but a cost of zero, matching what the invoice will say. See Plans.

Reading usage in the console

Open /{organization}/usage. The period picker covers the last six billing periods, and the page splits into a billing cycle summary, the metrics that need attention, a spend overview by category, every metric grouped into Requests and Delivery, Functions, Storage and Platform, and a per-application breakdown.

The per-application figures are an attribution. Allowances are pooled org-wide, so an application's cost is its share of the organization's billable overage by usage share, not a bill rated independently for that application.

Export CSV downloads one row per metric per day for the selected period, named gigadrive-usage-2026-08.csv, with this header:

date,metric,value,included,cost_eur

Values in that file are in the metric's stored base unit and costs carry six decimals.

There is no API or CLI for usage figures. For per-request detail behind these numbers, use Request logs.