3-year cost calculator
Pre-filled for Azure DevOps → Gitea / Forgejo. Adjust every figure with your own numbers.
Every figure here is an illustrative estimate, not a vendor quote. Defaults are editable starting points compiled from public information; real, binding pricing comes from the vendor or an authorized distributor. See our methodology.
All figures are illustrative and fully editable — adjust the cost-per-user and migration inputs with your own numbers. Not guaranteed vendor pricing (defaults reviewed May 2026). For a binding quote, use the request form below to reach an authorized distributor or partner.
Quick comparison: Azure DevOps vs Gitea / Forgejo
Common trade-offs teams weigh when staying on Azure DevOps versus moving to Gitea / Forgejo. These are general, commonly-reported considerations — not statements of fact about any vendor — so check them against your own contract and the vendors' current terms.
- Already in production — no migration effort or risk
- Mature ecosystem with vendor support and SLAs
- Per-user licensing plus parallel-job costs
- Tied to the Microsoft ecosystem
- Hosted-agent minutes billed separately
- Ongoing per-user + pipelines cost to budget for
- Open source — no license fees
- No vendor lock-in
- Cost model: Free (self-hosted)
- Requires a migration (~15 weeks, medium effort)
- Community support by default — paid support optional
Why teams evaluate alternatives to Azure DevOps
Reasons commonly cited by users and in public industry coverage for re-evaluating Azure DevOps. These are general, reported considerations — not statements of fact about Microsoft — and may not reflect your situation or the vendor's current terms. Verify against your own contract before deciding.
- Per-user licensing plus parallel-job costs
- Tied to the Microsoft ecosystem
- Hosted-agent minutes billed separately
The migration plan
Roughly 15 weeks for a mid-size estate, in six phases.
Tooling & automation
Migrate repos and pipelines; convert YAML pipelines to the new CI; move work items via API; re-point service connections; staged cutover.
OffVendor's wizard pre-fills these scripts with your environment — inventory export, disk/schema conversion, bulk provisioning, and validation.
Frequently asked
Is migrating from Azure DevOps to Gitea / Forgejo worth it?
For most teams facing rising Azure DevOps costs, yes — Gitea / Forgejo (free (self-hosted)) typically lowers 3-year total cost of ownership, though the right answer depends on workload complexity and in-house skills. Use the calculator to model your own numbers.
How long does a Azure DevOps to Gitea / Forgejo migration take?
A typical mid-size estimate is around 15 weeks across six phases — discovery, design, pilot, waved production migration, validation, and decommission. Larger or more complex estates take longer.
What tools are used to migrate from Azure DevOps to Gitea / Forgejo?
Migrate repos and pipelines; convert YAML pipelines to the new CI; move work items via API; re-point service connections; staged cutover.