Usage and add-ons

On instances that limit usage, your user account and each organization have their own limits for storage, CI time and download traffic. You can view your usage in your settings and raise some limits by buying add-ons. Which pages you see depends on what the administrator has turned on, and the limits and prices depend on the instance.

For an organization, the same pages are in the organization’s settings, and only its owners can open them. An organization’s usage and limits are its own, separate from those of its members.

See your usage

Storage and download traffic

Open Settings → Storage overview. It lists every quota rule that applies to you, with how much you use and the limit. Arbinel adds one row to Forgejo’s page.

• Monthly download traffic is what was downloaded from your account this month, such as packages, container images and Git LFS objects. It only appears when the instance limits download traffic. It resets at the start of each month, in UTC.

CI time is not on this page.

CI time

Open Settings → CI/CD usage. It covers the current month and shows:

• your CI time limits, each with a bar, and the date the usage resets,
• Minutes by CI engine, split between Forgejo Actions and any external CI system the instance accepts reports from, and by runner class,
• Minutes by day, a chart of the month,
• Minutes by repository, with the busiest repositories named and the rest under Other repositories.

The page counts only time on runners the instance provides. Jobs on runners you registered yourself are free and do not appear. Work that is still running is included in the total, with a note, and is added to the breakdown when it finishes.

Buy add-ons

When the instance sells add-ons, open Settings → Add-ons.

Current limits shows each limit an add-on can raise, with what you use, what is Included, what comes From add-ons, and the Total. Available add-ons lists the products for sale, the limits each one Raises, and its price per unit per month, including tax. Only add-ons that would raise one of your limits are offered.

To buy one:

1. Choose a Quantity under the add-on.
2. Select Buy. You go to Creem, the payment provider, to pay.
3. After paying, you come back to the Add-ons page. It shows “Waiting for Creem to confirm the payment…” and reloads once Creem confirms. If that takes longer than about half a minute, reload the page later.

The new limit applies as soon as the add-on appears under Your add-ons. A CI time add-on adds its amount every month. A storage add-on raises your storage limit for as long as you keep it.

For an organization, any owner can buy add-ons. The add-on shows who it is Billed to, and only that person sees it in Creem’s billing portal.

Change or cancel an add-on

Under Your add-ons:

• Change quantity changes the number of units. Creem prorates the difference for the current billing period, and lowering the quantity refunds the unused part.
• Cancel subscription stops the add-on from renewing. It keeps working until the end of the paid period. A paused add-on ends at once.
• Manage billing opens Creem’s portal, for invoices and payment details.

If a payment fails, the add-on shows “A payment failed and Creem is retrying it.” It keeps working while Creem retries.

Every owner of an organization can cancel its add-ons, not only the one who bought them.

Bandwidth

Some instances sell extra download traffic as Bandwidth, billed by use rather than by units. The card shows how much you downloaded this month against the free amount.

To set it up, select Add bandwidth, and enter:

• a Billing e-mail, which receives the invoices. It must be one of your verified addresses. For an organization it must be a verified address other than your primary one.
• a Monthly limit, in money, excluding VAT. Downloads above the free amount are billed until they reach this limit, and downloads stop when it is reached.

You pay only for traffic above the free amount, up to your monthly limit. Small amounts are collected until they reach a minimum charge, or until bandwidth ends. Change the limit with Save limit, and the e-mail with Save e-mail.

Reaching a limit

What happens depends on the limit.

Limit	What happens
Storage	New pushes, uploads, releases and similar writes are refused. What you already have stays available. Delete something, or buy more storage. An operation that has started finishes, so you can end up slightly above the limit.
CI time	Jobs that would run on the instance’s runners are cancelled before they start, and the run shows a banner naming the limit. Jobs that are already running finish. Jobs on your own runners still run. Rerun the cancelled jobs once the limit resets at the start of the month or is raised.
Download traffic	Downloads of packages, container images and LFS objects are refused until the month resets or the limit is raised. Pushes and the web interface keep working.

When an add-on can raise the limit, the error page or run banner points you to the Add-ons tab.

The instance may also mail you when you reach a percentage of a limit, by default at 80% and 100%. For an organization, the mail goes to every member of its Owners team.

Delete an account with add-ons

You cannot delete an account or organization while Creem still bills add-ons it owns, or add-ons you bought for an organization. Cancel them first. Deletion works once they have ended, at the end of the paid period. Bandwidth needs up to two more days after it ends, to bill the last downloads.