Salesforce Lifecycle Center (formerly DevOps Center) is free. Salesforce says it is "free and included" with Professional, Enterprise, Performance, Developer, and Unlimited editions. There is no license fee for the tool.
The costs sit around it: Git hosting seats, engineer hours for setup and admin, manual recovery when a promoted change has to come back out, and a separate backup tool. This guide prices each one and works through a first-year example for a 10-person team.
It is part of our Salesforce DevOps guide. For the full product overview, see the Lifecycle Center guide.
Where the money goes:
- Free: the Lifecycle Center app, its pipelines, work items, and promotions. No license fee.
- Paid, to someone else: Git hosting seats on GitHub or Bitbucket Cloud.
- Paid in hours: setup, ongoing admin, and manual recovery after a bad promotion.
- Not included: metadata and data backup, which is a separate purchase.
Is Salesforce Lifecycle Center free?
Yes. Salesforce's own DevOps tools page answers its cost question with "free", and adds that anyone can try the tool in a Trailhead Playground or a scratch org.
Salesforce Help lists the editions in more detail: Lightning Experience in Professional (API access required), Enterprise, Performance, Unlimited, and Developer editions. It is not available in Government Cloud Plus or the EU Operating Zone. The current version is built into the platform, so you open it from the App Launcher without installing a package.
If you are moving off change sets, Lifecycle Center is the free, source-driven replacement. See our change sets comparison and the limitations of change sets.
What Lifecycle Center costs to run
The license is free. Running it is not. Four costs land outside the Salesforce invoice.
Git hosting seats
Lifecycle Center uses source control as its single source of truth, and it supports two Git hosts: GitHub.com cloud-based plans, including GitHub Enterprise Cloud, and Bitbucket Cloud. GitLab, Azure DevOps, and self-hosted GitHub Enterprise Server are not supported.
Both hosts have free tiers, but teams usually pay. As of October 2026, GitHub's pricing page lists Team at $4 and Enterprise from $21 per user per month.
Bitbucket Cloud lists Standard at $3.65 and Premium at $8 per user per month, with the free plan capped at 5 users. The bill grows with every person who commits. For how Git fits a Salesforce team, see our guide to Salesforce version control.
Setup and admin hours
Someone has to connect the Git host, build the pipeline, set permissions, and keep it running. Salesforce recommends a separate project for each production org, notes that Lifecycle Center "doesn't sync metadata and data across projects", and says multiple projects add management complexity.
More orgs mean more admin hours. For the steps, see how to set up Lifecycle Center.
Manual recovery after a bad promotion
If a promotion fails, the branches stay as they were. After a successful promotion, though, there is no built-in way back.
Salesforce's known-issues log lists "Can't Move Promoted Changes Back to a Previous Pipeline Stage", and the workaround is a manual, multi-step resync. That time comes out of engineer hours, often under pressure.
Backup
Backup, archive, and point-in-time recovery are not among Lifecycle Center's documented capabilities. If you need them, they are a separate purchase. Salesforce's own Backup & Recover is quoted per customer: Salesforce says "pricing varies based on each customer's individual needs".
What is included: Lifecycle Center's quality gates can require Apex tests and Code Analyzer scans to pass before a change is promoted, at no extra cost. Its policy governance is in preview and applies to Agentforce Vibes coding agents, not to changes people make. For every gap in detail, see Lifecycle Center limitations.
A worked cost example
Here is a first-year estimate for a team of 10 people who commit and promote changes through Lifecycle Center, for one production org. Git prices are GitHub list prices from its pricing page.
The hours and the $100 hourly rate are illustrative assumptions, not benchmarks. Swap in your own team size, rate, and incident count. For the wider picture, see our breakdown of Salesforce DevOps TCO.
The license line is zero. The first-year total is about $12,880 to $14,920 before backup, and labor is more than 80 percent of it.
In year two the one-off setup drops out, but admin, recovery, and Git seats repeat. They grow with team size and the number of orgs.
Change one assumption and the total moves. Double the recovery incidents and you add $3,600, and a second production org adds a second project to set up and run.
The managed package change in 2026
The original managed-package version is closed to new installs. Salesforce Help says new downloads and installations of the managed package are no longer supported starting in April 2026. Existing installs keep working.
Teams still on the package have a migration tool (currently labeled Developer Preview) to move projects to the next-generation version, after which developers reconnect their environments. The tool is free; the time to plan, migrate, and re-test is not, so budget it if you are still on the package.
When the free tool stops being the cheaper option
Lifecycle Center stays cheapest while your release process is small and simple. The hidden costs rise when:
- You run several production orgs. Each needs its own project, and projects don't sync.
- Your team uses GitLab or Azure DevOps. Lifecycle Center doesn't support them, so you add a second Git host or move repositories.
- Recovery incidents pile up. Each promoted change that has to come back out is manual work.
- You need backup and audit history. Backup is a separate purchase, and Salesforce's Setup Audit Trail keeps 180 days.
- You deploy Agentforce agents. New Agentforce Builder agents need publishing and activation in each org unless the authoring and planner bundles deploy together. See deploying Agentforce agents.
How Flosum compares
Flosum DevOps and Flosum Backup & Archive cover the costs above on one platform. Here is what each part includes, as described on the product pages:
- One-click rollback with impact analysis, in place of manual recovery.
- Backup and archive of data, metadata, files, and relationships, with point-in-time restore at field, record, or full-org level.
- Drift detection and reconciliation across sandboxes, branches, and production.
- Segregation of duties, multi-level approvals, and audit trails that keep history beyond Salesforce's 180-day Setup Audit Trail.
- Git-optional version control, with connections to GitHub, GitLab, Bitbucket, Azure DevOps, Jira, and ServiceNow.
- Agentforce agent metadata under the same version control, approval gates, testing, and audit trail as other changes.
Flosum is free to start; enterprise pricing is custom and quote-based, scoped to your orgs, environments, and modules. For restores in practice, see field-level data recovery.
For side-by-side options, see our four-way comparison, the wider list of Lifecycle Center alternatives, and our roundup of Salesforce DevOps tools. Teams paying for Git seats mainly for version control can also look at version control without Git.
FAQs
Want to see it on your own release process? Book a personalized demo to see how Flosum can cover rollback, backup, and audit history alongside your Salesforce release pipeline.
Thank you for subscribing
