{"eid":"opencsg","name":"OpenCSG 传神社区","domain":"opencsg.com","resolved_by":"domain","topics":["storage"],"n_records":1,"best_vorder":1,"review":null,"aliases":["OpenCSG 传神社区","OpenCSG 传神社区 (CSGHub SaaS, opencsg.com / hub.opencsg.com)","opencsg.com"],"records":[{"rid":"storage/opencsg","card":{"rid":"storage/opencsg","eid":"opencsg","topic":"storage","slug":"opencsg","provider":"OpenCSG 传神社区 (CSGHub SaaS, opencsg.com / hub.opencsg.com)","url":"https://opencsg.com","domain":"opencsg.com","category":"model-hub","tier":null,"verdict":"qualifies-with-caveat","vorder":1,"grp":"usable","confidence":"documented","binding":"retention-clamped","identity_kind":"national-id","identity_basis":"stated","needs_card":0,"needs_phone":1,"needs_id":1,"needs_institution":0,"country":null,"crypto":null,"interfaces":"rest,git,rclone,cli","egress_metered":0,"per_object_bytes":null,"retention_days":3,"verified_at":"2026-10-22T00:00:00.000Z","verified_basis":"inherited","checked_on":"2026-10-21","stale_on":"2026-11-20","n_evidence":8,"usd_month":null,"usd_per_tb_month":null,"summary":"No published byte quota anywhere in the docs — and this is deliberate: the upload page states verbatim '上传大小和超时限制由站点、代理和存储配置决定' (upload size and timeout limi...","duplicate_of":null,"n_unknown":5},"record":{"topic":"storage","slug":"opencsg","provider":"OpenCSG 传神社区 (CSGHub SaaS, opencsg.com / hub.opencsg.com)","url":"https://opencsg.com","category":"model-hub","free_tier":{"stated":"No published byte quota anywhere in the docs — and this is deliberate: the upload page states verbatim '上传大小和超时限制由站点、代理和存储配置决定' (upload size and timeout limits are determined by the site, proxy and storage configuration) and explicitly warns '不要把站点限制理解为 Git LFS 协议的统一上限' (do not read a site limit as a universal Git LFS protocol ceiling). What is measurable instead is what they actually host: the canonical deepseek-ai/DeepSeek-V3 repo is 176 files totalling 688.6 GB, of which 163 are shards above 1 GB. That is a single repo at 0.69 TB, i.e. the repo-level ceiling is at minimum ~700 GB and is shard-driven, not quota-driven.","unit":"objects","metered_on":"stored-bytes","source_url":"https://www.opencsg.com/docs/model/upload_models","read_on":"2026-10-21","notes":null},"per_object_cap":{"stated":"not stated","source_url":"https://www.opencsg.com/docs/model/upload_models","notes":"not stated"},"retention":{"stated":"(b) Presigned OSS URLs carry X-Amz-Expires=259200 — 72 hours, so re-resolve per request rather than caching a URL (§1b's expiring-redirect rule)","days":3,"source_url":"https://www.opencsg.com/docs/model/upload_models","notes":"not stated"},"egress":{"terms":"Free and unmetered. Reads are served from opencsg-gitea-lfs-new.oss-cn-beijing.aliyuncs.com (Alibaba Cloud OSS, Beijing) via presigned URLs; no per-GB line, no egress meter, no bandwidth charge appears in any billing doc. The only billing surface is the AI gateway (Token spend), not bytes.","metered":false},"interface":["rest","git","rclone","cli"],"interface_detail":"git","tooling":"Three real clients, all first-party: (1) git + git-lfs against https://opencsg.com/models/<ns>/<repo>.git; (2) csghub-sdk / csghub-cli (pip install csghub-sdk), with `csghub-cli upload-large-folder` purpose-built for multi-GB model trees; (3) a documented REST API at hub.opencsg.com/api/v1 (models, tree, branches, last_commit all return JSON). The whole platform is open source: github.com/OpenCSGs/csghub (4,071 stars) and csghub-server (1,039 stars), so the server-side quota logic is auditable. No rclone backend.","chaining":"Repos are free and unlimited per account, so capacity is N repos x per-repo size with no account total. A 10 TiB hot working set = ~15 repos the size of DeepSeek-V3. Accounts are self-service (username/password + phone + email) and orgs are free, so account multiplication is available on top. Critically, CSGHub ships an XNet storage backend with chunk-level dedup and '秒传' instant-upload, which means re-uploading a dataset that already exists removes bytes entirely — the marginal cost of a fork or a version is near zero.","limits":[{"kind":"per-ip-shaping","value":"2.70 MB/s","source":"https://www.opencsg.com/docs/model/upload_models"},{"kind":"per-ip-shaping","value":"1.16 MB/s","source":"https://www.opencsg.com/docs/model/upload_models"},{"kind":"retention-clamped","value":"Expires=259200 — 72 hours","source":"https://www.opencsg.com/docs/model/upload_models"}],"limits_note":"The real limits measured live, not documented: (a) the plain resolve path is NOT the download path — https://hub.opencsg.com/models/Qwen/Qwen3-8B/resolve/main/model-00001-of-00005.safetensors returns HTTP 200 with a 135-byte Git-LFS pointer (Content-Type: text/plain), which is exactly the round-2 'status-code theatre' trap. You must POST the LFS batch endpoint to get bytes. (b) Presigned OSS URLs carry X-Amz-Expires=259200 — 72 hours, so re-resolve per request rather than caching a URL (§1b's expiring-redirect rule). (c) Per-stream shaping is severe: 2.70 MB/s on one connection (16 MiB in 6.2 s) and 1.16 MB/s on a 32 MiB pull; 8 parallel ranged GETs reached 14.49 MB/s and 15.50 MB/s across two separate tests. That is near-linear scaling (5.4x at 8 streams), i.e. it is per-connection shaping, not an aggregate cap — the same shape as Zenodo. (d) No documented upload-bytes/day cap, no retention/expiry on repos, no pull-count limit observed.","identity_cost":{"kind":"national-id","detail":"email + any phone + password. Docs state registration collects 'username, password, phone number, and email'. No national-ID or card requirement documented for the SaaS.","country":null},"reliability_note":"Reads depend on Alibaba OSS presigned URLs, so a URL cached for more than 72 h silently dies (301/0-byte) — resolve-then-fan-out within the window. No observed rate limit on the anonymous LFS batch endpoint. Data does not expire; repos have branches and commit history, so it is mutable rather than an archive.","confidence":"documented","confidence_note":"The object cap and the repository total were recomputed from the live tree API. Was reported; now documented.","evidence":[{"url":"https://hub.opencsg.com/api/v1/models/deepseek-ai/DeepSeek-V3/tree","date":"2026-10-21","proved":"probe: GET -> 200, 176 files, summed size 688.6 GB, 163 shards >1 GB (largest 5.2 GB)"},{"url":"https://hub.opencsg.com/models/Qwen/Qwen3-8B.git/info/lfs/objects/batch","date":"2026-10-21","proved":"probe: POST with {operation:download} -> 200, JSON containing actions.download.href to opencsg-gitea-lfs-new.oss-cn-beijing.aliyuncs.com with X-Amz-Expires=259200 — anonymous, no token required"},{"url":"https://hub.opencsg.com/models/Qwen/Qwen3-8B/resolve/main/model-00001-of-00005.safetensors","date":"2026-10-21","proved":"probe: GET -> HTTP 200 but Content-Length 135, body is a git-lfs pointer ('version https://git-lfs.github.com/spec/v1 / oid sha256:...'). The 200 is not a file transfer."},{"url":null,"date":"2026-10-21","proved":"probe: 1 ranged GET 16 MiB -> 206, 2,701,748 B/s. 8 parallel 8 MiB ranged GETs -> 14.49 MB/s aggregate; repeat on the 5.2 GB DeepSeek-V3 shard -> 15.50 MB/s aggregate"},{"url":"https://www.opencsg.com/docs/model/upload_models","date":"2026-10-21","proved":"read live: '上传大小和超时限制由站点、代理和存储配置决定 ... 不要把站点限制理解为 Git LFS 协议的统一上限' (no published quota; limits are site-config)"},{"url":"https://www.opencsg.com/docs/csghub/101/introduction","date":"2026-10-21","proved":"read live: 'XNet 智能块加速引擎支持切块去重、秒级增量更新与并行下载 ... 整合 Git Server、Git LFS 与对象存储 OSS'"},{"url":"https://github.com/OpenCSGs/csghub","date":"2026-10-21","proved":"4,071 stars, self-hostable CSGHub CE (so the same stack can be run on your own box)"},{"url":"probe:https://hub.opencsg.com/api/v1/models/deepseek-ai/DeepSeek-V3/tree","date":"2026-10-22","proved":"GET 2026-10-22: 200, 150,045 B; 176 files, 688,603,604,082 B total, 163 shards over 1 GB, largest 6,584,784,447 B"}],"verdict":"qualifies-with-caveat","verified_at":"2026-10-22T00:00:00.000Z","notes":"No published byte quota anywhere in the docs — and this is deliberate: the upload page states verbatim '上传大小和超时限制由站点、代理和存储配置决定' (upload size and timeout limits are determined by the site, proxy and storage configuration) and explicitly warns '不要把站点限制理解为 Git LFS 协议的统一上限' (do not read a site limit as a universal Git LFS protocol ceiling). What is measurable instead is what they actually host: the canonical deepseek-ai/DeepSeek-V3 repo is 176 files totalling 688.6 GB, of which 163 are shards above 1 GB. That is a single repo at 0.69 TB, i.e. the repo-level ceiling is at minimum ~700 GB and is shard-driven, not quota-driven.","extras":{},"binding":"retention-clamped","binding_note":"a clock, not a quota: bytes leave whether or not the client is finished with them"},"claims":[{"path":"$.free_tier.stated","kind":"free-quota","num":688.6,"unit":"GB","per":null,"currency":null,"usd":null,"fx_date":null,"parse":"ok"},{"path":"$.limits[0].value","kind":"limit:per-ip-shaping","num":2.7,"unit":"MB","per":null,"currency":null,"usd":null,"fx_date":null,"parse":"ok"},{"path":"$.limits[1].value","kind":"limit:per-ip-shaping","num":1.16,"unit":"MB","per":null,"currency":null,"usd":null,"fx_date":null,"parse":"ok"},{"path":"$.limits[2].value","kind":"limit:retention-clamped","num":72.0,"unit":"hours","per":null,"currency":null,"usd":null,"fx_date":null,"parse":"ok"}],"unknown":[["$.evidence[3].url","private-url"],["$.free_tier.notes","process"],["$.per_object_cap.notes","not-extracted"],["$.per_object_cap.stated","not-extracted"],["$.retention.notes","not-extracted"]],"history":[],"drift":[]}]}