GitVerse

gitverse.ru · Storage · 3 records · JSON

GitVerse (Sber git hosting: LFS + releases + packages) Storagefails: quotaemail?card?Rper-object-cap
gitverse (gitverse.ru) Storagefails: quotaemail?card?R
sberdisk / gitverse (sber) Storagefails: quotaemail?card?R

GitVerse (Sber git hosting: LFS + releases + packages) Storage

fails: quotaemail?card?Rper-object-cap

gitverse.ru · paas · storage/gitverse · JSON · compare

Free tier	2 GB Git LFS per user AND per org (monthly), 4 GB release assets per user/org, 500 MB packages per user/org unit GB; metered on unstated
Price	none stated
Per-object cap	100 MB per file (100000000 bytes)
Retention	not stated
Egress	free clone/download from the platform, no egress billing published
Identity	email (placeholder) not published
Limits	per-object-cap 100 MB per file source 2 GB LFS/mo; 4 GB releases; 500 MB packages; 100 MB per file via HTTP, 1 GB via SSH; max 5 files and 500 MB per release upload batch
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	ssh, git git
Tooling	standard git + git-lfs over HTTPS/SSH; registries for npm, PyPI, Maven, Go, NuGet, Docker, Generic, Helm, deb, rpm
Composes with	caps are per user/org TOTAL, not per repo — unlimited repos x 4 GB does NOT multiply. Only new orgs/users do: 4 GB per org. 20 TiB would need 5 000 orgs.
Reliability	Hard global caps per identity with no top-up path; exceeding them blocks new uploads entirely rather than throttling. Quota stays with the original owner after repo transfer.
Notes	2 GB Git LFS per user AND per org (monthly), 4 GB release assets per user/org, 500 MB packages per user/org
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 100.0 MB

Evidence (3)

date	source	what it proved
2026-10-21	gitverse.ru/docs/limits-lfs-cicd/limits-lfs	'каждому пользователю и каждой организации предоставляется ежемесячный лимит хранения объемом 2 ГБ'
2026-10-21	gitverse.ru/docs/limits-lfs-cicd/limits-releases	'Суммарный лимит для релизов на пользователя или организацию составляет 4 ГБ', 'Максимальный размер одного файла — 100 Мбайт'
2026-10-21	gitverse.ru/docs/limits-lfs-cicd/limits-packages	'Суммарный лимит для пакетов на пользователя или организацию составляет 500 Мбайт'

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "2 GB Git LFS per user AND per org (monthly), 4 GB release assets per user/org, 500 MB packages per user/org",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (7)

$.extras.dead_end.retry_when process
$.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

gitverse (gitverse.ru) Storage

fails: quotaemail?card?R

gitverse.ru/docs/limits-lfs-cicd/limits-lfs · rejected-provider · storage/gitverse-2 · JSON · compare

Free tier	2 GB/month LFS storage per user AND per organization, 100 MB per file over HTTP, 1 GB per file over SSH. Too small, hard-capped, monthly. unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	2 GB/month LFS storage per user AND per organization, 100 MB per file over HTTP, 1 GB per file over SSH. Too small, hard-capped, monthly.
Notes	2 GB/month LFS storage per user AND per organization, 100 MB per file over HTTP, 1 GB per file over SSH. Too small, hard-capped, monthly.
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (1)

date	source	what it proved
2026-10-21	gitverse.ru/docs/limits-lfs-cicd/limits-lfs	2 GB/month LFS storage per user AND per organization, 100 MB per file over HTTP, 1 GB per file over SSH. Too small, hard-capped, monthly.

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "2 GB/month LFS storage per user AND per organization, 100 MB per file over HTTP, 1 GB per file over SSH. Too small, hard-capped, monthly.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (15)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded

sberdisk / gitverse (sber) Storage

fails: quotaemail?card?R

gitverse.ru/ · rejected-provider · storage/sberdisk-gitverse · JSON · compare

Free tier	Both authenticate through Sber ID, which is phone+SMS ('Введите свой номер телефона... или отсканируйте QR-код в приложении Сбербанк Онлайн'), and GitVerse's own sign-in endpoint answers 401 unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	Both authenticate through Sber ID, which is phone+SMS ('Введите свой номер телефона... или отсканируйте QR-код в приложении Сбербанк Онлайн'), and GitVerse's own sign-in endpoint answers 401
Notes	Both authenticate through Sber ID, which is phone+SMS ('Введите свой номер телефона... или отсканируйте QR-код в приложении Сбербанк Онлайн'), and GitVerse's own sign-in endpoint answers 401
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (2)

date	source	what it proved
2026-10-21	gitverse.ru/	Both authenticate through Sber ID, which is phone+SMS ('Введите свой номер телефона... или отсканируйте QR-код в приложении Сбербанк Онлайн'), and GitVerse's own sign-in endpoint answers 401
2026-10-21	disk.sber.ru/	cited as the basis of the rejection: Both authenticate through Sber ID, which is phone+SMS ('Введите свой номер телефона... или отсканируйте QR-код в приложении Сбербанк Онлайн'), and GitVerse's own sign-in endpoint answers 401

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "Both authenticate through Sber ID, which is phone+SMS ('Введите свой номер телефона... или отсканируйте QR-код в приложении Сбербанк Онлайн'), and GitVerse's own sign-in endpoint answers 401",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (15)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded