CodeFloe

codefloe.com · Storage · 1 record · JSON

CodeFloe (Forgejo, Hetzner Germany) Storage

caveatanonymousno cardR

codefloe.com · registry · storage/codefloe · JSON · compare

Free tier	5 GB Git + 20 GB packages + 10 GB Git LFS + 10 GB attachments per account/organization; unlimited public and private repositories unit GB; metered on unstated
Price	none stated
Per-object cap	not stated
Retention	Single small operator on one Hetzner box; nightly off-site backups with 90-day retention described as disaster recovery, not per-account restore (90 days)
Egress	Download traffic for packages, container images and LFS is counted per account per month but 'There is no limit today' — unlimited, and the endpoint is Cloudflare-fronted. Git clones, release assets and attachments are explicitly not counted.
Identity	anonymous derived from the record's prose, not from an identity field, and no signup was executed: cross four subjects, and each further account carries the same 45 GB. Registry blobs are anonymous-pullable, so shard across repos like any OCI store. Per-account quotas only (5 GB git / 20 GB packages / 10 GB LFS / 10
Binding	none no constraint in the record binds at this scale; the record carries no limit of a kind the vocabulary names
Interface	rest, webdav, oci, rclone rest
Tooling	Full Forgejo API v1 (packages, generic, OCI registry, releases, LFS) + rclone's Gitea/Forgejo-compatible WebDAV-free REST via any HTTP client; OCI via ORAS/skopeo; package registry speaks Generic/Docker/npm/PyPI etc.
Composes with	Unlimited free accounts -> 5+20+10+10 = 45 GB of separately-metered pools per identity. Because packages (20 GB) and LFS (10 GB) are separate pools from Git (5 GB), one account yields ~45 GB across four subjects, and each further account carries the same 45 GB. Registry blobs are anonymous-pullable, so shard across repos like any OCI store.
Reliability	Single small operator on one Hetzner box; nightly off-site backups with 90-day retention described as disaster recovery, not per-account restore. Explicit published policy of monitoring several accounts used to exceed its quota and deleting/suspending — the chaining path is actively watched, unlike GitLab's.
Notes	5 GB Git + 20 GB packages + 10 GB Git LFS + 10 GB attachments per account/organization; unlimited public and private repositories
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (7)

date	source	what it proved
2026-10-21	docs.codefloe.com/usage-quotas/	'Git repo size 5 GB \| "Packages" size 20 GB \| Git LFS 10 GB \| Attachments 10 GB'; 'There is no limit today' on download traffic
2026-10-21	codefloe.com/pricing	'Unlimited public and private repositories', '5 GB Git storage per account'
2026-10-21	codefloe.com/api/v1/version	probe: GET -> {"version":"16.0.6"} (live Forgejo 16, not a brochure)
2026-10-21	codefloe.com/v2/	probe: GET -> 401 WWW-Authenticate Bearer realm=https://codefloe.com/v2/token (registry live)
2026-10-21	withheld	probe: anonymous token for CodeFloe/forgejo-codefloe:pull -> 200, then GET /v2/CodeFloe/forgejo-codefloe/manifests/latest with that token -> 200 application/vnd.oci.image.index.v1+json, docker-content-digest sha256:d75b4b8f... (anonymous OCI pull works)
2026-10-21	codefloe.com/user/sign_up	probe: GET -> 200 (open registration)
2026-10-21	codefloe.com/api/v1/packages/CodeFloe?limit=5	probe: GET -> 200, lists container packages incl. sha256-digest tags (anonymous package enumeration)

Unknown or withheld values (5)

$.evidence[4].url private-url
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes 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.