How is Code Buckets different from a Git repository?
Code Buckets is organized storage for code, without repositories, branches or comment threads to manage.
| Code Buckets | A Git repository | |
|---|---|---|
| How code arrives | Upload a zip (or a single folder of the tree) | Commits and pushes |
| History | An events feed, code refs and backups | Commit history and branches |
| Discussion | None (events instead of comments) | Issues, reviews, comments |
| Large files | Assets up to 10 GB per bucket | Often limited |
| Encryption at rest | Per-bucket key, AES-256-GCM | Depends on the host |
Good fits for Code Buckets#
- Archiving releases, client handovers and build artefacts.
- Keeping assets and code together with backups.
- Letting scripts, CI or agents store and fetch code over a simple API.
Many teams use both: Git for day-to-day work, Code Buckets for snapshots, assets and archives.
Learn more#
Related articles
Still need help?
Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Infrastructure questions, or permanent deletion of your data
infrastructure@clatterlabs.xyzFor deleting your whole account or the data of one service.