GitLab self-managed total cost calculator

Budget self-managed GitLab with upstream licences, CI runners, artifacts, repositories, backups and the operation that hosting does not remove.

Last updated

In short

  • Self-managed GitLab can retain per-user upstream licence fees.
  • CI runner capacity is a separate workload from the GitLab application.
  • A low-cost GitHub plan may remain cheaper when its included features meet the need.
On this page (5)

Costs and savings · Part of GitLab

Interactive worksheet · no sign-up

Estimate GitLab Self-Managed costs

Use the same currency and scope for both options. Inputs stay in this page; they are not included in analytics or sent with an enquiry.

1. Your current bill
2. The replacement

Business management: CHF 1,590/month for up to 3 apps; onboarding from CHF 9,900. Infrastructure and paid licences are extra.

Build runner usage

Include concurrency and idle machines in the infrastructure quote; do not charge the same runner twice.

Additional billable backup storage

Include copies and retention. Enter only costs outside the infrastructure quote and Pilae plan.

Compare the same GitLab tier and support level. A move from a paid SaaS tier to Free changes features as well as hosting.

3. Transition and overlap
Optional: value internal operating time

Time released is capacity, not automatically payroll or cash saved. Keep time already billed by Pilae or another supplier out of these fields.

How the calculation works
  1. Current monthly invoices = billed units × unit price + additional current spend.
  2. Replacement monthly invoices = Pilae management + additional infrastructure + target licences + workload usage + retained services.
  3. Transition = plan onboarding + new hardware + extra migration + training + parallel months × max(0, current invoices − retained services). Parallel months are capped at the comparison horizon.
  4. Total invoices = monthly invoices × horizon, plus transition for the replacement. Payback uses the full transition commitment divided by positive monthly invoice saving, including all entered overlap months even beyond the selected horizon.
  5. Economic saving adds the change in valued internal operating time. It does not assume headcount reduction.

Business includes up to 3 apps, then a published per-app fee (CHF 390 in CHF). Starter’s published CHF price is CHF 449/month. All Pilae figures come from the same price data as the pricing page. Workload inputs are your estimates, not supplier quotes. Taxes, price growth, discount rates, opportunity costs and differences in functionality are outside this arithmetic.

GitLab self-managed cost is the sum of the selected edition, the application platform, build execution and the people who operate them. Moving onto your infrastructure changes control and responsibility; it does not automatically remove GitLab licence charges or replace every GitHub feature.

Separate the application from CI

Cost area Measure Frequent omission
GitLab edition Required users and capabilities Paid features remain paid when self-managed
Application service Peak API/web/Git load Database, repository and cache components
CI execution Jobs, duration, concurrency and hardware type Idle runners and burst capacity
Stored data Repositories, LFS, artifacts, packages and registry Retention and recovery copies
Security Runner isolation and secrets handling Separate environments for untrusted jobs
Operation Upgrade cadence, incident coverage and recovery Testing and maintenance work

The current GitLab pricing identifies edition boundaries. Select features first, then enter the applicable licence quote; do not compare a paid source plan with a free target that lacks the required governance.

Size from load rather than seats alone

GitLab’s reference architectures are starting points for production designs, with expected load and deployment assumptions. Registered users are only a proxy. Automation, monorepositories, integrations and frequent cloning can materially affect the service even when the human team is small.

CI runners deserve their own calculation. As an illustrative workload, 200 pipelines a day using eight runner-minutes each consume 1,600 runner-minutes, or about 26.7 active runner-hours a day. That says nothing yet about simultaneous jobs, idle reservation, GPU jobs or weekend scheduling. Use actual pipeline history to quote those separately.

Count data with a retention policy

Artifacts that expire after a week and release packages kept indefinitely create different storage obligations. Inventory repositories, LFS objects, registries, package storage and logs. Agree which copies are authoritative and how recovery is tested.

The backup documentation covers several data components and restore requirements. A backup scope must match the actual installation; object storage and secrets should not be assumed covered by one generic archive. Record restore prerequisites and verify the exact version/edition path before accepting a recovery plan.

Compare to the real source bill

GitHub Free or Team can be an economical choice for a modest team. A move may be justified by private infrastructure, workflow control or operational requirements even when it increases expenditure. Keep hosted CI, security scanning or other services in the model if they remain in use.

The calculator combines the service basis from Pilae pricing with the infrastructure, licence and migration inputs you provide. Show first-year cash separately from recurring charges. If hardware is already owned, record its incremental cost and full replacement cost as different views.

Budget the migration and prove its scope

Before quoting the move, inventory repositories, issues, merge/pull requests, CI secrets, webhooks, registry data and identities. Some workflows require redesign rather than import. A representative rehearsal should check permissions, branch protections, build results and package access, not merely count repositories.

Use isolated runners and test an untrusted change without exposing production secrets. Keep the source service available until reconciliation and rollback conditions are met. The GitHub migration guide addresses that source; GitLab.com to self-managed is a different path. Both should finish with a clear list of subscriptions and services that can actually be discontinued.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Review our GitLab budget

Bring your current bill, required capabilities and workload assumptions. We will separate recurring operation from migration and retained services.