fshy

Home / Storage

JitPack (jitpack.io) - build-on-demand Maven from git

jitpack.ioRegistrystorage/jitpack-build-on-demand-maven-from-gitJSONcomparereport an errorprovider JSON

Free allowance
Bounded by the size of the git repo it builds from, not by a storage quota: a build fails with 'Git error.
Verdict
fails: quotathe free allowance is too small to matter
Cost
free tier
Identity
institution?placeholder, not evidence; card unknown, phone unknown
Binding limit
per-object-capper-object-cap: 250 MB
Evidence
reported3 sources; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierBounded by the size of the git repo it builds from, not by a storage quota: a build fails with 'Git error. Max repo size 250MB exceeded'. JitPack builds any public git repo on demand and serves the resulting Maven artifacts at com.github.<user>.<repo>:<tag>.
unit mixed; metered on stored-bytes
Pricenone stated
Limits
  • per-object-cap (binding) per-object-cap: 250 MB source
per-object-cap: 250 MB repo size (hard build error). request-rate: builds are queued per-IP (anonymous builds are rate limited; the API exposes per-tag build state). retention: build artifacts are cached but a failing/expired build is rebuilt on demand - not durable storage.
Identityinstitution (inferred, not read) not published
EgressFree. Artifacts served from jitpack.io CDN with no billing.
Per-object capper-object-cap: 250 MB (250000000 bytes)
Retentionnot stated
Interfacerest, rclone, cli rest
ToolingAny Maven/Gradle resolver pointed at https://jitpack.io; JitPack build API at /api/builds/<group>/<artifact> (open, returns build status per tag). No dedicated CLI beyond Maven/Gradle; no rclone backend.
Composes withunlimited public git repos x unlimited tags/commits x 250 MB repo each. Because artifacts are derived, storage is the repo's, and the same content is rebuilt per tag - so it amplifies, it does not multiply storage. 250 MB x N repos is the honest ceiling.
ReliabilityBuild service, not storage: artifacts can be evicted and rebuilt, and repo size is hard-capped at 250 MB. Read path live and public (verified /api/builds/com.github.jitpack/maven-simple returning ok states across dozens of tags).
Parsed numbers
  • has-free-tier 1
  • per-object-cap 250 MB
Evidence 3
datesourcewhat it proved
2026-10-21github.com/jitpack/jitpack.io/issues/4898'Build issue Max repo size 250MB exceeded'; 'Git error. Max repo size 250MB exceeded'
2026-10-21jitpack.io/api/builds/com.github.jitpack/maven-simpleprobe: GET -> 200 JSON, dozens of tag/commit entries with status 'ok'
2026-10-21docs.jitpack.io/building/build-on-demand model
More fields 1
dead end{"failure_class": "quota","why": "Bounded by the size of the git repo it builds from, not by a storage quota: a build fails with 'Git error. Max repo size 250MB exceeded'. JitPack builds any public git repo on demand and serves the resulting Maven artifacts at com.github.<user>.<repo>:<tag>.","retry_when": null,"first_recorded": "2026-10-21"}
Unknown values 3
  • 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
  • retention stated: the field may be stated in a source that was not read