Bitbucket Server (discontinued) vs. Perforce P4

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Bitbucket Server (discontinued)
Score 6.0 out of 10
N/A
Bitbucket Server (formerly Stash) from Atlassian was a self-hosted source code management solution. The product is no longer available for sale, and support for existing licenses ended in 2024.N/A
Perforce P4
Score 7.6 out of 10
N/A
Perforce P4 (formerly Helix Core) is the company's version control and peer code review solution. Perforce offers add-on products for code review for free, and Git support products.N/A
Pricing
Bitbucket Server (discontinued)Perforce P4
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Bitbucket Server (discontinued)Perforce P4
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Bitbucket Server (discontinued)Perforce P4
Considered Both Products
Bitbucket Server (discontinued)
Chose Bitbucket Server (discontinued)
We migrated several of our applications to BitBucket from legacy Team Foundation Server, and the experience has been significantly better. It's easy to use and plenty flexible. Other solutions such as GitHub are also good, but we needed to keep everything on-prem due to …
Chose Bitbucket Server (discontinued)
Bitbucket Server (formerly Stash), as part of Atlassian products, provides a native integration framework and tools for automation. The platform supports git and mercurial repositories and provides features to export and import repositories from other projects. Migration to the …
Chose Bitbucket Server (discontinued)
In our specific scenario and company goals, we chose Bitbucket because it has better integration with other Attlassian products and cost / benefit.
Chose Bitbucket Server (discontinued)
We started off with Apache Subversion (SVN) and moved over to Git (supported via Bitbucket) as Git itself has started to become the new industry norm. The pull request feature allows developers to perform code reviews without needing another code review application. We settled …
Chose Bitbucket Server (discontinued)
If you are selecting a product to use and you are not currently using version control, it may be in your best interest to choose another tool. Bitbucket Server is not as feature rich and doesn't feel as mature as some other platforms and arguably, with the lost production from …
Chose Bitbucket Server (discontinued)
Stash works better for hosting large repositories used across an enterprise.
Chose Bitbucket Server (discontinued)
GitHub, Team Foundation Server, Visual SourceSafe and Bitbucket
Chose Bitbucket Server (discontinued)
Stash was selected before I was at the company, but we're looking at these alternatives and actively considering switching. Stash seems to have all the necessary features we need to make it work, but it doesn't have any bells and whistles or extra special features that we can …
Chose Bitbucket Server (discontinued)
It can be daunting to set up a Git server for a developer. Managing it can be more time consuming than you want it to be. Stash helps you out by handling what you likely need. If you are already a Git pro, you won't need it, but our team loves the simplicity that Stash brings …
Perforce P4
Chose Perforce P4
In my opinion, Perforce Helix Core is on a top level of irritation and anti-user experience. In my experience, I can't do simple things like 1 word file edits, while I have never been confused when using something based on Git.
Chose Perforce P4
Git is great, I love Git. But it's not great for dealing with binary assets, even when using git LFS. Locking is not as simple as on perforce. Git presents some problems on using for non-tech people it can get overwhelming and tech people have to come by and help.
Chose Perforce P4
I am only starting with BiBucket and do not yet have sufficient experience to draw upon for comparison.
Chose Perforce P4
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that …
Chose Perforce P4
My last two jobs used SmartSVN but it required a paid license to use regardless of the number of users. The initial setup for Perforce was much more difficult than SmartSVN. There is a lot of parity between the two software packages even though the terminology can be different. …
Chose Perforce P4
Perforce has a better built native visual client that is much simpler to use than Git's. It has a lot of optimizations in the workflow that can execute common patterns during a usual workday. Perforce also has an easier to understand method of presenting merge conflicts and …
Chose Perforce P4
Perforce is internally hosted, which makes it quite a bit faster. I found it easier to use that GitHub and Bitbucket, at least in terms of checking out files and creating changelists. GitHub and Bitbucket are much better for smaller teams, as they are cloud hosted, making …
Chose Perforce P4
Today's web based software makes them easier to integrate into a development process. Jira with integrated BitBucket as the versioning tool, is ahead of the competition. However for large organizations, Perforce is still a very good choice. GitHub can be used as free tool, but …
Chose Perforce P4
Subversion
  • missing many of the features that Perforce provides, but
  • a much more lightweight versioning system
Chose Perforce P4
Perforce has more features than SVN. However even the simpler tasks in SVN require a degree more technical aptitude with Perforce. Git offers most of the same features, however most of these are only really supported via the command-line in Git, where as most tasks can be …
Chose Perforce P4
Perforce is similar to SVN but the SVN has better command line support. Git surpasses both SVN and Perforce because of its flexibility with multiple branches and code review.
Features
Bitbucket Server (discontinued)Perforce P4
Version Control Software Features
Comparison of Version Control Software Features features of Product A and Product B
Bitbucket Server (discontinued)
-
Ratings
Perforce P4
7.9
Ratings
4% below category average
Branching and Merging00 Ratings8.00 Ratings
Version History00 Ratings8.00 Ratings
Version Control Collaboration Tools00 Ratings8.00 Ratings
Pull Requests00 Ratings8.00 Ratings
Code Review Tools00 Ratings8.00 Ratings
Project Access Control00 Ratings8.00 Ratings
Automated Testing Integration00 Ratings8.00 Ratings
Issue Tracking Integration00 Ratings7.00 Ratings
Branch Protection00 Ratings8.00 Ratings
Best Alternatives
Bitbucket Server (discontinued)Perforce P4
Small Businesses
Git
Git
Score 10.0 out of 10
Git
Git
Score 10.0 out of 10
Medium-sized Companies
Git
Git
Score 10.0 out of 10
Git
Git
Score 10.0 out of 10
Enterprises
Perforce P4
Perforce P4
Score 7.6 out of 10
Git
Git
Score 10.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Bitbucket Server (discontinued)Perforce P4
Likelihood to Recommend
8.9
(0 ratings)
6.5
(0 ratings)
Likelihood to Renew
10.0
(0 ratings)
6.6
(0 ratings)
Usability
5.0
(0 ratings)
7.0
(0 ratings)
Availability
-
(0 ratings)
9.0
(0 ratings)
Performance
-
(0 ratings)
6.0
(0 ratings)
Support Rating
9.0
(0 ratings)
9.6
(0 ratings)
Implementation Rating
-
(0 ratings)
7.0
(0 ratings)
User Testimonials
Bitbucket Server (discontinued)Perforce P4
Likelihood to Recommend
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.
Read full review
For large-scale codebases with fixed and regular releases that do not follow a continuous delivery paradigm, Perforce is certainly well suited. In projects that are small and distinctly separated from other discrete (though potentially dependent) units, the benefits of the Perforce tool may not be as clear of a victor over other systems.
Read full review
Pros
  • 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.
Read full review
  • Merge algorithm is smart and utilizing the visual interface to do merges makes them easier to digest.
  • Easy to set up on multiple platforms and architectures and is well supported on all of them.
  • Visual interface has many tools and customization options that help to optimize and personalize workflow.
Read full review
Cons
  • 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)
Read full review
  • I was having a hard time learning it. Even if you are an experienced developer, there is some learning curve.
  • Can be slow when working with large data sets at once.
  • When working on multiple workspaces on the same machine, Perforce can make it difficult not to mess up the code.
Read full review
Likelihood to Renew
Because we're so locked in, it's likely we'll be using Bitbucket Server for a while, unfortunately.
Read full review
We have a need to consolidate into a single package, and have such a large variety of technical proficiency among our users that Perforce seems less suitable. Many would like to remain using it, however, even those who use Perforce are the minority, and are often limited to our development teams.
Read full review
Usability
The usability of its interface is pretty straight forward when it comes to creating projects and repositories, but when you have to dive into finer grained portions of the UI things can get tricky. If you are used to using tools like GitHub or Gitlab -- Bitbucket is just different enough to be a bother.
Read full review
With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!
Read full review
Reliability and Availability
No answers on this topic
In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.
Read full review
Support Rating
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.
Read full review
I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.
Read full review
Implementation Rating
No answers on this topic
This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.
Read full review
Alternatives Considered
We migrated several of our applications to BitBucket from legacy Team Foundation Server, and the experience has been significantly better. It's easy to use and plenty flexible. Other solutions such as GitHub are also good, but we needed to keep everything on-prem due to constraints around our industry and company, though we are currently re-evaluating whether we can move to something cloud based in the future.
Read full review
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that requires hours to pull together that would take me less than 30 seconds in Perforce Helix. Large file storage in Bitbucket is clunky and requires you to jump through too many hoops. It's not even something you have to think about with Perforce Helix, as you are only limited by your OS. Perforce Helix is very easy to use even for non-developers. I wouldn't dare ask a non-developer to store their documentation in Bitbucket.
Read full review
Return on Investment
  • In positive form, having Stash over not having it at all has provided us with a superior repository system over trying to push to some local server instance and manage branches/merging from our local machines.
  • There are no real negatives to using Stash, its only problem is that there are competitors out there that can offer additional features.
Read full review
  • Locking assets make us have no merge problems which are harder to manage on other versions control without locking
  • Almost no need to give support to artists or non-tech folks because the operations are very straightforward
  • There's no way to do interim checkins without going to the process of creating a stream
Read full review
ScreenShots