Fair use and retention policy
Version 1.0, effective 18 September 2026. How we keep free hosting free: limits, inactivity, and what happens to dormant projects.
Limits for free accounts
- Up to 3 projects per account.
- Up to 1.0 GB per project (repository, LFS, artifacts and uploads together). At 1 GB you get a warning; above 2 GB the project is archived until it is cleaned up.
- Pushes are limited to 100 MB at a time; attachments to 10 MB.
- CI on shared runners: 1 vCPU and 1 GB of memory per job, one hour per job, artifacts kept for 7 days. Runners are shared; heavy or abusive pipelines are stopped.
- No permanent free compute. Anything that needs to run continuously belongs on a Cloud plan.
Inactivity
A project counts as active when there is a push, merge request, issue or other repository activity, or when one of its owners or maintainers signs in.
| After | Private projects | Public projects |
|---|---|---|
| 5 months without activity | Warning e-mail to all owners and maintainers | Warning e-mail at 11 months |
| 6 months | Project archived: read-only, still visible and cloneable | Archived at 12 months |
| 30 days after archiving | Permanent deletion, unless the project was reactivated. Deletion is announced in the archiving e-mail. | |
Reactivating is simple: sign in, or unarchive the project from its settings, or push a commit. Public open-source projects that should stay online without activity can ask for an exemption by e-mail; we mark them and they are left alone.
Backups and deletion
We keep encrypted backups for disaster recovery: daily for 7 days, weekly for 4 weeks, monthly for 6 months. A deleted project therefore disappears from backups within 6 months at most. Backups are never used to restore individual projects on request.
Cloud servers
Paid servers are not subject to inactivity rules. They are destroyed at the end of the paid period after a cancellation or after 7 days of failed payment, together with their disks.