CircleCI vs. Octopus Deploy

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CircleCI
Score 9.5 out of 10
N/A
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.
$15
per month
Octopus Deploy
Score 10.0 out of 10
Mid-Size Companies (51-1,000 employees)
Australian company Octopus Deploy offers their eponymous automated deployment and release management software that integrates with the user's preferred CI server and adds deployment & ops automation capabilities. Octopus Deploy enables developers, release managers, and operations folks to bring all automation into a single place. The vendor states that by reusing configuration variables, environment definition, API keys, connection strings, permissions, service principals, and automation logic,…
$12
Pricing
CircleCIOctopus Deploy
Editions & Modules
Server
Contact Sales
Performance
starting at $15
per month
Scale
starting at $2000
per month
Cloud
Free 30 day trial
unlimited targets/users/projects
Server
Free 30 day trial
unlimited targets/users/projects
Enterprise
Starting at $18 per month
Enterprise
Starting at $18 per month
Server
Starting at $12 per month
Cloud
Starting at $12 per month
Offerings
Pricing Offerings
CircleCIOctopus Deploy
Free Trial
NoYes
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeOptional
Additional DetailsOctopus Server edition is available as a 30 day free trial on our unlimited tier for any scenario, including production, and commercial use. After the trial period ends you can keep your working configuration and upgrade to a paid license and continue deploying uninterrupted. Octopus Cloud is an alternative that is hosted by us, and is also available as a 30 day unlimited trial. No credit card is needed to create a Octopus Cloud trial instance. You can convert the Cloud trial to a paid instance at any time during or after the trial period, and keep all of your instance configuration. Octopus also offers an Enterprise tier which offers advanced features for teams at scale including, advanced high availability, insights & DORA metrics, ServiceNow & Jira Service Management integration, unlimited instances, 24/7 support & service credits, and a Customer Success Manager. Volume discounts are available above 500 targets, and temporary bursting for certain scenarios is supported.
More Pricing Information
Community Pulse
CircleCIOctopus Deploy
Considered Both Products
CircleCI
Chose CircleCI
Based on the cost for feature set that we needed we went with CircleCI. There were also more people on our team that knew how to use CircleCI already compared to other products which made it a preferred choice for ramp up. Other products were not as robust and quick to …
Chose CircleCI
CircleCI is the only product we've used.
Chose CircleCI
We use CircleCI when we need a good, independent CI/CD provider in an existing workflow. That said, we've begun investing more heavily in GitHub actions as it's closer to where our code is stored. CircleCI is a feature of a workflow, and can be filled by many different service …
Chose CircleCI
CircleCI is a sass product which means you don't need to maintain your own servers. This can also be a negative as you are dependent on their service. This also means you can't ssh into a machine to see what went wrong like you can with Jenkins. However for most users this …
Chose CircleCI
Because the Travis CI features are not very good, it has a lot of problems with concurrency and the uptime of the on-cloud solution was the worst we have ever tried.
Chose CircleCI
CircleCI is still being developed and worked on continually while TravisCI is not.
Chose CircleCI
CircleCI seemed to have a quicker setup than other similar products, with a good integration with GitHub repos. Projects are quick and easy to set up within the UI, and workflows can then be created off the back of those fairly intuitively. Clever interpretation of commit …
Chose CircleCI
CircleCI is the company that is innovating compared to the other ones. I think it's a great piece of software compared to other open source options that don't have as much functionality and improved capability over time.
Chose CircleCI
While the UI on CircleCI is not my favorite, it's leagues better than Travis CI. I really like Heroku CI much better, but the functionality is much more limited there. If Heroku CI had the same functionality as CircleCI, I probably wouldn't use CircleCI.
Chose CircleCI
Jenkins and Teamcity both have additional features that maybe you require, but they are also a lot more work to get set up and working. There's a much longer learning curve to getting these configured for a simple build. They're not hosted, so you have to maintain the …
Chose CircleCI
CircleCI does a lot of what we need it to do; however, I believe Jenkins is a better Continuous Integration tool. Jenkins has more capabilities and integrations. In addition, Jenkins is a much more widely used tool, which means more developers are familiar with it and have …
Chose CircleCI
Not having to manage / deal with a Jenkins server is fantastic. I don't have much personally against Jenkins. I've set up and run a Jenkins server before. It's just complexity that doesn't really have much to do with the business beyond getting our software to our customers. My …
Chose CircleCI
Since CircleCI gave us its infrastructure we don't have to worry about servers, provisioning and maintenance. Also CircleCI provides us great features to increase speed of builds by adding more containers to the build. Jenkins is the best open source alternative but it requires …
Chose CircleCI
Jenkins is usually self-hosted, Travis CI's infrastructure is largely unreliable (lots of tests time out for no discernable reason), and Semaphore encourages you to configure your CI/CD from a web UI. We like CircleCI because its hosted, our tests run largely as expected on …
Chose CircleCI
It was our CTO who did the evaluation, not me, but as I recall other services weren't as parallelizable. We knew we wanted to run on many containers simultaneously for fast test results.
Chose CircleCI
For us it really came down to CricleCI being the fastest and simples tool to get started with. The GitHub integration is slick and seamless and the scripting config file allowed us to configure our entire build system, including tests, in less than a day. It's very light weight …
Chose CircleCI
Circle was the first CI with simple setup, great documentation, and tight integration with Github. Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when …
Chose CircleCI
Travis has full YML configuration in areas where CircleCI is slightly lacking still, which is great, but CircleCI offers more features, settings, and potential performance.

Codeship is simpler to use, you can use it entirely from their UI without modifying your Git repository at …
Chose CircleCI
Travis CI is great for open source projects – it's completely free, but CircleCI offers some support for closed projects as well. CircleCI has cheaper pricing plans, and you are able to customize them as much as you want. At Travis CI you can select only a predefined amount of …
Chose CircleCI
The biggest downside to CircleCI is that it doesn't support parameterized builds, that is testing your code against language version X and Y, or framework version A and B. Beyond that, it is really a great product.
Chose CircleCI
I had used Travis CI in some of my open source projects. However, it was too expensive for us so I looked for an alternative that was in our budget. Scrutinizer is also very useful, but also out of our budget. When we get larger I could see myself using Scrutinizer for quality …
Chose CircleCI
I think these three tools are just as good as the other except that Travis CI supports mobile a lot better but price wise, CircleCI is the best that I have found and is supports the need for a startup. For a long while, CircleCI had Docker support before Codeship but now, …
Chose CircleCI
We looked at various others, but the clincher for us was really iOS build support and CircleCi was one of the few that had it.
Octopus Deploy
Chose Octopus Deploy
We also use Ansible, which is much broader and platform/tool diverse. Octopus [Deploy] currently serves a niche for us - .Net and .Net Core deployments. It is capable of doing other things, but it does its original function better than broader tools like Ansible.
Chose Octopus Deploy
I used TFS back when it was called that, and that was a mess. ADO isn't as bad but has many limitations and things that are hard to do. The main difference is I ENJOY working in Octopus Deploy. Not so much with ADO. I'm always trying to figure out things that are stupid. …
Chose Octopus Deploy
Octopus showed better cost numbers than Azure DevOps and more flexibility against GitLab CI/CD. Octopus customization in step templates that can be reused and easily created gives big advantages against many of its competitors. Octopus was selected for these features and …
Chose Octopus Deploy
Octopus Deploy was the obvious choice at the time, its strong .net support, robustness, ease of use, and integration into an existing process was a big plus. Also, Octopus Deploy was kind enough to give my organization a not for profit community licence. In addition, the …
Chose Octopus Deploy
Azure DevOps Server (formerly Team Foundation Server), Azure DevOps Services (formerly VSTS) and Visual Studio IDE
Chose Octopus Deploy
This software, unlike Chef, is much easier to configure or manage, since its platform provides documentation or tutorials on how to use it, besides its interface is much more modern and easy to use, it allows you to choose where you want carry out the implementations of the …
Chose Octopus Deploy
I am not aware of other products like Octopus that are available, but it is a great product for our company. We can stay ahead of the game by allowing developers to deploy code in a continuous deployment model while still maintaining the overrall infrastructure and enabling …
Chose Octopus Deploy
TeamCity is focused more on the build process. It's deployment capabilities are weak compared to Octopus. Bamboo is a proper competitor, but it is far more costly for our needs. The free version of Octopus has proven incredibly competent and sufficient for our needs, and …
Chose Octopus Deploy
There aren't really any competitors in the land of ASP.NET. Deployment is too ad-hoc. Other tools exist that have massive downsides, like Web Deploy. Most aren't even supported anymore. You could argue that containers (Docker) are a competitor, but containers cannot be used for …
Chose Octopus Deploy
Octopus Deploy is a deployment focused tool. Its purpose is to manage deployment environments. Tools like TeamCity and Visual Studio Team Services are Continuous Integration tools. You can accomplish many of the same tasks in TeamCity and VSTS but their focus on CI also means …
Chose Octopus Deploy
We looked at IBM UrbanCode Deploy and Release and Microsoft VSTS while looking for Application Release Automation tools. While VSTS doesn't work with cross-platform technologies IBM UrbanCode Deploy commands a premium price for the features it offers. Also, it needs UrbanCode …
Best Alternatives
CircleCIOctopus Deploy
Small Businesses
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Enterprises
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
CircleCIOctopus Deploy
Likelihood to Recommend
8.0
(0 ratings)
8.6
(0 ratings)
Likelihood to Renew
-
(0 ratings)
8.0
(0 ratings)
Usability
10.0
(0 ratings)
8.4
(0 ratings)
Performance
7.8
(0 ratings)
8.5
(0 ratings)
Support Rating
6.9
(0 ratings)
8.2
(0 ratings)
Ease of integration
-
(0 ratings)
8.5
(0 ratings)
User Testimonials
CircleCIOctopus Deploy
Likelihood to Recommend
CircleCI is well suited if you, your developer, or team of developers have already worked with it in the past. They don't need to go through the learning curve of yet another Continuous Integration tool. Circle handles Continuous Integration workflows very well, including pretty complex workflows. With that said, Circle can get expensive if you need to run multiple containers in parallel and might not be as easy to setup as some alternatives, such as Jenkins.
Read full review
  • The ability to manage different stages and define a workflow is very useful for ops troubleshooting as well as deployment. You can see which version each environment has for each project, and promote or redeploy versions.
  • You can view deployment logs and dig deep into problems or long deployment steps.
  • Finding old releases can be a pain, and there isn't a good way to compare releases.
  • It does not really lend itself well to viewing what the content of a release is further than the version number. Ideally, you would be able to tie a deployment to the builds from the build server as well as specific commits from source control.
Read full review
Pros
  • Full customization and scripting abilities. Using tools like bash scripts, SSH, and Node, running almost anything upon committing some code to GitHub becomes possible.
  • Integration with all of our favorite services. GitHub and Slack in particular are crucial to our business and CircleCI's integration is seamless and full-featured.
  • Great config file syntax. Many CI services require you to perform advanced configuration in a UI. This is fine at first (and CircleCI offers this for many options available), but when you start needing to manage a large number of projects, committing configuration changes to a Git repository is more consistent and maintainable than making the change many different times manually in a UI.
Read full review
  • Many different platforms, languages, and operating systems are supported. You can deploy to your own server or the cloud. You can deploy to Windows, Linux, etc.
  • Many different "step templates" are included, which make it very easy to deploy what you want, how you want. Such as deploying over SSH, FTP, etc.
  • Support is very responsive and personable. You won't just be talking to a robot or a script. They will either solve your problem or understand it enough to solve it in a future release.
  • Their documentation is well thought-out and very helpful. I have found very few missing pieces.
Read full review
Cons
  • CircleCI mostly getting built into both upstream platforms (Github/Gitlab) and downstream platforms (AWS, Azure, GCP), in which cases it's often a better fit or can be used as a part of existing tooling
  • UX can be confusing to navigate and see what's happening.
Read full review
  • Support for non-Microsoft applications needs to be improved to bring it on par with other comparable automation tools.
  • It doesn't yet provide integration options with other IT management tools like JIRA and HP Support to implement continuous delivery and true DevOps processes.
  • Support for AWS/Azure has been included very recently and it's not still very mature and feature rich and is expected to improve further in upcoming releases.
Read full review
Likelihood to Renew
No answers on this topic
Would be a 10 except for the retirement of the free Community Edition.
Read full review
Usability
CircleCI interface is awesome in that it is relatively modern and makes it clear exactly which parts of the engineering lifecycle you are in
Read full review
Some functionality feels slightly hidden in the menu system. For example: script modules are in the same menu as packages, where I feel that are not related entities. One is code for the deployment, the other is the thing that you are deploying...
Read full review
Performance
It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
Read full review
Octopus Deploy is a software that runs very effectively, is easy to use, does not require such a high learning curve, provides the necessary tools to carry out the functions it offers, making it a very flexible software, it also allows that can be configured according to the needs of the user and provides integrations with other very advantageous tools since they are carried out in a very favorable way.
Read full review
Support Rating
I haven't personally used their support service, but I have heard from others that they are responsive. I've also seen only one or two downtimes in over a year of use and both were no more than an hour or two.
Read full review
Octopus Deploy support has always been there for us, even when using the free tier, we get responsive hands-on help. We haven't needed to use that level of support since the documentation is clearly written, and help is readily available within the interface itself. Using Octopus Deploy is a truly joyful experience.
Read full review
Alternatives Considered
Jenkins and Teamcity both have additional features that maybe you require, but they are also a lot more work to get set up and working. There's a much longer learning curve to getting these configured for a simple build. They're not hosted, so you have to maintain the infrastructure and scale yourself. They're both good products if you require more than CircleCI, but if not, skip the extra headache and go with something simple like CircleCI.
Read full review
Octopus Deploy was the obvious choice at the time, its strong .net support, robustness, ease of use, and integration into an existing process was a big plus. Also, Octopus Deploy was kind enough to give my organization a not for profit community licence. In addition, the product comes from a local Brisbane based company and it is always good to support local businesses when you can.
Read full review
Return on Investment
  • Saves us a lot of time and reduces potential mistakes by making our deployment and QA process completely automated
  • Builds docker images for us so we don't have to build them locally on our machines
  • Runs tests automatically on every commit, so we catch mistakes early
Read full review
  • Any automated deployment process will save your company a ton of money on testing and bugs. When you don't automate your deployments, you can't be certain that what you are moving between environments is the exact same code with the same or appropriate configuration. What you tested might not be what got deployed.
  • We've saved a lot of money using Octopus over the mostly manual process we were using before. We've removed a lot of the errors that come from manual, human intervention.
  • Octopus has also allowed us to accomplish more with fewer people. It is easy to bring new people up to speed on the deployment process, and we can be confident of success after very little training.
Read full review
ScreenShots

Octopus Deploy Screenshots

Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of