How Backblaze B2 is billed
B2 bills storage per TB-month, starting at $6.95. Downloads are free up to three times your average monthly stored volume and $0.01 per GB beyond that; egress to partner CDNs is free. Most API calls are free; one class (Class D) is billed per 10,000 calls after a daily free allowance. The first 10 GB are always free and there is no minimum storage duration.
Those are the figures on Backblaze's pricing page as of 7 October 2026; check there before you decide.
The model in one sentence: B2 is priced for data that is stored much more than it is read. A backup set fits it perfectly; a bucket that serves a busy site's images can cross the 3x egress line.
How our side is priced
We do not sell storage by the gigabyte. A plan gives you one monthly pool, and both your peak object storage and the traffic you serve through the CDN draw from it, one to one. There is no per-request fee, no separate egress line and no minimum billable volume.
Small is $9 a month (449 TL) with a 200 GB pool and 1 bucket. Medium is $19 (949 TL) with 400 GB and 3 buckets. Large is $49 (2,449 TL) with 1,000 GB and 10 buckets. The same plan also covers the CDN, the WAF and DDoS protection in front of the bucket, and container apps if you run any.
So the comparison is not "their price per GB against ours" — we do not have one. It is "what would I pay them for storage plus delivery plus protection, against one plan here".
Serving files, not just keeping them
On B2, publishing files to visitors usually means adding a CDN from a partner and wiring the two together. Here the bucket and the CDN are in the same panel: point a hostname at the bucket and the files are served from our edge with an automatic certificate, behind the same WAF and DDoS protection as the rest of your site.
B2 speaks the S3 API and so do we. Moving across is one rclone job between two S3 remotes, and your code only changes its endpoint (https://s3.cdn.com.tr) and keys.
Where the data sits is your choice
Our storage runs in Turkey, in Europe and in the United States, and a bucket lives where you put it. If your users or your legal obligations are in Turkey, the data can stay in Turkey — which removes the cross-border transfer question under KVKK entirely, rather than leaving you to document it.
Support answers in Turkish and English, in the Turkish time zone, and the invoice can be in Lira.
Where B2 is the better choice
An honest comparison has to say this part.
For backups, archives and anything measured in terabytes that is rarely read, B2 is cheaper than any plan of ours and you should use it. Its integrations with backup software are mature, and it offers features such as Object Lock for immutable backups.
We fit the other case: a site or an application that serves its files to users and wants storage, CDN, WAF and apps on one bill, with the data in a region you choose — including Turkey — and support in Turkish.
Backblaze B2 alternative FAQ
Is your storage compatible with B2?
With B2's S3-compatible API, yes: change the endpoint to https://s3.cdn.com.tr and the keys, and S3 clients keep working. Code written against B2's native API needs to move to an S3 client first.
Is Backblaze B2 cheaper?
Per terabyte of stored data, yes. Our plans make sense when you serve the files as well — CDN, WAF and apps in the same plan — or when the data must stay in Turkey.
Do you charge egress beyond a limit?
There is no separate egress tariff. Traffic you serve and data you store draw from the same monthly pool, one to one; if you outgrow the pool you move to a larger plan.
How do I migrate from B2?
Set up B2 and https://s3.cdn.com.tr as two S3 remotes in rclone and run a sync. Then switch your application's endpoint and keys.
Where is the data stored?
In the region you choose: Turkey, Europe or the United States.