DuDrive · for developers

Images for your product, from your backend.

Your server requests an upload URL, the file goes straight to storage, and you keep a stable link on drive.duworks.xyz.

Images only. Usage-based billing, separate from Workplace.

app.duworks.xyz/drive

product-images

1,284 files

https://drive.duworks.xyz/…/shoe-42.webp

Features

What the first version does

Images only, with a hard quota on stored bytes and monthly uploads, checked before the upload is signed.

One secret API key

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. Bytes stay in private storage, 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.

DuDrive has its own usage-based billing in the Console and is not part of the Workplace plan.

Activate DuDrive in your workspace

Create a key in the Console and make your first signed upload.

Get started