Blob storage
An instance holds as many buckets as you care to make, and the buckets hold your files. You pay for one storage quota across the instance, not for the bytes you happen to be holding, at one flat rate per block with no largest size. Reads, writes and transfer are never charged on top.
€1 per 25 GB a month · downloads free
Key features
The three things worth knowing before the price: what protects it once it is written, how you get it here from somewhere else, and what happens when somebody else's workload gets busy.
AES-256
on every object, at rest
Objects are encrypted on the way to disk and decrypted on the way back out, below your code. There are no keys to manage, no setting to find, and nothing to change in how you read and write.
Migrate & sync
from Azure, AWS or GCP
A managed job copies the objects across and then keeps the two ends in step — from another cloud, or from one Dripspace bucket to another. Point it at a source, watch it run, and switch over once it has caught up.
Isolation per bucket
on shared infrastructure
Each bucket is handled on its own, so somebody else's busy hour does not slow yours down. The hardware underneath is shared, so this reduces noisy neighbours rather than removing them. More buckets, more separation.
What you get
An HTTP API with clients for the runtimes we run, links you can hand a browser without proxying the bytes through your API, and versioning, lifecycle and usage in the same dashboard as everything else.
Plain HTTP for objects and prefixes, with .NET, Node and Bun clients matching the runtimes we run. Large objects upload in chunks and resume where they stopped.
A new bucket is closed to the internet. Publishing an object or a whole prefix is a switch you throw, and the dashboard lists everything currently public.
Hand a browser a URL that uploads or downloads one object and then stops working. Your service never proxies the bytes and never ships a long-lived key.
Keep old versions, expire temporary objects on a schedule, and restore a deleted key without a support ticket.
How full the instance quota is, which buckets and prefixes hold it, and the request mix — before you hit the ceiling, not after.
Every object is written across several storage devices inside the region you chose, so a failed drive loses nothing. It is included in the price rather than a tier you add — and the copies stay in that one region rather than spanning several.
Pricing
Metered storage means your invoice moves with every upload, and egress charges mean a popular file is a financial event. Neither is true here. Buy the quota in blocks and add or drop blocks whenever you like — the change takes effect immediately and is prorated. Buckets inside the instance cost nothing, so the only number that moves is the ceiling.
€1 / 25 GBper month
25 GB upwards, no maximum
The quota moves 25 GB at a time, either way, and changes are prorated. There is no largest instance and no allowance to use up first — the hundredth block costs what the first one did.
Transfer and operations included
Reads, writes and lists are unmetered, and transfer is not billed in either direction. The quota is the whole blob-storage line on your invoice.
What counts against it
The bytes held across every bucket in the instance, including versions kept by versioning and objects waiting on a lifecycle rule. Buckets themselves are free — make as many as you want. Delete objects and the space comes back the same day.
Quotas can raise themselves, if you let them
An instance can be set to lift its own quota 25 GB at a time as it fills, so a quota you forgot to watch does not turn into a failed write. It costs nothing to switch on and you pay for the larger quota, as you would have anyway. It is off until you turn it on, because it is the one thing here that can move your bill without you asking.
Notifications
You are told when an instance is nearing its quota while there is still room to act, whether automatic growth is on or off. A ceiling is never something you find out about from a failed write.
Questions
An instance is the thing you pay for: one blob-storage service with a storage quota attached. A bucket is a container inside it, and the buckets hold your files. Make as many buckets as you like — they cost nothing and all draw on the same instance quota.
Create a bucket, hand your frontend a link that expires, and leave transfer off the invoice.
