Home / Storage
Discourse hosted Free plan
www.discourse.org/freePaaSstorage/discourse-hosted-free-planJSONcomparereport an errorprovider JSON
- Free allowance
- 5 GB storage per free site, with unlimited topics, chat and members
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported4 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 5 GB storage per free site, with unlimited topics, chat and members unit GB; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | Free; uploads served from *.discourse-cdn.com behind CloudFront, so a Cloudflare/CloudFront cache sits in front already |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | rest, rclone rest |
|---|
| Tooling | Discourse's own REST API is fully available on the free site (POST /uploads.json with an API key, /posts.json, /latest.json); no rclone backend |
|---|
| Composes with | 5 GB x N free sites. Free sites are self-serve from id.discourse.com/create-site with a Discourse ID; provisioning is rate-limited but per-hour, not per-account. 100 sites = 500 GB; 400 sites = 2 TB. |
|---|
| Reliability | Free plan launched 2026-02 and is still labelled beta; the provisioning throttle is the real scaling brake, and the 10-category cap makes bulk-upload workflows awkward. |
|---|
| Parsed numbers | |
|---|
Evidence 4
Unknown values 4
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read