Plan limits
This page is the reference for how each limit behaves. For the wider billing picture (top-ups, refunds, VAT), see billing. For how minutes are metered as jobs run, see CI runners.
What each plan includes
Section titled “What each plan includes”Personal
Section titled “Personal”| Personal | |
|---|---|
| Base (monthly) | €7/month |
| Storage included | 5 GiB |
| Hosted CI | No |
| BYO runners | Yes |
Personal plan users can run CI via BYO runners or external CI systems. No hosted CI, no concurrency slots, no top-ups.
Organization
Section titled “Organization”| Starter | Team | Scale | |
|---|---|---|---|
| Base (monthly) | €19/month | €49/month | €99/month |
| Storage included | 25 GiB | 200 GiB | 500 GiB |
| Hosted CI included | 3,000 min | 10,000 min | 25,000 min |
| Concurrent CI jobs | 1 | 3 | 6 |
Every plan includes private repos, the container registry, daily encrypted backups, and bring-your-own-runner support. Organization plans also include unlimited users and any hosted runner size (codebahn-small, codebahn-medium, codebahn-large); larger runners consume included minutes faster via their cost factor. Annual prepay is 17% off the base fee; usage is always billed monthly.
Behavior at the limit
Section titled “Behavior at the limit”| Resource | Type | What happens |
|---|---|---|
| Compute minutes | Hard cap | New jobs are denied with a “CI is paused” message. A running job is stopped if it goes 30 minutes past the cap. |
| Storage | Soft overage | You are not cut off. Overage is billed per GiB at the end of the billing period. |
| Concurrency | Hard cap | Jobs above your concurrency limit queue until a slot opens. |
Compute minutes and concurrency apply to organization plans only. The Personal plan has storage limits but no hosted CI.
The two hard caps behave differently. The compute-minute cap denies new jobs. The concurrency cap queues them. Don’t confuse the two.
Compute minutes
Section titled “Compute minutes”This section applies to organization plans. The Personal plan does not include hosted CI or compute minutes.
Compute minutes are wall-clock time multiplied by the runner’s cost factor, summed across your jobs for the billing period. A 5-minute job on codebahn-medium (2x) uses 10 compute minutes. See CI runners for the full size and cost-factor table. Plan minutes drain first; top-up minutes are used only once plan minutes are gone.
When you run out of both:
- A job already running keeps going, but is stopped if it runs more than 30 minutes past the cap.
- New jobs are denied immediately with a “CI is paused” message. They do not queue.
- To continue, buy a top-up or wait for the next billing period, then re-run the denied jobs. They do not resume on their own.
Top-up minutes cost €5 per 1,000 minutes, are added to your pool immediately, and persist until used. They do not expire at period end.
Storage
Section titled “Storage”Storage is the total size of everything you keep on Codebahn:
- Git repositories (objects, refs, pack files)
- Git LFS objects
- CI artifacts (expired artifacts are excluded)
- Packages (container registry, npm, Maven, and others)
- Attachments (issue, PR, and release uploads)
Usage is measured daily. Your overage is based on the monthly average, not a peak. There is no hard cut-off. When you exceed your plan’s included storage:
- Overage is billed at €0.10/GiB/month across all tiers, rounded up to the nearest GiB. Our infra cost is around €0.05/GiB; the difference covers backups, monitoring, and ops.
- Charges under €1 in a month roll forward and are added to the next month’s bill.
- After three consecutive months in overage, you get a notice suggesting a plan upgrade.
Concurrency
Section titled “Concurrency”Each organization plan includes a fixed number of concurrent CI job slots (1, 3, or 6). Jobs beyond that limit queue in order and start when a slot opens. The limit applies across every repository in your account or organization.
Next: set up CI or read the full billing reference.