Plan limits

Each Codebahn plan includes a set amount of resources. See codebahn.net for current plan details and pricing.

Behaviour at the limit

Resource	Type	What happens
CI minutes	Hard cap	New jobs queue. Jobs already running get a 30-minute grace window to finish.
Storage	Soft overage	You are not cut off. Overage is billed per GB at the end of the billing period.
Concurrency	Hard cap	Jobs above your concurrency limit queue until a slot opens.

CI minutes in detail

Minutes are wall-clock time per job, rounded up to the nearest minute.

When you reach your allocation:

• Jobs currently running are allowed to finish (grace window: 30 minutes).
• New jobs enter a queue.
• The queue clears when the next billing period starts or when you purchase a top-up.

Top-up minutes are added to your pool immediately and persist until used. They do not expire at period end.

Warnings

You receive email notifications at 80% and 95% of your minute allocation. These give you time to purchase a top-up before builds start queuing.

Storage in detail

There is no hard cut-off for storage. When you exceed your plan’s included storage:

• Overage is calculated at the end of the billing period.
• The per-GB overage rate depends on your plan tier (higher tiers have lower overage rates).
• If you remain in overage for three consecutive months, you receive a notice suggesting a plan upgrade.

Concurrency

Each plan includes a set number of concurrent CI job slots. Jobs beyond your concurrency limit queue in order and start when a slot becomes available. Concurrency limits apply across all repositories in your organisation.