Sell object storage on Amazon S3, Cloudflare R2, DigitalOcean Spaces or MinIO — any mix, from one Blesta module
Sell DigitalOcean Spaces object storage under your own brand — provisioned, metered and billed in Blesta
Made and supported by Projektif Digital Ltd. Runs inside PD Modules, the panel every module installs into.
PD DigitalOcean Spaces lets a hosting company sell DigitalOcean Spaces object storage as its own product in Blesta. Your customer orders a storage package, and a private Spaces bucket with its own access keys is created in your DigitalOcean account within minutes. The customer manages it from your Blesta client portal, you set the price, DigitalOcean bills you at cost, and the difference is your margin.
It is built for hosts who already use DigitalOcean, or who want a simple S3-compatible storage line for backups, media and application data, without handing out DigitalOcean logins and without building the tooling to create buckets and keys by hand.
Twelve datacenters, chosen by the customer. Customers pick their bucket's location: New York, Atlanta, Richmond, San Francisco, Toronto, Kansas City, Amsterdam, London, Frankfurt, Bangalore, Singapore or Sydney. One package covers four continents.
Every customer is isolated by DigitalOcean itself. Each service gets its own bucket and its own Spaces access key whose grants cover that bucket only. A customer's key cannot list or reach any other bucket or any other data in your account, even if they try. Isolation is enforced by the provider, not by convention.
One token to connect. You connect your account with a single DigitalOcean Personal Access Token, stored encrypted and never shown to customers. Customer keys are never sent to DigitalOcean for storage.
Your other DigitalOcean resources are untouched. Droplets, databases and existing Spaces carry on exactly as before. The module works only inside its own bucket namespace, so you can run it on the account you already use.
Works with every S3 tool. The endpoint is the standard Spaces address for the customer's region, and any S3-compatible client or SDK that supports a custom endpoint connects with no modification.
Quotas you can sell in tiers. Blesta does not invoice usage-based overage, so storage is sold in quota tiers, one package option per tier. Usage is measured daily and shown to customers against their quota, and you see who is over in the admin panel.



Bucket management, share links and storage settings are each a switch on the package. Turn one off and it disappears from the customer's page and its actions are refused. The pages follow Blesta's client portal theme and are fully translatable.
PD DigitalOcean Spaces is one paid module with everything included: provisioning, metering, quotas, versioning, clean-up rules, CORS, share links, retention and reconcile. There is no free tier. There are no per-gigabyte fees to us: your buckets live in your own DigitalOcean account, you pay DigitalOcean at cost and set your own sell price.
Quota emails warn at 80% and 100%. On Spaces, going over quota never pauses uploads, in either quota mode, because a Spaces key cannot allow deleting files without also allowing uploads. Downloads always keep working.
If your subscription ever lapses, nothing is deleted. You get a 14-day grace period with everything working, then admin management locks while customers keep being served, and only after that do customer features pause behind a neutral message.
Yours. You connect your own account, and every customer bucket is provisioned into it. You pay the provider at cost, set your sell price in Blesta, and keep the difference.
Every order gets its own bucket and a Spaces key scoped to that bucket alone. One customer's credential cannot reach another's data, and your master credentials stay on your Blesta server — they are never sent to the customer or stored in the client area.
A daily task measures each service's real usage and writes it into Blesta's disk-usage fields. Native overage billing, quota warnings and the client-area usage graph then work exactly as they do for hosting products — there is nothing extra to configure.
New uploads are blocked, but downloads always keep working, so a customer over quota can still retrieve everything they have stored. Raising their plan restores uploads immediately with all data preserved.
Only if you choose that. By default, terminating a service revokes access instantly but keeps the bucket and its contents for a retention window you set. Purging then needs your approval and typing the bucket name to confirm — there is no single click that destroys a customer's data.
Yes, through the standard Blesta upgrade/downgrade flow. Quota changes apply with data preserved in both directions; downgrading below current usage pauses uploads rather than deleting anything.
PHP 8.1+ and a working Blesta's cron. The module talks to DigitalOcean Spaces over its standard HTTPS API — there is nothing to install on the server and no daemon to run.
PD Object Storage is the flagship covering Amazon S3, Cloudflare R2, MinIO and DigitalOcean Spaces in one module. This edition is the same engine focused on DigitalOcean Spaces alone — choose it if that is the only backend you sell, and move up to the flagship if you later add another.