DevOps Software

What I dislike about GitHub is that it can become complex and overwhelming, especially for non-technical users or smaller teams. Some workflows require many steps, such as branches, pull requests, permissions, Actions, and issue management. The interface is powerful, but it is not always simple to understand where something is configured or why an automation failed. Review collected by and hosted on G2.com.

GitHub helps me solve problems around software delivery, code quality, collaboration, and traceability across complex technical projects. In my work as a senior software engineer and AI evaluation specialist, I use GitHub to manage code changes, review pull requests, track issues, organize project history, and support CI/CD workflows.

The biggest benefit is that it gives me a reliable way to collaborate across distributed teams while maintaining accountability. It helps me compare changes, verify implementations, manage regression tests, document technical decisions, and keep a clear record of what was changed and why. This is especially valuable for microservices, cloud infrastructure, payment systems, AI coding-agent evaluation, benchmark development, and production-grade software work. Review collected by and hosted on G2.com.

The pricing model can be surprisingly difficult to forecast as you scale, especially if you rely heavily on client-side feature flags. Because billing factors in Monthly Active Users (MAUs) and service connections, a sudden spike in traffic or expanding our client-side footprint can cause the bill to increase faster than expected. It’s definitely an enterprise-tier tool with an enterprise-tier price tag. Review collected by and hosted on G2.com.

In a distributed architecture, coordinating releases across multiple backend services used to be high-risk. LaunchDarkly solves the stress of 'big bang' deployments. We can deploy new Node.js or Spring Boot services into our Kubernetes clusters behind feature flags, completely decoupling the deployment from the actual feature release. The ROI is massive: zero-downtime releases, no more weekend deployment windows, and the ability to instantly kill a failing feature without having to rollback and redeploy containers. Review collected by and hosted on G2.com.

I think when I was brand new to the platform, I was a little confused by how many similar tools there were. There are a lot of ways to do the same thing, so we really relied on the training resources to help us understand the differences and when it made sense to use each tool. Review collected by and hosted on G2.com.

The brand new Gearset Agent is a GAMECHANGER. The setup was not nearly as intense as I would have expected to get the incredible value out of an AI agent that knows Salesforce inside and out as well as knowing all the details of our Org and the existing fields, automations, and customizations.

We all began with a lot of hesitancy, but very quickly built confidence in the Agent's ability to build/edit/update our existing codebase. Speeds us up so quickly on the mundane and tedious tickets as well as a great partner for solution designing big changes to make sure no stone is left unturned. Review collected by and hosted on G2.com.

The interface can feel a bit cluttered when we have lots of repos, branches, pull requests, and notifications going on simultaneously. Creating more complex GitLab Actions workflows may require a bit of technical experience for advanced CI/CD workflows. Some admin and security features require upgrading to higher-tier plans and can be costly as our team grows. Review collected by and hosted on G2.com.

GitLab is a single source control, code review, issue tracking, and CI/CD automation platform. It helps us team members to align during the development process, avoiding time spent around transferring files and wasting time arguing about edits on a code file. Pull requests and automated testing lead to more stable releases, and Actions means less time spent on runs and deployments, and more knowledge of what's happening in the process. Review collected by and hosted on G2.com.

Frequent UI changes each time we upgrade to new version. Review collected by and hosted on G2.com.

Initially, as a team, we were deploying our DB scripts manually to each server. First, I helped my team analyze the Flyway desktop. We have minimized Deployment errors by using Flyway deployment using Desktop. As we learn and move to CICD using GitHub Actions, we are even faster with our deployments using Flyway Commands for DB deployment. Overall, we have moved from Manual deployment to CICD using Flyway and it's been a very good experience. Review collected by and hosted on G2.com.

Except some small issues, there's not much to complain about. Review collected by and hosted on G2.com.

We used to handle store submissions manually, which was time consuming and error prone. Appcircle automated that entire flow; build, sign, and publish and cutting down our release cycle significantly. The Re-sign Binary feature has also been a huge time saver, allowing us to redistribute the same build with different signing identities without rebuilding from scratch. The publish module in particular removed the need for anyone on the team to have direct access to developer portal credentials, which also improved our security posture. Review collected by and hosted on G2.com.

Some development and multi-environment workflows are limited on the free plan, so teams may encounter plan restrictions earlier than expected.

Protected Preview deployments can also create friction when sharing a build with testers or reviewers. Authentication adds security, but it can make external review more complicated. Environment variables must be assigned carefully to Preview and Production, and a redeployment is usually required after changing them.

The dashboard is powerful, but deployment settings, domains, environment variables, build logs, and runtime information are spread across several sections. This can take time to learn when troubleshooting a release. Review collected by and hosted on G2.com.

Vercel provides the deployment and hosting workflow for our Next.js SaaS application without requiring us to maintain dedicated web infrastructure. It gives us isolated Preview environments for testing, automated Production deployments, custom-domain hosting, and visibility into build and runtime health.

The biggest benefit is release confidence. We can connect a deployment to an exact GitHub commit, test it before merging, and verify that the same approved code reaches Production. This has made our release process faster, safer, and easier to manage. Review collected by and hosted on G2.com.

One area for improvement in Copado DevOps is the initial setup and configuration. New team members face a learning curve around pipelines, deployment processes, and resolving conflicts. Troubleshooting deployment errors can be time-consuming, especially with complex metadata dependencies. Enhancements in initial setup experience, configuration guidance, better error messages, and conflict-resolution capabilities could significantly reduce this learning curve and make onboarding new developers easier. Review collected by and hosted on G2.com.

I use Copado DevOps to automate Salesforce deployments, manage version control, and track releases, which reduces manual errors and gives full traceability. It improves our efficiency by reducing time on deployments and enhancing collaboration with better visibility. Review collected by and hosted on G2.com.

I like it alot Review collected by and hosted on G2.com.

I can automate tasks with different workflows instead of manual setup, maintaining my applications through up-to-date images. It ensures pipelines work smoothly and new changes don't break the master branch. Review collected by and hosted on G2.com.

While JFrog is an industry standard for artifact management, the main challenge is its cost and licensing complexity, especially as storage and user seats scale up for enterprise tiers. Additionally, the learning curve and admin overhead for managing fine-grained permissions, repository replication, and self-hosted instances can be steep for smaller teams that might prefer a lighter, plug-and-play solution. Review collected by and hosted on G2.com.

The Problem: Modern applications rely on dozens of different tech stacks, package managers (npm, Maven, PyPI, NuGet, Docker/OCI, Helm, etc.), and multi-cloud infrastructure. Managing these dependencies across disconnected registries creates fragmented workflows, security blind spots, and build failures due to external registry downtime.

How JFrog Solves It: JFrog Artifactory acts as a universal, binary repository manager that supports virtually every package format, framework, and build tool out-of-the-box.

The Benefit:

Consistency: Every developer and CI/CD agent pulls dependencies and pushes artifacts through a single, centralized hub.

Reliability: Caching remote dependencies locally prevents build breaks if external registries (like npmjs or Docker Hub) experience downtime or rate limits. Review collected by and hosted on G2.com.

New users and administrators often need significant time to fully understand the workflows, transport controls, dependencies, and overall configuration. Implementation and setup can also be more involved than a team might expect, especially in a complex SAP landscape like ours (DEV-QUA-STAGING-PT-PROD). Review collected by and hosted on G2.com.

Rev-Trac is solving the problem of managing and controlling changes across our SAP landscape. Without a centralized tool, coordinating transports, approvals, dependencies, testing, and releases can be manual and difficult to track, which increases the risk of errors and failed deployments.

The biggest benefit is greater visibility and control. Rev-Trac helps us understand what is changing, where it is moving, what dependencies exist, and whether the appropriate approvals and checks have been completed before deployment.

This benefits us by reducing deployment risk, improving governance and auditability, and making the release process more predictable. It also reduces the amount of manual coordination required between development, testing, Basis, and business teams, allowing us to deliver changes more efficiently and with greater confidence. Review collected by and hosted on G2.com.

Nothing major springs to mind. I have noticed that some jobs can sit in the queue for a while, which I think is down to worker availability. While it isn’t a huge issue most of the time, it can be a problem if you’re trying to push through an urgent change. Review collected by and hosted on G2.com.

Semaphore helps us build complex CI/CD pipelines, which gives us confidence that we’re not deploying broken builds. Review collected by and hosted on G2.com.

The interface feels dated compared to more modern CI/CD tools, and navigating plugin configurations can get cluttered as a project's pipeline complexity grows. Managing and updating plugins over time requires ongoing maintenance, since compatibility issues between plugins occasionally surface after updates. Setting up more advanced pipelines still requires a fair amount of Groovy scripting knowledge, which adds a learning curve for team members newer to Jenkins specifically. Self-hosting means taking on infrastructure maintenance responsibility that some newer, managed CI/CD platforms have abstracted away entirely. Review collected by and hosted on G2.com.

Jenkins has automated build, test, and deployment processes across every project I've used it on, removing the need for manual deployment steps that used to be error-prone and time-consuming. Its flexibility has let me tailor CI/CD pipelines to each project's specific needs rather than working around a more rigid, opinionated tool, which has been valuable across the range of different tech stacks I've worked with over the years. Review collected by and hosted on G2.com.

Not a fan of the new pipeline UI (hard to see what I need to debug infrastructure issues), but Buildkite hasn't forced anyone over to it since it was introduced a year ago. For SOX compliance, the user roles could use more granularity and the Audit log is difficult to use. Review collected by and hosted on G2.com.

It is solving management of our complex pipelines, allowing us to easily manage running hundreds of jobs for our test pipelines. Review collected by and hosted on G2.com.

At times it feels a bit limited when I’m working on slightly more complex Salesforce tasks. For basic deployments it works fine, but when I tried to manage more detailed changes, I still had to rely on other tools alongside it. It also took me a while at the beginning to understand the overall flow, so a little more guidance or clearer direction would really help new users get started. That said, for simple use cases, it still does the job well. Apart from that, it works well for simple and structured deployments. Review collected by and hosted on G2.com.

In my work, managing deployments and tracking changes in Salesforce manually can be time-consuming and error prone. Copado Essestials helps solve this by providing a structured way to manage deployments and keep track of changes across environments. This reduces my manual efforts, saves my time, and helping me to avoid mistakes. In my current work, I use it mainly for handling smaller deployments and tracking changes step by step. Although, it improves my productivity and making my workflow more efficient, organized, and reliable. Review collected by and hosted on G2.com.

I don’t like the “X projects per plan” kind of subscription. I usually have 10 to 20 projects that get, at most, one deployment per month, so I’d much rather be billed by build minutes. I also don’t use most of the “premium” features, so even though they’re available to me, I feel like I’m basically paying for nothing. Review collected by and hosted on G2.com.

DeployHQ lets me stop worrying about what happens when I push a commit to my repository. I know the changes will be live within a few minutes, without me having to keep track of anything. I also don’t have to set up any DeployHQ-specific configuration files. Review collected by and hosted on G2.com.

I believe that the DevOps solution should have greater segmentation of access and security, with the possibility of segmenting access to pipelines or other resources within the branch. In the backup solution, it would be interesting to have the possibility to transfer data between orgs, such as removing data from org A and transferring it to B. Review collected by and hosted on G2.com.

I use Flosum as a DevOps and backup solution for Salesforce, solving issues like rollback, code versioning, and quality analysis, which were absent in Salesforce's DevOps Center. Review collected by and hosted on G2.com.

- no german hoster available, only big american hosters Review collected by and hosted on G2.com.

Hosting our "mono repo drupal application" as a "poly site project".

Every tenant has their own:

- database

- filesystem

- feature flags activated

All from one code base.

Deployments can be triggered manually or automatically, easy to handle.

Setup of new client infrastructure can be automated. And is up in minutes to run the same code in a new project.

I can focus on developing the application and don't have to be afraid of handling the infrastructure for it.

We self-hosted Lagoon for 1/2 year and switched to a fully managed service by Amazee. Best decision ever for my work-life balance as CTO. Review collected by and hosted on G2.com.

Configuration heavy which can be difficult to setup in the beginning. Had trouble in configuring pipeline for wheel file deployment Review collected by and hosted on G2.com.

Opsera helped us in automating our deployment of python scripts to AWS Glue jobs as well as our DB schemas to AWS Redshift. It helped us achieve our goal of CICD in record time. Automation pipelines have helped us decrease our turnaround time and increase productivity Review collected by and hosted on G2.com.

The UI could be more intuitive, and sometimes large data sets take longer to process than expected. Review collected by and hosted on G2.com.

I use Prodly DevOps to make Salesforce change management and deployments faster and less error-prone. It automates configuration migration, ensures accuracy, maintains compliance, improves release speed, and reduces deployment risk. It saves time and gives me confidence in smooth changes. Review collected by and hosted on G2.com.