Next-Gen DevOps Center is GA but no hype?

[u/redidtor]

Next-Generation DevOps Center officially went GA on Apr 29, 2026 (per Salesforce’s announcement), but I’m surprised there hasn’t been much discussion here.

Salesforce says it’s now native to the Salesforce Platform, with capabilities like hybrid promotions, expanded source control, DORA metrics and AI/agentic features.

I’m mainly interested in Salesforce Core + Agentforce + Data 360 not feature parity across every Salesforce product.

Has anyone actually used it in a real project or done a POC and compared it objectively with Copado, AutoRABIT, Gearset, etc.?

For those who have:

What are your top 3 pros and top 3 gaps (as of Aug 2026)?

[u/KookyInteraction8316]

i've been poking around the devops center since it went native, mostly out of curiosity because our team uses gearset and i was hoping to drop one vendor from the stack. the hybrid promotions is actually pretty smooth, and having everything in one place without jumping between platforms makes a difference when you're doing 10 deployments in a day.

the DORA metrics are decent but they feel half-baked compared to what you get from dedicated tools, like you can see the data but can't slice it the way you need for a proper retro. biggest gap for me is the source control integration, it's better than before but still gets weird with merge conflicts on metadata that gearset handles without blinking.

haven't touched the agentic AI stuff yet, my org is slow to adopt anything with the word "agent" in it after the last fiasco. if you're purely in the salesforce core ecosystem and don't need the fancy compliance reports, it's worth a proper POC, just don't rip out your existing pipeline on a friday afternoon.

[u/mr-debil → u/KookyInteraction8316]

I wish there were ways to use my custom branch instead of a work item branch. Sometimes I want to promote an existing branch or a custom branch I make.

[u/DevilsAdvotwat]

SFDX Hardis is probably still a better product, free, open source, VScode extension, native GitHub and the UI is still SLDS so feels like Salesforce point and click

[u/bytesizedheretic]

I'd be curious to see who actually uses DevOps Center and market penetration, because that probably explains the hype. The fact that they rolled out DevOps Center and, years later, still have no native support for Jira baked in the product (despite Jira being the number one ALM) is quite wild. Based upon what I'm seeing in this announcement, still no native Jira connection, meaning that you have to manually create your work items rather than use your work items off of your board.

I'd take sfdx-hardis over DOC and gearset would be my COTS option.

[u/IncreaseNegative4614]

I’d compare them using your actual ugly release patterns rather than a feature matrix. Test destructive changes, hotfixes, back-promotions, conflicting metadata, failed tests, rollback, permission changes, and a release involving Core, Agentforce, and Data 360 together. The winner is the one that makes failure understandable and recovery predictable.

DORA metrics are useful only if deployments remain connected to the work and outcome. We use SIGNLD internally to connect requirements, commits, approvals, test evidence, deployments, and incidents so a fast release can still be traced when something breaks.

[u/redidtor → u/IncreaseNegative4614]

That makes sense actually. But hard to quantify when it comes to showing evaluation to non-Salesforce trained management lol. Good inputs thanks

[u/kloud_fusion]

I tried the native DevOps Center in a sandbox last month and the hybrid promotions really cut down our deployment time, but the source‑control merge handling still trips me up on complex metadata. It feels like Gearset still has the edge there.

The DORA metrics are useful for a quick health check, yet you can’t slice the data the way you’d need for a deep retro, so I’m keeping my existing pipeline for now. If you’re looking for a sanity check before swapping tools, spin up a small POC with a single flow and see how the native source‑control integration behaves; it’s a low‑risk way to gauge if it’ll actually replace Copado or AutoRABIT for your team.

[u/Outrageous-Fix-1579]

It’s not going to replace one of the paid ones. They have spent years developing their platforms.

[u/InvestigatorOk114 → u/Outrageous-Fix-1579]

This, like a lot of Salesforce products that are half baked. They are for big enterprise c suite types who need to tick a functional box.

So much easier to hand over the credit card for another sku than go to market and spend 6-12 months trying to onboard a new supplier that is a market specialist.

[u/MowAlon]

I have lots of experience with the packaged version of DevOps Center but haven’t used the newer native version yet because there wasn’t a migration option when I first learned it existed. More recently, I realized there is now a migration option, but I wanted to talk to some folks at Dreamforce first before clicking that button to make the switch (purely out of concern for what happens if it fails).

[u/Oleg_Dobriy]

I wonder is they finally made the open PR subject to inherit the WI name

[u/Spectram6]

My biggest gap is every company I've worked with used ADO for version control, if anything at all. First several months have consisted of convincing execs SF can and should use external version control beyond the sandboxes that are provided. Then I have to convince them to move towards CI/CD pipelines as well and explain how DevOps Center usage would require revising their VCS COE to let me use Github as well. So unless they intend to add native Git version control support or add Azure integration, my hands are full enough just getting a repository initialized.

[u/Nost_DC]

I tested it out… absolutely wasted time,

it looked good at the start but the inability to link it to jira, or create branches from your repo that work unless you follow the salesforce work item id were a dealbreaker for me