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”| Solo | |
|---|---|
| Base (monthly) | €9/month |
| Base (annual) | €90/year (save 2 months) |
| Storage included | 2 GiB git + 50 GiB objects |
| CI minutes included | 200/month |
| Hosted CI | 1 concurrent job |
| BYO runners | Yes |
Solo includes 200 CI minutes per month with 1 concurrent job. Top-up packs (€9 per 1,000 minutes) are available for additional minutes. BYO runners and external CI systems also work.
| Crew | |
|---|---|
| Per seat (monthly) | €9/seat/month |
| Team (monthly) | €10/month |
| Annual | €90/seat/year + €100/year team (save 2 months) |
| Hosted CI included | 1,000 min/month per seat (pooled) |
| Builds a day (approx) | 5 |
| Concurrent CI jobs | 2 (1-5 members), 4 (6-15), 8 (16+) |
| Storage included | 2 GiB git + 50 GiB objects per seat |
| BYO runners | Yes |
| Solo included | Yes |
Build counts assume a five-minute build on codebahn-small; minutes are the limit. Every plan includes private repos, the container registry, daily encrypted backups, and bring-your-own-runner support. Every Crew member gets a personal Solo plan at no extra charge; see billing for details. Crew plans include any hosted runner size (codebahn-small, codebahn-medium, codebahn-large); larger runners consume included minutes faster via their cost factor. 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 all plans with hosted CI. Solo includes 200 minutes per month. Crew includes 1,000 minutes per seat per month, pooled across the organization. Both plans can buy top-up packs for additional minutes.
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 all plans with hosted CI. Solo includes 200 minutes per month. Crew includes 1,000 minutes per seat per month, pooled across the organization. Top-up packs are available on both plans for additional minutes.
Each job’s wall-clock time is rounded up to a whole minute, then multiplied by the runner’s cost factor. Compute minutes are the sum across your jobs for the billing period. A 5-minute job on codebahn-medium (2x) uses 10 compute minutes; a 20-second job on the same runner uses 2. 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 €9 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, split across two pools with separate caps: 2 GiB for git, 50 GiB for objects.
| Category | Pool |
|---|---|
| Git repositories (objects, refs, pack files) | git |
| Git LFS objects | objects |
| CI artifacts (expired artifacts are excluded) | objects |
| Packages (container registry, npm, Maven, and others) | objects |
| Attachments (issue, PR, and release uploads) | objects |
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 plan includes a fixed number of concurrent CI job slots. Solo gets 1. Crew scales with seats: 2 jobs for 1-5 seats, 4 for 6-15, 8 for 16 or more. Jobs beyond the limit queue in order and start when a slot opens. The limit applies across every repository in your account or organization.