How Cloudflare R2 is billed
R2 charges for three things and not for a fourth. Storage is billed per GB-month ($0.015 for Standard, $0.01 for Infrequent Access). Every write-type request (Class A) and every read-type request (Class B) is billed per million ($4.50 and $0.36 for Standard). Egress — the data you serve out — is free. The first 10 GB-month, 1 million Class A and 10 million Class B requests each month are free.
Those are the figures on Cloudflare's R2 pricing page as of 7 October 2026; check there before you decide, prices change.
The model matters more than the numbers: on R2 your bill grows with storage and with request count, not with traffic. A bucket of millions of small objects read constantly is billed differently from a few large files downloaded often.
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".
Moving from R2 changes one line
R2 and our storage both speak the S3 API, so your code does not change — the endpoint and the keys do. Point the client at https://s3.cdn.com.tr and the AWS CLI, boto3, aws-sdk, rclone or s3cmd keep working as they are.
Copying the data across is one rclone job with two S3 remotes, R2 as the source and us as the destination. If you serve the files on your own domain, point that hostname at the bucket through our CDN and the URLs your users have do not change.
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 R2 is the better choice
An honest comparison has to say this part.
If you store many terabytes and serve them heavily, R2's free egress at any scale is very hard to beat, and a per-GB storage price will be cheaper than any plan's pool. If your application already lives on Cloudflare Workers, R2 bindings are native there and nothing we offer replaces that. And Cloudflare's network is global in a way ours is not.
We fit the other case: a project that wants storage, a CDN in front of it, a WAF and perhaps a container app on one bill and one panel, with the data in a region you choose — including Turkey — and support that answers in Turkish.
Cloudflare R2 alternative FAQ
Is your storage compatible with R2?
Both implement the S3 API, so anything that talks to R2 through an S3 client talks to us after you change the endpoint (https://s3.cdn.com.tr) and the access keys. R2-specific features such as Workers bindings have no equivalent here.
Do you charge for egress like other S3 providers?
Not as a separate line. Traffic you serve through the CDN draws from the same monthly pool as your stored data, one to one. There is no per-request fee either.
Is R2 cheaper?
For pure storage at scale, usually yes — R2 bills about $15 per TB-month with free egress. Our plans make sense when you also need the CDN, WAF and apps around the bucket and want them on one bill, or when the data has to stay in Turkey.
How do I move my data from R2?
Configure two S3 remotes in rclone — R2 and https://s3.cdn.com.tr — and run rclone sync from one to the other. Your application then only needs the new endpoint and keys.
Can I keep my own domain on the files?
Yes. Point a hostname at the bucket through the CDN; the public URLs stay on your domain with an automatic certificate.