Plans and quotas
Preview plan limits, release artifact caps, and retention.
Sneka keeps preview quotas small so the service stays predictable while the product is still private. Quotas are enforced by the backend; UI labels are only guidance.
| Plan | Availability | Repositories | Release artifact | Release storage |
|---|---|---|---|---|
| Private preview | Invite only | 25 per user | 5 MiB | 100 MiB per user |
| Team preview | By arrangement | 100 per team | 5 MiB | 100 MiB per user |
| Future paid plans | Not yet sold | TBD | TBD | TBD |
Release Retention
Release storage uses first-in, first-out artifact expiration. If a new upload would push a user over the release storage limit, Diffinite expires the oldest active artifacts until the upload fits or rejects the upload if it still cannot fit.
Published release pages keep expired artifacts visible as expired rows rather than pretending a downloadable file still exists.
What Counts
Release artifact bytes count when an artifact upload succeeds. Bytes stop counting when an artifact is deleted from a draft release or expired by FIFO retention.
Checksums, signatures, notes, and changeset metadata do not count against the release artifact byte quota.
Errors
Uploads larger than the per-artifact cap fail with release_artifact_too_large. Uploads that cannot fit even after FIFO expiration fail with release_storage_exceeded.