No required US cloud drive in the intake path.
Run Sprag where your policy allows and point uploads at storage you choose.
Dropbox File Request alternative
File requests without the Dropbox path.
Dropbox File Requests are useful when Dropbox is the right storage account. Sprag is for sensitive intake where the operator wants a self-hosted upload boundary, sovereign storage, and no shared folder assumptions.
Comparison
Dropbox collects into Dropbox. Sprag makes intake the product.
Dropbox's help docs describe file requests as a way to collect files from other people into a folder you choose in your Dropbox account. That is a good cloud-drive workflow. Sprag is narrower: a one-way intake page with no folder listing or sender-side retrieval path.
Source: Dropbox file request documentation.
| Question | Dropbox File Requests | Sprag |
|---|---|---|
| Where files land | A selected Dropbox folder. | Operator-chosen S3-compatible storage. |
| Product shape | Cloud-drive file request. | Dedicated one-way secure intake. |
| Sender return path | The request exists inside a drive account model. | No listing, folder, sync, edit, delete, or download path. |
| Sovereignty | Dropbox account and Dropbox infrastructure. | Host, region, and storage are operator choices. |
| Hardening | Cloud-drive controls. | Plain HTTPS, E2E-required, or onion-only modes. |
Sprag edge
Use Sprag when the upload boundary itself is sensitive.
The sender gets a receipt, not a folder.
The public page receives files and does not become a browsing or collaboration surface.
Intake facts stay attached to the arrival.
Grouped submissions, receipts, hashes, manifests, and sealed pages support later explanation.