Images for your product,
from your backend.
DuDrive stores images for a DuWorks workspace. Your server requests an upload URL, the file goes straight to storage, and you keep a stable link on drive.duworks.xyz.
What the first version does
Images only. A hard quota on stored bytes and monthly uploads, checked before the upload is signed.
One secret API key
Create it in DuDrive. It is shown once and stored as a hash. Your backend sends it as Authorization: Bearer. It is not the widget public key.
Signed upload
Ask for a short-lived upload URL, then put the file straight into storage. DuDrive keeps the id, type, size, and dimensions.
A stable URL
Each file has a public URL on drive.duworks.xyz, plus list and delete. The bytes stay in private storage and are cached at the edge.
Three cached variants
After upload, DuDrive writes a thumbnail, a max-width resize, and a WebP once. There is no live query-string transform.
Activate DuDrive in your workspace
The dashboard will live at drive.duworks.xyz. Console only opens it.
- One secret key, shown once
- Signed upload, then a stable public URL
- Thumbnail, resize, and WebP cached after upload