ddrive

github.com · Storage · 1 record · JSON

ddrive (Discord as a filesystem) Storage

caveatemail?card?Rper-object-cap

github.com/forscht/ddrive · messaging · storage/ddrive · JSON · compare

Free tier	Unlimited logical file size and unlimited total: 'Tested with storing 4000 GB of data on single discord channel'. Splits files into 24 MB chunks and fans them across webhooks. unit GB; metered on stored-bytes
Price	none stated
Per-object cap	file size and unlimited total: 'Tested with storing 4000 GB (4000000000000 bytes)
Retention	not stated
Egress	Free — downloads are proxied by ddrive, which pulls refreshed signed URLs from Discord on demand. On the read path the only cost is your own egress.
Identity	email (placeholder) not published
Limits	per-object-cap file size and unlimited total: 'Tested with storing 4000 GB source 24 MB chunk size; ~5 messages/5 s per channel even via webhook (~30 msg/min per webhook reported); metadata lives in Postgres — lose the DB and 3 TB of chunks become unreachable in a channel (author notes a 3 TB cold start takes 30+ min).
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest, ftp rest
Tooling	github.com/forscht/ddrive, 533 stars, MIT, Node 16+ / Docker, REST API with OpenAPI 3.1 spec, Postgres for metadata, web UI. Companion: `tris203/disftp` (FTP front-end for Disbox).
Composes with	1 Discord account x N webhook/channel pairs. Webhooks are used because 'Webhooks are not bound to a user's global rate limit' (Discord docs), so throughput scales with channel count rather than with the 50 req/s token budget.
Reliability	Viable and battle-tested at multi-TB scale, but every download depends on re-deriving a 24 h signed URL, so the front-end must be alive. Two major rewrites (v2 -> v4) invalidated old layouts.
Notes	Unlimited logical file size and unlimited total: 'Tested with storing 4000 GB of data on single discord channel'. Splits files into 24 MB chunks and fans them across webhooks.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 4000.0 GB

Evidence (3)

date	source	what it proved
2026-10-21	github.com/forscht/ddrive	'Tested with storing 4000 GB of data on single discord channel (With max file size of 16GB)'
2026-10-21	github.com/forscht/ddrive	the project's own note, quoted: 'Now uses webhooks instead of bot/user tokens to bypass the discord rate limit', which is to say it routes around the per-token limit by using webhooks; 'I was able to upload file with 5GB of size in just 85 seconds'
2026-10-21	docs.discord.food/topics/rate-limits	'Webhooks are not bound to a user's global rate limit.'

Unknown or withheld values (6)

$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

Built from commit 872967ae41, data as of 2026-10-27. Every value links to its source; freshness badges are computed in your browser. How to read this.