Object Storage · Buckets
S3-compatible buckets on Excloud-operated storage.
Excloud buckets use the S3 protocol at buckets.excloud.dev. Existing tools can upload, download, list, presign, and read ranges without custom integration work.
$ exc buckets create my-bucket
one bucket, one month
- 100 GiB stored × ₹1.30/GiB·mo
- ₹130
- 2M write requests × ₹390/million
- ₹780
- 10M read requests × ₹31/million
- ₹310
- data transfer in + out
- free
Rates
Storage and request behavior are documented together.
Storage is metered continuously by the hour, with a month counted as 720 hours. Delete a hundred GiB on Tuesday and Tuesday is when you stop paying for it. Requests are billed per million, split the same way S3 splits them: writes are Class A, reads are Class B.
| Item | What it covers | Rate |
|---|---|---|
| Storage | metered hourly, month = 720 h | ₹1.30/GiB·mo |
| Class A requests | writes — PUT, COPY, POST, LIST | ₹390/million |
| Class B requests | reads — GET, HEAD | ₹31/million |
| Ingress | upload to bucket | free |
| Egress | download from bucket | free |
Data transfer policy is documented in the bucket pricing page, and transfer usage is visible alongside storage and request usage.
S3-compatible
Point your existing tools at one endpoint.
Anything that speaks the S3 protocol works against buckets.excloud.dev with AWS Signature Version 4: aws s3, rclone, boto3, the AWS SDKs, MinIO mc. Set the region to auto and use path-style addressing, and the rest of your code stays as it is.
- One endpoint for every org. Your access key identifies you, so the org ID never goes in the URL.
- Access key IDs are prefixed EXC, so you can tell them from AWS keys at a glance.
- Multipart uploads, range reads, presigned GET URLs, and encryption at rest are all supported.
The full list of supported operations is in the S3 compatibility docs.
$ exc buckets create backups $ exc buckets keys create laptop ACCESS_KEY_ID: EXCEXCLOUDEXAMPLEKEY SECRET_ACCESS_KEY: shown once — store it now $ aws --endpoint-url https://buckets.excloud.dev \ s3 cp ./photo.jpg s3://backups/photo.jpg upload: ./photo.jpg to s3://backups/photo.jpg
The details
Small decisions that save you a headache.
The name "backups" is available
Bucket names only need to be unique within your organization, so you can call a bucket backups or assets without racing the rest of the internet for the name.
Hourly metering, honest months
Storage is measured every hour and a month is exactly 720 of them. A bucket that holds data for a week costs a week, not a billing cycle.
Scope is documented
Endpoint and location details are in the docs, so automation can target the service without guessing at hidden region behavior.
Get started
Point your S3 tooling at Excloud buckets.
Open the console, create a bucket, and point your tooling at buckets.excloud.dev. The quickstart covers access keys, endpoint configuration, and path-style addressing.
$ exc buckets create my-bucket