Developer tools · Hybrid · unit: hosted CI minutes
GitLab pricing teardown: plan plus usage
Short answer
GitLab charges per user on paid plans, and hosted shared-runner workloads consume compute minutes; your own runners are treated differently.
Pricing mechanics
| Plan or rate | Position in ladder |
|---|---|
| Free | Entry |
| Premium | Paid step |
| Ultimate | Top published step |
- What the docs describe
- Paid plans charge per user and hosted shared-runner workloads use compute minutes. Own runners are treated differently.
- Free or trial fence
- A Free plan is listed; its compute-minute terms are on the linked page.
- Overage or upgrade rule
- Hosted shared-runner workloads consume compute minutes; purchase terms for more minutes are not stated in the summary used here — check the linked page.
- Cap or spend control (none stated)
- Not stated in the linked pricing documentation.
A feature or configuration fence (what a plan includes) is not the same as an abuse cap. We do not infer private costs, margins or unpublished limits.
Takeaway for founders
Distinguish the seat entitlement from infrastructure burn, and give heavy users a bring-your-own-capacity escape hatch.
Load into simulator
Illustrative remix · amounts and costs are editable.
Fictional tiers inspired by the pattern above. It does not reproduce GitLab's plans, invoices or margins. Fictional variable cost: $0.007 per hosted CI minute.
| Tier | Model | Price | Limit | Accounts |
|---|---|---|---|---|
| Sample entry | Flat / seat | $0 (free) | hard cap 100 hosted CI minutes | 200 |
| Sample growth | Hybrid | $24.00 base, 600 hosted CI minutes included, then $0.018 each | hard cap 4,000 hosted CI minutes | 70 |
| Sample scale | Hybrid | $89.00 base, 2,500 hosted CI minutes included, then $0.014 each | hard cap 20,000 hosted CI minutes | 15 |
Related guide: Hybrid vs. usage-based billing · All teardowns