Forgejo operating cost calculator

Estimate Forgejo costs from repositories, LFS, CI runners, packages, backups, migration and the support that a lightweight forge still needs.

Last updated

In short

  • A lightweight Git forge does not make CI execution or storage free.
  • Required GitHub or GitLab services may remain after repositories move.
  • Recovery must include configuration, database, repositories and external dependencies.
On this page (5)

Costs and savings · Part of Forgejo

Interactive worksheet · no sign-up

Estimate Forgejo source control 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.

Review branch protections, identity, audit and code-security requirements. Rebuilding CI and losing a required security feature are not savings.

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.

Forgejo can provide a focused, owned Git service without buying a large development-platform suite. Its total cost still includes infrastructure, build execution, storage, recovery and operation. The calculator is most useful after deciding which development workflows actually move.

Separate Git hosting from the development estate

Function Count or verify Possible retained cost
Repositories Size, count, activity and permissions Mirrors or source-host access
Large files LFS volume and transfer Storage and bandwidth
CI jobs Runner type, duration and peaks Compute and external CI services
Packages Registries, artifacts and retention Storage and scanning tools
Governance Reviews, identity and audit needs Separate controls or services
Integrations Webhooks, bots and release automation Rebuild and ongoing maintenance

Do not credit a migration with the whole GitHub or GitLab bill when code scanning, hosted runners or another required feature stays there. For a small team, an inexpensive hosted Git plan may be cheaper even before private infrastructure and operation are added.

Build a runner budget from pipeline history

Forgejo Actions documentation describes workflows and their security boundaries. Review compatibility rather than assuming every existing workflow runs unchanged. Actions that use untrusted code, privileged access or deployment secrets need an explicit isolation design.

As an illustrative workload, sixty jobs a day at twelve minutes each use twelve active runner-hours. A permanently reserved runner can be billed for far more time than that. Several simultaneous jobs may require additional capacity even when the daily total is small. Include idle reservation, cache storage and any specialized hardware.

A runner is also an entry point into the systems its credentials reach. Cheap consolidation is not a reason to let untrusted pull requests share secrets with production deployment jobs.

Budget storage and recovery coherently

Repositories are only one part of the service. Account for the database, configuration, LFS, attachments, packages and runner-related data as applicable. Agree what must be recovered and what can be rebuilt.

The upgrade guidance emphasizes a recoverable state before changing versions. Record the application version and database state together, and test the restore before relying on it. Discovering an upgrade problem after several days of new writes makes a simple rollback much harder.

A financial example with retained services

Suppose an existing development subscription costs 700 units monthly. The proposed forge operation and infrastructure cost 650, but 180 of scanning and runner services remain. The replacement costs 130 more each month before migration. These are hypothetical inputs, not vendor prices. The result could still be justified by infrastructure ownership, but it must not be described as a subscription saving.

Conversely, an already operated estate with spare capacity may have a lower incremental cost for another forge. Show the shared-cost allocation rather than calling the existing service free. Use Pilae pricing and the actual runner/infrastructure scope in the live model.

Validate the move before cancelling anything

Test repository access, branch protection, review flow, CI output, packages and a release. Reconcile issue and review history where the chosen migration path supports it. Document objects that remain as a read-only archive or require manual rebuilding.

Define the source of truth during the parallel period and how new commits or issues would be reconciled if the cutover is reversed. The GitHub migration guide and Bitbucket guide address different export paths. Bring representative pipelines and current service bills so that the cost review follows the actual development workflow.

Sources and further reading

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

Scope a managed Git forge

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