drophost
drophost vs Amazon S3
- drophost: zero bucket config
- S3: infrastructure storage
- drophost: passwords and MCP built in
Primitives versus product
S3 gives you objects. You still build the upload UI, URL strategy, auth, and HTTPS edge. drophost is that product already: drop zone, project URL, optional password, optional custom domain. Free remains useful to validate the loop at 2 MB before you pay.
Cost models
S3 can be pennies at scale and expensive in engineering time at small scale. drophost Starter at €5/mo buys the productized path. Compare fully loaded cost, not storage GB alone. Starter at €5/mo is the usual upgrade when passwords or domains appear.
Static website hosting on S3
Possible, with gotchas. drophost Website mode is the short path for previews. Production static hosting at scale may still belong on S3+CloudFront or a dedicated platform. Pro at €12/mo fits teams that keep many parallel links online.
Security responsibility
Misopen S3 buckets are a classic incident class. drophost narrows the knobs: public project links or password gates. Different responsibility boundary.
Agents and scripts
AWS SDKs talk to S3. drophost MCP talk to projects with hashed keys. Use AWS when the object is part of your platform; use drophost when the object is a human handoff.
Decision rule
Infrastructure asset → S3. Human handoff / preview → drophost. Complement, do not replace.
The hidden checklist behind “just put it in S3”
Bucket, block public access settings, policy, CORS, CloudFront, HTTPS, upload UI—or a pre-signed URL script. drophost is what teams build the tenth time they get tired of that checklist for a human handoff.
Platform assets versus people assets
App images and data lakes belong in S3. The PDF you owe a customer this afternoon belongs on a productized share link.
Pre-signed URLs are not a product
Engineers reach for pre-signed S3 URLs, then discover expiry, UX, and support burden. drophost is the productized answer for human recipients. Keep pre-signed URLs for machine-to-machine platform needs where IAM already exists.
Static website hosting footnotes
S3 static website hosting works until you need HTTPS defaults, password gates, and a sane upload UI for a non-engineer. At that point you either build a small app or use drophost. Building the app is fine for your platform; it is rarely fine for Thursday’s client deck. Prefer S3 for platform objects behind IAM; prefer drophost for people who should never see a bucket policy. Pre-signed URLs are not a customer-facing product.
Support desk reality
When a non-engineer asks where the file lives, “in the bucket” is not an answer they can use. “Here is the link” is. drophost produces the second answer without a ticket to platform engineering for IAM help.
HTTPS and DNS chores
S3 website endpoints and CloudFront distributions are real work. drophost’s default HTTPS URL removes that chore for human handoffs that never needed a distribution.
Audit stories
Explaining a public object ACL in an audit is harder than explaining a passworded drophost link you deleted after the deal. Pick the story you want to tell later.
drophost vs Amazon S3: feature comparison
| Feature | drophost | Amazon S3 |
|---|---|---|
| Bucket / IAM setup | None | Required |
| Browser upload UI | Yes | DIY |
| Password gate | Starter / Pro | DIY |
| Static site option | Yes | Possible |
| MCP / agent publish | Yes | AWS SDKs |
| Best fit | Handoffs | Infrastructure |
Common questions
Is drophost an alternative to Amazon S3?
For human handoffs, yes. For infrastructure object storage, no—keep S3.
Do I need IAM to share a file on drophost?
No. Sign in, upload, copy the URL.
Can drophost replace CloudFront?
Not as a production CDN design. Use drophost for productized share links; use CloudFront for platform traffic.
Does drophost include a password gate without custom code?
Yes on Starter and Pro.
Can scripts upload to drophost like to S3?
Yes via MCP with a hashed API key—still as projects, not raw buckets.
Related
You probably do not need IAM for this PDF
Upload on drophost for human handoffs. Keep S3 for production assets your infrastructure already manages.