Your existing S3 tooling just works
Our object storage exposes an S3-compatible API. The only thing you change in your code or deploy scripts is the endpoint: https://s3.cdn.com.tr
AWS CLI, boto3, aws-sdk, MinIO client, s3cmd, rclone — anything that speaks S3 keeps working. Verifying it is one line:
aws --endpoint-url https://s3.cdn.com.tr s3 ls s3://your-bucket
No new SDK to learn, no data model to change, no application to rewrite.
Included in your plan — no second provider, no second bill
Buckets come with the platform plan: Small gives you 1 bucket and 2 access keys, Medium 3 buckets and 6 keys, Large 10 buckets and 20 keys.
There is no separate storage provider to sign up with, no second card to register, and no pair of invoices to reconcile at the end of the month. Storage, apps, database, cache and CDN sit in the same account and the same panel.
Usage is metered: GB-hours for stored data, $0.02 per GB for egress.
A CDN in front of your bucket, without buying a delivery layer
The concrete benefit of getting object storage from a CDN company: you do not have to buy a second product to publish your files.
Content in your bucket can be served from behind our edge network, including our four PoPs in Turkey. Images, video, backups, user uploads or static site output reach the visitor from the nearest point instead of going back to origin every time.
WAF and DDoS protection live in the same edge layer, so you are not bolting security onto storage afterwards.
Bind it to your app, manage it from the panel or the CLI
When you bind a bucket to a container app, the credentials are passed into the app's environment automatically — nothing to commit to a repo, no environment variables to copy by hand.
Everything is available in the panel, and on the command line if you prefer:
cdnctl object-storage buckets list --account <account_uuid> cdnctl object-storage buckets create --account <account_uuid> --name uploads
An access key's secret is shown only at creation time — we cannot retrieve it afterwards either, so store it somewhere safe right then.
Priced in Turkish Lira, not tied to the exchange rate
Buying from Turkey, your plan price is fixed in Turkish Lira; your invoice does not move every time the dollar does.
Support is in Turkish and in your time zone. When something breaks you are not writing an English ticket and waiting for the next day.
And if it is not for you, same-day refund: nothing is committed during the 15-day free trial.
Object Storage FAQ
What is the endpoint?
https://s3.cdn.com.tr — set that as the endpoint in any S3-compatible client. Tools that require a region can be left at the default.
Do the AWS CLI and my existing SDKs work?
Yes. Because the API is S3-compatible, AWS CLI, boto3, aws-sdk, MinIO client, s3cmd and rclone all work as they are once you change the endpoint. To check: aws --endpoint-url https://s3.cdn.com.tr s3 ls
How many buckets and access keys do I get?
It depends on your plan: Small 1 bucket / 2 keys, Medium 3 buckets / 6 keys, Large 10 buckets / 20 keys. Upgrading raises the limits immediately.
How is storage billed?
By usage: stored data is metered in GB-hours and outbound traffic at $0.02 per GB. There is no separate storage subscription — usage appears on your platform invoice.
Can I serve files from the bucket over the CDN?
Yes — that is the point of buying storage from a CDN provider. You can serve content from behind our edge network, delivering from the closest point to the visitor including our PoPs in Turkey, without purchasing a separate CDN product.
Is migrating my data difficult?
Because it is S3-compatible you can copy straight from your existing bucket with standard tools like rclone or aws s3 sync. On the application side the only things that change are the endpoint and the access keys.