Gemfury — Public (free) plan
- Free allowance
- Public plan is $0/mo with UNLIMITED public packages, unlimited versions and unlimited collaborators, and NO private packages.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- institution?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-cap300 MB per file; 20 MB per file
- 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 | Public plan is $0/mo with UNLIMITED public packages, unlimited versions and unlimited collaborators, and NO private packages. No storage figure appears anywhere on the pricing table — the plan matrix lists only collaborators / private packages / public packages. The only published numbers are per-file caps. unit unlimited; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
HARD per-file ceiling: 300 MB per file via push.fury.io/Dashboard/git builds, and only 20 MB per file through a repository endpoint (gem.fury.io etc.). Git-backed packages: 500 MB per repo, 20 MB per file. Public/private is a per-package toggle; everything uploads private first and must be flipped public. No private packages at all on the free plan. |
| Identity | institution (inferred, not read) not published |
| Egress | No published bandwidth allowance or per-GB rate for the Public plan; public repos are served from the fury.io edge to anonymous clients (probe below). Nothing meters delivery in the documented plan matrix. |
| Per-object cap | 300 MB per file (300000000 bytes) |
| Retention | Small independent operator (fury.co, the same shop as the old gemfury.com); the 20 MB repository-endpoint cap silently breaks pushes that work through the API, and cancelled accounts have packages deleted after ~1 month. (30 days) |
| Interface | rest, cli rest (push.fury.io upload API), per-ecosystem endpoints (gem/npm/pypi/nuget/apt/yum/maven/php/go), Gemfury CLI |
| Tooling | fury push CLI and curl upload; documented at gemfury.com/help/upload-packages; public repo is consumed by stock pip/gem/npm/apt/yum with the account URL. |
| Composes with | Unlimited packages × unlimited versions per account, and unlimited free accounts. Since there is no aggregate storage line item, the effective ceiling is (unlimited public packages) × (per-file cap) — the 'per-record unlimited' pattern rather than a bucket cap. |
| Reliability | Small independent operator (fury.co, the same shop as the old gemfury.com); the 20 MB repository-endpoint cap silently breaks pushes that work through the API, and cancelled accounts have packages deleted after ~1 month. |
| Parsed numbers |
|
Evidence 4
| date | source | what it proved |
|---|---|---|
| 2026-08-28 | fury.co/pricing/ | read live (also archived 2026-08-28): 'Public free $0/mo'; table row 'Free | ∞ collaborators | - private | ∞ public | $0/mo'; no storage or bandwidth line anywhere on the page |
| 2026-10-21 | gemfury.com/help/limits/ | read live: 'Package files have an absolute limit of 300MB per file uploaded ... packages uploaded to a repository endpoint (e.g. gem.fury.io) are limited to 20MB'; 'Git repositories have a 500MB size limit, with a 20MB limit for individual files' |
| 2026-10-21 | gemfury.com/help/public-packages/ | read live: 'Gemfury supports distribution of public packages without the need to distribute credentials ... Anyone can plug it into one of the supported package managers' |
| 2026-10-21 | pypi.fury.io/arrow-nightlies/ | probe: GET -> 200, returns a live 'Simple Index' listing pyarrow and nanoarrow anonymously; GET https://pypi.fury.io/arrow-nightlies/pyarrow/ -> 200. GET https://gem.fury.io/arrow-nightlies/ -> 404 and https://gem.fury.io/solmaz/ -> 401 (private endpoints gated, public index open) |
Unknown values 2
- per object cap notes: 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