GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps teams across the complete DevSecOps lifecycle, from developing, securing, and deploying software. Differentiators, as described by Gitlab:
Simplicity: With GitLab, DevSecOps can…
$0
per month per user
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
GitLab
Octopus Deploy
Editions & Modules
GitLab Essential
$0
per month per user
GitLab Premium
$29
per month per user
GitLab Ultimate
$99
per month per user
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
GitLab
Octopus Deploy
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
Optional
Additional Details
—
Octopus 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.
As mentioned earlier, the features like chart visualization sets it apart from the others. Other than that, GitLab is open source while other are not and comparatively more secure that its other counterparts. Also, GitLab supports adding other types of attachments which is not …
When i was using the other platform, Some time i face down time, But GitLabs its not happening for single time. GitLab is having easy user interference as compared to other platforms. Pull Request, Code review, Issue tracking, Merging, Access control and User Roles is having a …
GitLab is miles ahead of the competition. In so many words, having a simple UI with robust security and the ability to conduct Git actions takes the cake. The competitions like to say they can do these things easily but their products are more confusing and hard to use.
GitLab allows a self-hosted version that is easy to setup and configure. It is also open-source as compared to GitHub. The integrated CI/CD tools is a plus, since we do not have to worry about those tools, unlike Github. The All-in-one solution of GitLab made sense for our …
Gitlab offers the best support for CI/CD pipelines and the highest degree of customisation for workflows, permissions, and integrations. The integration of BitBucket with JIRA is better than GitLab but CI/CD features are limited in comparison. GitLab's built-in Container …
Gitlab provides basic functionality like any other git tool. Some features of push and pull requests , clone and merge is handled equally well. It lacks in AI features which are there in GitHub and setup processes are difficult. Cost difference is the only concern while …
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution.
GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" …
It's much simpler than the competitors. The one important feature Gitlab stand out is the CI/CD pipeline. GitHub required integration with external CI tools but Gitlab has this feature built-in. Compare to Jenkins and Teamcity, It's easy to use without any additional Plugins. …
Gitlab seems more cutting-edge than GitHub; however, its AI tools are not yet as mature as those of CoPilot. It feels like the next-generation product, so as we selected a tool for our startup, we decided to invest in the disruptor in the space. While there are fewer …
i have more exoerence in GitLab rather than bitbucket . As personally , it is good for me to understand how things is going on. i have used personally and also in organisation . It is great for developer to see there 3 months ago code and also can come up with new solution to …
Because with Visual Studio code, it was very easy for us to install GitLab in it and have easy access through the terminal and due to GitLab, it was easy to implement codes regarding API and AWS services to make our software better. Gitlens and all features help to check the …
GitLab provides a far superior platform due to it's great integration and CI/CD focus. And while in the beginning the UI might look a bit overwhelming with use you will find it way more useful than it's competitors. The variables and settings also make way more sense and it's …
My feedback may not be important here because when I joined the company they already had GitLab and we still use it due to the ability to do CI/CD Integration, deployments, debugging, code owners approval, and Jira integration. So far we have not had any major blocker that has …
Github is more open-source first and enterprise-first second in their approach. The reverse is true for GitLab. Both are exceptional products and it highly depends on the specific needs of an org
GitLab has a open-source community and great documentation that provides support resources and community contributions. AWS CodeCommit is used for integration with other AWS services in the AWS ecosystem and also have a low community and support compared to GitLab hence …
It was a management decision to use GitLab over other tools. It integrates well with RBAC using Terraform. Runners are easy to setup. Almost all the features the organization used before are available in GitLab.
For small projects or companies that do work on a few only code repositories selecting one of the git code hosting services like GitLab, GitHub, Bitbicket etc does not make a big difference.
But, if you are on a code development company that handles too many repositories and …
Software delivery is the key objective and GitLab made it much easier to hit the group quickly. It worked well with automation, and integrations with other SDLC tools used in the Organization and it is really easy to use. It's widely adopted and has the power to deliver what we …
GitLab's online IDE and code modification is much better compared to Stash. While pricier than Bitbucket, Gitlab also provides CI CD configuration better than BB.
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.
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. …
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 …
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 …
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 …
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 …
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 …
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 …
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 …
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 …
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
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.
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.
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.
I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features
I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
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...
I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version
GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO
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.
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft
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.
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.
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.
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.