Efficiently deploy your ASP.NET apps and windows services

DriveCentric and Octopus Deploy


“Using Octopus and GitHub Actions, we successfully released to Production nearly 500 times in 2021, doubling the number of releases compared to the previous year.”

- Philip Magalios, Senior DevOps Engineer

Download Octopus Convert to PDF

DriveCentric uses Octopus to double its annual deployments

DriveCentric, based in Missouri, United States, is a leading provider of Customer Relationship Management (CRM), Artificial Intelligence (AI), and conversational engagement tools for the automotive industry. Its software provides innovative capabilities to automate automotive dealership processes and to provide an exceptional customer experience. Widely regarded as an industry leader, DriveCentric has many product awards to its credit, including the prestigious AWA Vanguard Award and DrivingSales Dealer Satisfaction Award for CRM sales.

DriveCentric operates in an industry where digital experiences are becoming increasingly critical. Its CRM technology is at the forefront of improving these experiences, allowing dealers to enhance engagement, reduce sales cycles, and increase growth.

Auror case study pipeline


Leading up to implementing Octopus Deploy in 2018, DriveCentric's deployment processes, while effective, were time-consuming and tedious. The company’s goal was to modernize and automate its CI/CD pipelines, while providing faster and more reliable deployments.

DriveCentric supports a variety of workloads such as web applications, Windows services, containerized services, and AWS Lambdas, with each having unique requirements and challenges. With a relentless focus on innovation, the DriveCentric team sought out a robust solution to increase automation, reduce deployment risk, and deliver value faster to its customers.


Thanks to Octopus Deploy, DriveCentric was able to implement automated deployments across its entire portfolio of applications and services, reducing time spent on deployments and enabling teams to focus their efforts in other high-impact areas.

Whereas deployments were once manual, the DevOps team now deploys exclusively with Octopus. This has resulted in:

  • Consistent and repeatable processes
  • Lifecycles being maintained
  • Visibility into deployed versions
  • Quality gates for process compliance
Two years ago, DriveCentric began migrating its build server from Jenkins to GitHub Actions for better integration with GitHub. At this stage, DriveCentric was already using Octopus, so the team used the Octopus CLI actions to manage deployments in their workflows.


Octopus has reduced errors and deployment time for DriveCentric by introducing an automated, repeatable deployment process. DriveCentric’s DevOps team has experienced a nearly flawless success rate with Octopus deployments.

Automating deployments through Octopus has allowed DriveCentric to scale the frequency of its deployments. DriveCentric successfully released to production nearly 500 times in 2021, doubling the number of releases compared to the previous year, and is on track to exceed 500 production releases in 2022.

Combining Octopus with GitHub Actions has also streamlined DriveCentric’s pipeline. The team harnesses the power of Octopus in their GitHub workflows to ensure rapid deployment creation and high reliability when deploying.

Shout out to @OctopusDeploy for making their software so easy to work with. Just upgraded a 2 year out of date instance and migrated it to a new server and it worked with no effort beyond what their documentation said to do.

Twitter user Alex Dent Alex Dent

We've been overhauling our internal infrastructure and back-end systems over the past month, including a move back to full @OctopusDeploy deployments; rediscovering how nice it is to have a platform-agnostic orchestrator that can deploy practically anything, anywhere ❤

Twitter user Nicholas Blumhardt Nicholas Blumhardt

Tools like @OctopusDeploy can be great in enabling culture change, we've been able to scale and improve our configuration story since we started using it.

Twitter user Niel Chalk Niel Chalk