fshy

Home / Storage

Debian

debian.org · 3 records in Storage · JSON

Records 3

salsa.debian.orgPaaSstorage/debian-salsa-gitlab-with-generic-package-registryJSONcomparereport an error

Free allowance
No published total-storage quota, but a fully published per-object table on the instance-configuration page.
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-capper-file caps: Generic 5 GiB
Evidence
reported3 sources; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierNo published total-storage quota, but a fully published per-object table on the instance-configuration page. Package registry per-file caps: Generic 5 GiB, Conan 3 GiB, Maven 3 GiB, PyPI 3 GiB, Terraform 1 GiB, npm/NuGet 500 MiB, Helm 5 MiB. Core GitLab: max push size '-' (unlimited), max attachment 20 MiB, job artifact 750 MiB, pages 300 MiB, snippet 50 MiB, import remote file 10 GiB, download file 5 GiB.
unit GiB; metered on stored-bytes
Pricenone stated
Limits
  • write-gated reviewed due to the high volume of spam registrations source
  • write-gated approved source
  • per-object-cap (binding) per-file caps: Generic 5 GiB source
per-object-cap: 5 GiB per Generic package file; 750 MiB per CI artifact; THE GATE: 'New user registrations are manually reviewed due to the high volume of spam registrations. It may take a few days before a new account is approved.'
Identityinstitution (inferred, not read) not published
EgressFree. Debian-hosted infrastructure with no billing, no per-GB meter, and package/registry downloads served straight from the instance. No Cloudflare dependency to worry about.
Per-object capper-file caps: Generic 5 GiB (5368709120 bytes)
Retentionper-object-cap: 5 GiB per Generic package file; 750 MiB per CI artifact; 300 MiB Pages. retention: indefinite for packages and repos (no pruning policy published on this page)
Interfacessh, git git
ToolingFull GitLab: git over SSH/HTTPS, GitLab Generic Package API (PUT /projects/:id/packages/generic/:package_name/:version/:file_name), CI runners, glab/lab CLIs, python-gitlab. Max push size is '-' (unlimited) which is the interesting cell - the per-object cap is on the registry, not on git.
Composes withUnlimited projects per account x 5 GiB per Generic-package file x unlimited files per package version x unlimited versions. Plus unlimited-size git pushes as a second surface. The binding limit is account creation, not storage.
ReliabilityManual registration review is the whole story - it converts account-farming from an API call into a queue measured in days, which is fatal for the 'unlimited free orgs' pattern that made the Google-Drive-service-account trick work. Once in, the surface is clean and standard GitLab. Public read is fine (project pages and package downloads are anonymous).
Parsed numbers
  • has-free-tier 1
  • per-object-cap 5 GiB
Evidence 3
datesourcewhat it proved
2026-10-21salsa.debian.org/help/instance_configuration'## Size Limits ... Maximum push size | - ... Maximum job artifact size | 750 MiB'; '## Package registry ... Generic | 5 GiB'
2026-10-21salsa.debian.org/users/sign_uppart of the text of Limits, above
2026-10-21salsa.debian.org/help/instance_configuration'There are several size limits in place for the package registry.' (table as quoted in quota)
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

snapshot.debian.org/storage/debian-snapshotJSONcomparereport an error

Free allowance
Read-only ingest of the Debian archive; no user write path at any size.
Verdict
fails: quotathe free allowance is too small to matter
Cost
not stated
Identity
email?placeholder, not evidence; card unknown, phone unknown
Binding limit
noneno named constraint binds
Evidence
documented5 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
Free tierRead-only ingest of the Debian archive; no user write path at any size. 172 TB is theirs, not yours.
unit none; metered on none
Pricenone stated
Identityemail (placeholder) not published
Egressnot recorded
Interfaceunknown
Toolingnot recorded
Evidence notedocumented The front page of snapshot.debian.org, re-read on 2026-11-03, says the archive holds 172 TB and describes a read-only history of old Debian packages with no upload path. The registration detail in identity_cost stays a default, not a page reading.
Evidence 5
datesourcewhat it proved
2026-10-21snapshot.debian.org/the text of Free tier, above
2026-11-03snapshot.debian.org/the archive holds 172 TB of Debian package data
2026-11-03snapshot.debian.org/the service is a read-only history of the Debian archive
2026-11-04snapshot.debian.org/the archive holds 172 TB of Debian package data
2026-11-04snapshot.debian.org/the service is a read-only history of the Debian archive with no upload path described
More fields 1
dead end{"failure_class": "quota","why": "Read-only ingest of the Debian archive; no user write path at any size. 172 TB is theirs, not yours.","retry_when": null,"first_recorded": "2026-10-21"}
Unknown values 7
  • chaining: no value was recorded for this field
  • egress terms: no value was recorded for this field
  • interface: the access interface was not established
  • per object cap notes: no value was recorded for this field
  • per object cap stated: no value was recorded for this field
  • retention stated: no value was recorded for this field
  • tooling: no value was recorded for this field

snapshot.debian.orgAcademicstorage/debian-snapshot-archiveJSONcomparereport an error

Free allowance
No user storage: snapshot is a read-only archive of the Debian package archives; the site news dated 2024-10-08 says it holds 172 TB.
Verdict
fails: quotathe free allowance is too small to matter
Cost
not stated
Identity
anonymousno card, no phone
Binding limit
noneno named constraint binds
Evidence
documented8 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
Free tierNo user storage: snapshot is a read-only archive of the Debian package archives; the site news dated 2024-10-08 says it holds 172 TB.
unit none; metered on none
Pricenone stated
Identityanonymous none: an unauthenticated HTTPS GET of /mr/timestamp/ returned HTTP 200; there is no write path to register for.
EgressFree, two sites (Glasklar + LeaseWeb). Netfilter rate limiting was explicitly disabled ('It will be replaced by rate limiting on the HTTP layer').
Per-object capnot stated
Retentionnot stated
Interfacerest, rclone rest
Toolingapt with a dated sources.list entry, debian-snapshot machine-usable API at /mr/ (e.g. /mr/timestamp/), plain HTTPS. No rclone backend.
Composes withNone - you cannot add content. Valuable only as a source of old Debian packages for a corpus, not as a place to put your data.
ReliabilityRead-only by construction. Included to close the category: Debian's snapshot is a preservation tool, not storage you can use. API verified live.
NotesNo user quota because there is no user write path - snapshot ingests the Debian archive itself. Scale reference from the site's own news: 'Snapshot is currently holding 172TB of data' (2024-10-08), up from 135 TB (2022) and 24 TB (2014), on 2 x 164 TB RAID6 arrays.
Evidence notedocumented The front page of snapshot.debian.org, re-read on 2026-11-03, says the archive holds 172 TB and describes a read-only history of old Debian packages; the unauthenticated GET of /mr/timestamp/ succeeded on the same date. The free-tier and identity fields cite those rows.
Evidence 8
datesourcewhat it proved
2026-10-21snapshot.debian.org/'Snapshot is currently holding 172TB of data'; 'The Netfilter rate limiting has been disabled ... rate limiting on the HTTP layer'
2026-10-21snapshot.debian.org/mr/timestamp/probe: GET -> 200 JSON, debian timestamps from 20050312T000000Z onward
2026-10-21source not publishedprobe: GET /archive/debian/20250101T000000Z/dists/bookworm/Release -> 302 (redirect to a dated snapshot; live)
2026-11-03snapshot.debian.org/the archive holds 172 TB; it is the service's own archive of Debian packages
2026-11-03probe: snapshot.debian.organ unauthenticated GET of /mr/timestamp/ returned HTTP 200 JSON
2026-11-03snapshot.debian.org/request limiting moved to the HTTP layer; no threshold is published
2026-11-04snapshot.debian.org/the archive holds 172 TB of Debian package data
2026-11-04snapshot.debian.org/the service is a read-only history of the Debian archive with no upload path described
More fields 1
dead end{"failure_class": "quota","why": "No user quota because there is no user write path - snapshot ingests the Debian archive itself. Scale reference from the site's own news: 'Snapshot is currently holding 172TB of data' (2024-10-08), up from 135 TB (2022) and 24 TB (2014), on 2 x 164 TB RAID6 arrays.","retry_when": null,"first_recorded": "2026-10-21"}
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