DevOps Software

While GitHub is an exceptional platform, there are a few areas that could be improved. Some advanced features — especially around enterprise‑level automation and security — are locked behind higher‑tier plans, which limits flexibility for smaller teams. The interface can also feel slow or cluttered when navigating large repositories with many branches, issues, or pull requests. Additionally, GitHub Actions sometimes requires deep YAML knowledge, making complex workflows harder to maintain.

One major concern for me is customer support responsiveness. When I encounter a serious issue and open a support ticket, it often takes months before I receive any meaningful reply. This delay makes it difficult to resolve critical problems in a timely manner. Review collected by and hosted on G2.com.

GitHub solves several critical challenges in modern software development. It provides a reliable and structured way to manage version control, ensuring that every change is tracked, documented, and reversible. This eliminates confusion around code updates and makes collaboration far more efficient. The Pull Request workflow helps maintain code quality by enabling clear reviews, discussions, and approvals before merging.

GitHub also centralizes project management through Issues, Discussions, and integrated CI/CD pipelines with Actions, allowing me to automate builds, tests, and deployments without relying on external tools. This reduces operational overhead and keeps the entire development lifecycle in one place. Overall, GitHub gives me a more organized, secure, and productive environment for building and maintaining software. Review collected by and hosted on G2.com.

Managing a growing number of feature flags over time requires discipline to clean up ones that are no longer needed, otherwise the codebase accumulates unnecessary complexity. Pricing scales with usage and seats, which can get expensive as the number of flags and monthly active users grows. The initial setup for integrating flags cleanly into existing code took some restructuring, especially for parts of the codebase that weren't originally built with feature flagging in mind. Some of the more advanced targeting and experimentation features have a learning curve before getting full value out of them. Review collected by and hosted on G2.com.

LaunchDarkly has let us test new features on a small subset of real users before a full rollout, catching issues early without risking a broken experience for everyone on the platform. This has made deploying changes to core functionality, like trip flow updates, much safer, since we can instantly disable a feature if something goes wrong instead of needing an emergency rollback and redeploy. Review collected by and hosted on G2.com.

We would all like for it to be able to be faster, but it is getting better, and vastly better than traditional tools. I would like to be able to more easily accommodate refreshing sandboxes in the pipeline (or hot-swapping). No real dislikes, just feature requests, I guess! Review collected by and hosted on G2.com.

It's allowing our team to be able to work across the globe, on projects that may or may not overlap in terms of metadata components that we touch, while not hindering our ability to deploy changes. We overall much more efficient not only in the standard build -> deploy, but we're not fixing things accidentally overwritten when someone else updated the same layout, etc.

It's also integrating with Jira so that we can capture actual changes made in tickets, that we can then use to auto-generate actually useful release notes. Review collected by and hosted on G2.com.

While GitLab provides a comprehensive DevOps platform, navigating its vast feature set across complex nested projects and CI/CD configurations can occasionally feel cluttered. Additionally, managing heavy pipeline runner overhead or debugging intricate continuous integration configurations locally prior to pushing changes can still present a steep learning curve for development teams. Review collected by and hosted on G2.com.

It is the most accessible tool for code review and maintenance. Review collected by and hosted on G2.com.

GitLab eliminates the friction of managing fragmented toolchains by consolidating version control, CI/CD automation, issue tracking, and security scanning into a single unified DevOps platform. This centralizes code maintenance and versioning, allowing teams to seamlessly collaborate, rollback or switch between release versions instantly, and automate pipeline workflows to deliver secure software faster with significantly reduced operational overhead. Review collected by and hosted on G2.com.

The thing I dislike about Redgate Flyway is that every time I manually need to migrate changes. It should have AI integrated into it that automatically migrates all changes whenever there is any. Review collected by and hosted on G2.com.

Redgate is saving a lot of time for my organisation developers and testers providing easy usage and quick response time for migration. Also the error messages it shows whenever there is any migration error are very descriptive and easy to understand for a new joiner as well. It is overall benefitting me by adding up business value and safe migration of changes keeping all developers and testers at same level of code. 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.

The main thing I find slightly difficult is understanding the logs when there is a technical error. They can contain information that is useful to an experienced developer but takes some time to understand as a student. The Hobby plan also has usage limits, so I have to be more conscious of those when working on projects that receive more traffic or need more resources. Review collected by and hosted on G2.com.

Earlier, when I finished a web project, getting it online and keeping track of different versions was something I had to think about separately. If I made a change that broke something, it was also not always obvious which version I should return to. Now, I can deploy the project, check the deployment status, open the live version, look at logs when something goes wrong, and use an earlier deployment if I need to go back. I can also connect a domain once the project is ready to share. As a result, hosting has become a more regular part of my development workflow rather than something I have to figure out from scratch for every project. It does not remove the technical problems that come with deploying a website, but it gives me a clear place to manage and troubleshoot them. Review collected by and hosted on G2.com.

One thing I dislike about Copado DevOps is that the initial setup and learning curve can feel complex for new users, especially for teams that aren’t already familiar with DevOps practices. Some configurations and more advanced features can also require additional training before you’re able to use them effectively. That said, once you get past the onboarding, the platform works well for managing Salesforce deployments and helps keep the overall deployment process organized. Review collected by and hosted on G2.com.

Copado DevOps helps tackle the challenge of managing Salesforce deployments, version control, and release coordination across multiple environments. It helps reduce deployment errors, improves collaboration across development teams, and automates repetitive release tasks. For me, that translates into real time savings, more reliable deployments, and a Salesforce development lifecycle that stays better organized and runs more efficiently overall. 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.

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.

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.

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.

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.

One challenge with JFrog is managing repository storage as artifacts grow over time. However, implementing automated cleanup policies and regular monitoring helps keep repositories organized, optimize storage usage, and maintain smooth CI/CD performance. Review collected by and hosted on G2.com.

It helps solve challenges related to artifact management, dependency control, and software release reliability in DevOps environments. It centralizes binaries, packages, and build artifacts in one place, making deployments more organized and consistent across teams.

This has helped improve build reliability, simplify version tracking, and reduce issues caused by dependency mismatches. It also supports faster CI/CD workflows and provides better traceability for both modern and legacy applications, making release management more efficient and secure. 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 triggerd manually or automatic, 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 dont have to be afraid of handling the infrastructure for it.

We self hosted lagoon for 1/2 year and switched the to fully managed service by amazee. Best decision ever for my work live balance as CTO. Review collected by and hosted on G2.com.

Opsera has established itself as a market leader in insights and analytics. Its capabilities are invaluable for organizations that want to effectively track AI token consumption, monitor usage trends, and understand overall token economics. That said, the UI/UX still needs improvement to make the experience smoother and more intuitive. Review collected by and hosted on G2.com.

We use it to create CI/CD pipelines, handle migrations, and manage Apigee deployments. It also provides unified insights, which helps keep everything visible in one place. 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.

Build times become more noticeable in monorepos and in projects with a large number of generated pages. Caching helps when enough of the previous build can be reused, but changes that invalidate a large portion of the project can still take a while. On a small application, that delay is easy to ignore. Once several developers are opening pull requests and each one generates a preview, concurrency and overall build consumption start to become part of the delivery conversation. Deploy Previews reduce the work of maintaining temporary environments, but they don’t make those environments free. Review collected by and hosted on G2.com.

A checkout redesign had already passed local testing when the client asked marketing, design, and QA to review the variants before anything reached production. The pull request produced a Deploy Preview with its own configuration, the Netlify Functions used by the new flow, and a payment variable pointing to the test environment. Design left feedback through the Netlify Drawer, and QA caught an issue that only showed up when a user returned from the payment provider. The Function logs made it clear that the same callback was being processed twice. We corrected the idempotency logic, updated the pull request, and everyone re-reviewed the fixed version using the same preview link, rather than waiting for another temporary environment to be set up. After release, a dependency triggered a failure on a less frequently used route, so we used Instant Rollback to restore the previous deploy while the fix was being prepared. Netlify didn’t prevent the defect, and it didn’t replace proper test coverage. What it did change was how quickly the team could review the real build, trace the problem to the exact Function version, and recover production without having to improvise a rollback while the client was already watching. Review collected by and hosted on G2.com.