A bucket, and a place to actually work in it
The S3 endpoint is for your application. The workspace in the portal is for you and everyone on your team who would rather not install one.
A file workspace, not just an endpoint
Everything below runs from the bucket's own page in the portal. Upload a file, make a folder, hand a colleague a link, remove an object — with the same permissions that guard the rest of your infrastructure.
Private unless you say otherwise
An object is private the moment it lands; you choose at upload time whether to publish it. Sharing one that stays private is a signed link that expires on its own, so nothing you send out lives forever.
S3-compatible, so your code already speaks it
Buckets are provisioned on DigitalOcean Spaces, and the bucket's S3 endpoint appears on its page as soon as provisioning finishes. It speaks the S3 API, so the SDK, backup tool or framework driver you already use can point straight at it.
Put it behind a CDN with one switch
CDN delivery is a toggle on the service. It is queued as an operation like any other, so you watch it run, the CDN endpoint appears on the bucket once it is live, and you can switch it back off the same way.
How your buckets behave
Sizing a media library or a backup target? [email protected] reaches a person who will work it out with you.
Only the people you let in. An object is private unless you publish it at upload time, and the bucket's page shows its current access level and delivery state rather than leaving you to guess. To share a private object you generate a signed link that expires after 15 minutes.
That is the point. The storage is S3-compatible and the bucket's S3 endpoint is shown on its page once provisioning finishes, so an S3 SDK or backup tool can point straight at it. The file workspace in the portal is a convenience on top of that, not the only way in.
Stored bytes count against the storage quota and outbound traffic against the transfer allowance. Both, plus the object count, are on the service page as they stand right now — not as a monthly summary you have to wait for.
Yes, with one switch. CDN delivery is queued as an operation like any other, so you can see it run and see it turned off again, and the CDN endpoint appears on the bucket once it is enabled.
You cancel from the bucket's own page, and the window runs from the moment you ask rather than to the end of the term you have paid for. The bucket stays reachable for 7 days so you can pull your data out, support can still recover it for another 14 days, and only then are the bucket and its objects removed. The exact dates are written onto the service when you confirm.
Somewhere private for the files, that you can still open
An S3 endpoint your code can point at, and a file workspace in the portal for the days you would rather just look.
GHS 125.00a month
The cheapest bucket the catalogue is carrying today250–5,000 GB of object storage, depending on the plan
6 bucket actions in the portal, no S3 client needed
Temporary share links expire after 15 minutes
Cancel and keep access for 7 days
Nothing is charged until you place an order. Not sure how much space the archive needs? Sales is at [email protected].