Bitbucket Server, discontinued

Bitbucket Server, discontinued
Formerly Stash

About TrustRadius Scoring
Score 7.8 out of 100
Bitbucket Server, discontinued


What is Bitbucket Server, discontinued?

Bitbucket Server (formerly Stash) from Atlassian offered a self-hosted source code management solution. The product is no longer available for sale, and support for existing licenses will end in 2024.
Read more

Recent Reviews

Read all reviews

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Bitbucket Server, discontinued, and make your voice heard!

Return to navigation


View all pricing

What is Bitbucket Server, discontinued?

Bitbucket Server (formerly Stash) from Atlassian offered a self-hosted source code management solution. The product is no longer available for sale, and support for existing licenses will end in 2024.

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

Alternatives Pricing

What is Bitbucket?

Bitbucket from Australian-headquartered Atlassian offers source code management and version control.

What is GitLab?

GitLab is a complete open-source DevOps platform, delivered as a single application, fundamentally changing the way Development, Security, and Ops teams collaborate and build software. From idea to production, GitLab helps teams improve cycle time from weeks to minutes, reduce development process…

Return to navigation

Product Details

What is Bitbucket Server, discontinued?

Bitbucket Server (formerly Stash) from Atlassian offered a self-hosted source code management solution. The product is no longer available for sale, and support for existing licenses will end in 2024.

Bitbucket Server, discontinued Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Bitbucket Server (formerly Stash) from Atlassian offered a self-hosted source code management solution. The product is no longer available for sale, and support for existing licenses will end in 2024.

Reviewers rate Support Rating highest, with a score of 9.

The most common users of Bitbucket Server, discontinued are from Enterprises (1,001+ employees) and the Computer Software industry.
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings




(1-11 of 11)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Our organization uses BitBucket Server as our primary source control solution, across many different types of software - from front-end to back-end, or even to store configuration and documentation. It allows us to perform code reviews, link changes to Jira tickets, and facilitates enforcement of quality gates - all important in our increasingly remote workforce.
  • Pull requests / code reviews are simple but effective - it's easy to discuss the changes and enforce quality gates (through integration with Bamboo)
  • The access control model is fairly granular, with per-branch and per-action permission configuration options
  • There are various plugins available to extend functionality, such as SonarQube
  • You can't allow users to create new repositories without them being full admins of a whole project
  • There's not a way to limit who can merge a pull request (e.g. allow only the author to merge) outside of branch permissions
  • Some settings like default reviewers can't be easily copied to different repositories (without setting default reviewers at the project level, which we don't want to do because a single project has multiple team's code under it)
BitBucket Server would work really well for small to medium sizes businesses who require a self-hosted code repository. It's less well suited for those who don't want to manage their own infrastructure, and would be better served by something like GitHub or BitBucket Cloud. Additionally we've ran into some small limitations as a large enterprise in regard to some configuration options, and it doesn't allow for zero downtime upgrades for major releases. Finally BitBucket's integration with Bamboo is great, but other automation tools might not integrate quite as tightly.
Score 10 out of 10
Vetted Review
Verified User
Bitbucket is used mainly by the IT Application and Development team plus the IT Developer and Operations team. There are other departments using it, but with minimum interaction. It has helped a lot to produce better code, consistent deployments, testing and great collaboration with all the teams. Since we [started] using it, our internal clients' confidence in IT has improved.
  • Project management
  • Collaboration
  • Testing
  • Integration
  • Better deployments
  • Interface is not intuitive
Bitbucket is well suited for private code repositories. There are tons of excellent integrations, including AWS, Microsoft Azure, Python, Visual Studio, Circle CI. and more. It is well-suited to support individual or team projects.
There are no scenarios where is less appropriate that I can think of, we use it in all our needs successfully.
Oscar Narváez Del Rio | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Bitbucket Server (formerly Stash) is used for some specific development units focused on software development for the business. Bitbucket Server (formerly Stash) has helped the development teams to overcome how they control the coding cycle in a collaborative environment with more than one group of developers working on the same project. Bitbucket Server (formerly Stash) allows the teams to handle the projects themselves and also to organize a portfolio of different products. Bitbucket Server (formerly Stash) is easy to deploy and manage using the internal or managed infrastructure on-premises or cloud servers.
  • Easy deployment and platform management
  • Provides a collaborative framework for development cycle
  • Allow integration with different DevOps and ITSM tools
  • Bitbucket Server (formerly Stash) should be evaluated for implementation based on the capacity of the environment ownership and support.
  • Insights and analytics reports are basic.
  • Bitbucket Server (formerly Stash) as part of Atlassian tools has some restrictions for centralized user management.
Bitbucket Server (formerly Stash) is suitable for departments or teams with the capacity to manage and support their own products and the availability to implement the tool on their own infrastructure. Bitbucket Server (formerly Stash) enables a good framework based on git to integrate the development cycle and to handle anything from a minor group of users and repositories to an extended usage with multiple users and roles collaborating in different projects.
Score 10 out of 10
Vetted Review
Verified User
Bitbucket Server is used as our main code repository for our development team. It is a distributed version control system so developers can still commit and track their changes even when they do not have an internet connection, and push the changes later when they are back online. Its pull request feature also lets developers to collaborate and review each other's work before changes are accepted.
  • Simple and intuitive UI.
  • Pull request for code review.
  • Good integration with other systems such as Jira for issue tracking.
  • Enforce rules on commit message format (although you can get this feature via 3rd party add-on), but this should be an out-of-the-box feature.
  • Lack of reporting and graph features.
Bitbucket and GitHub are the two market leading products when it comes to distributed version control system, or using Git to be specific. You choice is going to come down to what other systems and applications you have in your organization. If you are using other Atlassian applications such as Jira and Bamboo, then Bitbucket would be a better choice due to its deep integrations with them out of the box, and you will get a 1 + 1 > 2 experience.
Never really needed any support as the application is very easy to set up and maintain. Any questions we had were well documented in their online documentation, and community forum.
Score 5 out of 10
Vetted Review
Verified User
Currently, Bitbucket Server (formerly Stash) is being used as the primary version control system in my organization. This means it is being used pretty standardly across both operations and development teams. This also means it is allowing multiple teams to collaborate on code as any version control system would within an organization.
  • Bitbucket is, as far as things go, good at being a version control system. In look and feel, it's very much like GitHub with regard to structure and browsing code.
  • Bitbucket Server has quite a few integrations out of the box that make it pretty quick and not very painful to integrate other systems (Jenkins for example).
  • When restoring from backup, Bitbucket Server does not re-enable plugins that were once enabled. This means anytime you rebuild you are left to either go with enabling all of them or disabling all of them and waiting for other downstream systems to break.
  • Permissions on repositories and projects are not very straight forward. From a user interface perspective, it's a little unclear the first time how to lock down things like pushing to master for some but not others, how to all others to merge pull requests (thus pushing to master) as long as it's not their own change, etc.
  • Reliability is a real problem with Bitbucket Server. Sometimes, for no apparent reason, it will just decide to stop working and require a full restart of the application (which takes a fair bit of time). Being the primary version control system, this means there are quite a few people unable to complete their work while these issues are resolved.
Bitbucket Server would be good to use if you are not extremely reliant on the availability of your code at any given moment. If you have other systems relying on the up status of Bitbucket Server that can cause problems if unable to reach it -- you might consider going with a different product.
I am not the primary administrator of bitbucket so I have never used Atlassian support. As such, I cannot provide an accurate rating.
Dane Allen | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use stash to host our code repositories. We have many different repositories stored on their servers. We also use it to create and manage pull requests and browse individual files and commits to the code base.
  • It picks up changes to your branches immediately.
  • It's very easy to do a diff and compare your branch with another.
  • Pull Requests are very easy to manage. You can set specific requirements so that a branch cannot be merged until a certain criterion is met.
  • I love how easy it is to browse code in the entire repo.
  • Maybe implement a slider on the top of the Pull Request where you could slide between commits to see what was changed (similar to Crucible).
It works great for our large company. We have many different repositories and it handles them all nicely. If you're just doing your own small little project, you'd be better off probably using something like GitHub.
April 13, 2017

Stash for GIT

Score 9 out of 10
Vetted Review
Verified User
We switched to stash from TFS across whole organization due some limitations that we facing at TFS, especially on branching. On top of that, my company is using some of Atlassian's other products as well such as Bamboo, JIRA and Confluence, and we wanted to integrate the process of CD/CI seamlessly so Stash is an ideal choice.
  • Auto merging is one of my favourite features.
  • Deep integration with Bamboo.
  • Deep integration with Bamboo for quality reporting which focus on commit (e.g. build failed)
  • Queryable engine reporting (like JIRA)
  • Guide template for branch strategy
In my opinion, Stash is well suited for all software houses, however you need to plan ahead because if you don't understand how branching works, it will be a disaster when the source code grows bigger.
Score 6 out of 10
Vetted Review
Verified User
Our entire organization uses Stash for all code repositories. We store code in repositories specific to applications. Each department has control over a section of repositories. Some applications are spread across multiple repositories when they have deep collections of dependencies or scripts. We also use the pull requests system of stash for all code changes. Most if not all departments require two approvers for every pull request to be merged.
  • Integrations with HipChat are solid, informative, and easy.
  • Pull requests are easy to comment on, discuss, approve, deny, and merge. It has a very intuitive workflow.
  • It's difficult to create flexible pull requests that might need to be approved by 4 people and others by only 1 person. All pull requests require the same number of approvers
  • Maneuvering through the git-components of Stash to look at particular branches, diff branches, or view tags can be difficult, tedious, or impossible. Direct support for some more advanced git actions would be appreciated.
  • There is no readme concept (like in GitHub) for a repository.
Stash is good if you can incorporate it into other Atlassian products, and it is certainly acceptable for simple operations, but it is not as good as other products out there such as GitHub or Gitlab. Stash has nothing to truly separate itself from the crowd apart from its integrations with the rest of the suite of Atlassian products.
Alexandre Amantea | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Stash is being used to handle pull requests from JIRA issues into our development and production branches. Also, it is configured to run builds for java applications whenever a pull request is accepted into development branch. It has a nice and easy UI. Also used to create branches directly if not attached to a JIRA issue. Its integration with JIRA is the big plus of this product.
  • Integration with JIRA
  • Easy to use
  • Review and accept code changes
  • More free plugins
  • Hooks examples
  • Better control of branches parents
Stash is well suited for integration with JIRA. Control code changes in small or large teams is made very easily with Stash. You can assign code reviewers that will be responsible for the code merge. Its integration with JIRA made things very easy and productive. Using JIRA and STASH you are just a few clicks from submitting your code.
Advait Deshpande | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Stash is used primarily for version control of different modules of codes within various teams at Fidelity Investments. Ours is a cross functional team geographically located in different time zones. The development team works on a piece on code, pushes the code onto the Stash server, which is then pulled by the testing team for review. Upon final approval, the release engineering team pulls the code from server and moves across various environments. Continuous availability of correct version of code is big business problem that gets solved because of the usage of Stash.
  • Projects & Permissions - Stash keeps you and your developers productive by providing a way to structure your repositories and manage permissions via a simple, yet powerful user interface. Stash is very easy to use, manage & administer.
  • Essentially Stash gives two versions of interfaces to work with.
  • Stash Repository hosted on a server.
  • Atlassian SourceTree.
  • Atlassian Sourcetree is a tool to work with a code in stash. The two 'web' and 'desktop' versions make working with code user friendly, intuitive and comprehensive.
  • Connectivity to JIRA - Stash keeps track of all issues associated with commits. Users can use Stash to quickly see all issues associated with a commit, or use the Source tab on JIRA issues for an aggregate view of all the code changes that are related to a specific JIRA issue. With this information available, your development team saves time when tracking particular bug fixes or improvements.
  • I feel Stash should allow direct download of the entire folder containing various files of code. It is cumbersome to go inside a folder to download an sql file and then come back to the folder to download another.
  • With respect to security password syncing between Stash & Sourcetree, there should be a mechanism of automatic syncing of passwords. In urgency if I need to download a piece of code and pull doesn't work simply because the authentication fails.
  • Sometimes Stash gives problems while pulling files with long file names. I feel this can be addressed and there should not be any such restriction.
Version control is a must these days with the amount and complexity of code continuously increasing at workplace. A scenario where an approver has to approve a piece of code, an analyst needs to compare two different commits and an end user simply wants to download and replicate an entire repository of code, Stash is very useful for it's intuitive interfaces, clean description of error messages and segregation of staging and non staging areas for files. I don't see a scenario where you cant make use of Stash in a software team setup.
Darian Rawson | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
We use Stash locally for projects that we just don't want hosted elsewhere. It gives our clients peace of mind, as well as gives our developers the tools they need for developing. Stash is very similar to the hosted Bitbucket, and recently was pivoted to be more in line with that service, however it is extremely easy and straightforward for a small agile team to host Stash compared to other options.
  • Version Control Environment.
  • Easy set up and maintenance.
  • It is really really reasonably priced!
  • The features aren't in parity with Bitbucket, but are getting better.
  • Upgrading to new versions of Stash.
  • Solving technical issues that pop up from time to time can be confusing.
Stash is well suited when you want to locally host repos and manage your team without having to manage everything from a terminal. It works well for small teams with big clients that don't want their code hosted off site. This can make auditing and other processes for contract negotiation doable for teams that can't host things outside of their development environment.
Return to navigation