Storage, traffic and credits
Images, video, documents and archives all use the same account credit wallet. CDN deductions have service: "cdn" and the file's namespace when one was supplied. There is no separate CDN balance. Monthly workspace capacity does not include CDN media storage or delivery.
Current rates
GET https://api.oblien.com/cdn/catalog is the public source of truth for tier limits, rates, the effective date and whether billing is active. GET /cdn/policy adds your effective account and namespace limits. Administrators can publish a new policy; previous usage keeps its applicable rate.
The starting rates are 3 credits per GiB-month of storage and 2 credits per GiB delivered by Oblien. At the standard 100 credits per dollar, those are $0.03 and $0.02 respectively. One GiB is 1,073,741,824 bytes; a storage month is 720 hours. These are usage charges, not included storage bundles or an upload fee. Read the current catalog before quoting a price to customers.
For example, retaining 10 GiB for 720 hours and delivering 100 GiB from Oblien costs 30 + 200 = 230 credits at those rates. Shorter retention is charged proportionally. Every retained original and variant counts; compressed-only uploads retain one output instead of a second original.
Storage deductions settle daily for the preceding UTC day, using each object's exact retained byte-time. Delivery deductions normally settle within seconds. Processing delays can postpone a deduction; retries retain the original usage identity and cannot charge it twice. The Usage screen also shows the monthly estimate at the current stored size.
What is measured
Storage is the actual published object footprint integrated over time. Private, unfinished upload inputs are not billed. Trash remains stored and billable until the CDN node confirms physical removal. A purge request, expiry or an HTTP timeout does not itself prove that bytes were removed.
Delivery measures response body bytes sent by Oblien for successful full or range responses. Failed responses and response headers are not charged. HEAD and unmodified responses have no body bytes. Traffic served entirely from a browser or external CDN cache is not measured or billed as Oblien delivery. The dashboard labels these counters as origin delivery, not estimated total audience traffic.
Origin delivery receipts survive worker restart and retry. A receipt can update recorded traffic, the wallet, namespace spending and the credit ledger only once. Storage checkpoints, fractional credits and wallet deductions also commit together. Usage before the billing activation date is not charged retroactively.
Local and bucket-backed objects use these same rates and ledger. Moving bytes internally from an Oblien origin to the customer-facing edge does not create a second customer delivery charge. The API acknowledges a delivery batch after durable receipt storage; an independent, bounded worker settles its credit deductions. A lost acknowledgement replays the same batch identity.
Namespace spending and availability
A namespace may have both byte quotas and a cdn credit spending quota. Byte quotas limit retained storage and monthly published uploads; the spending quota limits credits used for storage and delivery. All namespaces still share the account wallet and account-wide byte ceilings. See CDN quotas.
When credit access is exhausted, new upload admission and origin delivery are rejected with a useful error. Existing storage remains billable until removed. Already authorized or in-flight delivery and cached responses cannot be recalled instantly: origin authorization is cached for up to five seconds, and public responses may remain cached for five minutes or longer if an external cache overrides the response. A spending quota is not a byte-perfect network cutoff.
Use the existing signed credit quota events for warning thresholds and exhaustion. The service is cdn; namespace identity and account ownership remain authoritative. Give customers a way to top up, reduce stored data, or adjust their namespace budget. The CDN does not silently withdraw from a separate payment method.
Dashboard and API
Dashboard → CDN → Usage shows stored and reserved bytes, current-month published uploads, storage and delivery deductions, and current rates. Lifetime file hit/byte counters are separate from monthly spending. GET /cdn/usage and GET /cdn/files/:id provide the corresponding data; namespace filters never broaden namespace-scoped credentials.