Affordable CDN for File Delivery

"Affordable" in CDN-land usually means a low headline per-GB rate that quietly compounds: bandwidth metered separately from storage, requests billed on their own line, and a different price in every region. The bill you actually receive depends on traffic you can't perfectly predict, which is the opposite of affordable when something goes viral. files.link takes a different shape — CDN delivery isn't a separate meter at all.

Storage, delivery across the edge network, and API requests all draw down one prepaid credit balance, so the cost you reason about is a single number, not three.

That single-meter model is what makes it genuinely budgetable. Instead of forecasting GB-out per region and multiplying by a rate card, you watch one balance fall and top it up. Auto-recharge handles the rest: when credits run low the account tops up on a step schedule (climbing toward a cap) so a sudden traffic surge keeps serving from the edge without you babysitting a dashboard at 2am. There's no per-GB bandwidth invoice and no regional pricing tier to decode.

Who this fits: a marketing site whose hero video occasionally gets shared widely; a side project that could hit the front page of a news aggregator; a static asset host that serves the same logo and CSS bundle millions of times. In all of those, delivery volume dwarfs the amount of data stored, which is exactly the case where a per-GB egress model punishes you and a prepaid-credit model stays flat and legible.

Compared to a per-GB CDN like Bunny or a hyperscaler's CDN, you trade a lower theoretical floor for a far more predictable ceiling — and you skip configuring a distribution, an origin pull, and cache rules entirely, because the CDN is just on for every public file the moment you upload it. The honest caveat: this is prepaid (no free tier), and sustained extreme abuse is governed by fair-use terms rather than a surprise per-GB charge — but for ordinary spiky web traffic, the bill is something you can actually plan around.