What users are saying about
3 Ratings
76 Ratings
3 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 10 out of 100
76 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 9.5 out of 100

Attribute Ratings

  • Buddy is rated higher in 3 areas: Likelihood to Recommend, Usability, Support Rating
  • Buddy and Git are tied in 1 area: Likelihood to Renew

Likelihood to Recommend

10.0

Buddy

100%
1 Rating
9.0

Git

90%
35 Ratings

Likelihood to Renew

10.0

Buddy

100%
1 Rating
10.0

Git

100%
1 Rating

Usability

10.0

Buddy

100%
1 Rating
9.0

Git

90%
1 Rating

Support Rating

10.0

Buddy

100%
2 Ratings
8.5

Git

85%
22 Ratings

Implementation Rating

Buddy

N/A
0 Ratings
9.0

Git

90%
2 Ratings

Likelihood to Recommend

Buddy (BDY, Sp. z o. o. Sp. k)

Springloops is the best tool for deployment to any environment. Especially, the auto-deployment feature on development servers is essential for the early stages of development. The built-in source control mechanisms are a perfect combination of ease of use and a rich feature set that allows the development team to have an easier and more complete view of each part of the project. A section that is lacking is time tracking - but then this is not the main usage of the service.
Read full review

Open Source

GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
Read full review

Pros

Buddy (BDY, Sp. z o. o. Sp. k)

  • Easy of use - clear user interface
  • Fast deployment to all environments
  • Great combination of source control and project management
Read full review

Open Source

  • Ability to create branches off current releases to modify code that can be tested in a separate environment.
  • Each developer had their own local copy of branches so it minimizes mistakes being made.
  • Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
  • Conflicts are displayed nicely so that developers can resolve with ease.
Read full review

Cons

Buddy (BDY, Sp. z o. o. Sp. k)

  • We would love to have a more flexible management for resources (users, storage)
  • More advanced web hooks would be a plus
Read full review

Open Source

  • There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
  • Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
  • Many different GUIs, many people (including myself) opt to just use the command-line.
Read full review

Pricing Details

Buddy

Starting Price

$75 per month

Editions & Modules

Buddy editions and modules pricing
EditionModules
Free (for freelancers)01
Pro (for teams)$752
Hyper (for teams)$2003
On-premises (for teams)$354

Footnotes

  1. per month
  2. per month
  3. per month
  4. per month per user

Offerings

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services

Entry-level set up fee?

No setup fee

Additional Details

Git

Starting Price

Editions & Modules

Git editions and modules pricing
EditionModules

Footnotes

    Offerings

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services

    Entry-level set up fee?

    No setup fee

    Additional Details

    Likelihood to Renew

    Buddy (BDY, Sp. z o. o. Sp. k)

    Apart from being a great versioning control system Springloops offers the options to automatically deploy code to multiple systems. This feature alone is a determining factor to renew Springloops over and over again. Another important factor is that it offers a full set of tools that help the team during the development cycle. No switching between time-tracking to project management. This is a real time-saver.
    Read full review

    Open Source

    Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
    Read full review

    Usability

    Buddy (BDY, Sp. z o. o. Sp. k)

    Easy to use, automatic deployments, comments on projects are only a few factors. Multiple servers per project is another must-have feature. User permissions and rights offer granular control on access to the system
    Read full review

    Open Source

    Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.
    Read full review

    Support Rating

    Buddy (BDY, Sp. z o. o. Sp. k)

    I rarely use it but when I need it the team is there. During the initial steps of Springloops, I had close contact with one of the founders. He provided support to me over Skype! He didn't have to but he did. We had a couple of long talks about some issues I was facing. He has there regardless of time. It was a great experience
    Read full review

    Open Source

    I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
    Read full review

    Implementation Rating

    Buddy (BDY, Sp. z o. o. Sp. k)

    No answers on this topic

    Open Source

    It's easy to set up and get going.
    Read full review

    Alternatives Considered

    Buddy (BDY, Sp. z o. o. Sp. k)

    Springloops has a built-in feature that is lacking from Bitbucket (at least on the out-of-the-box functionality). Deployment of projects to various servers/development stages. The process is so easy and painless that even remote servers can act as local environments. This is a feature that differentiates Springloops from other solutions that require other tools to perform the same task.
    Read full review

    Open Source

    I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
    The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
    It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
    Read full review

    Return on Investment

    Buddy (BDY, Sp. z o. o. Sp. k)

    • A total time saver - just commit changes and Springloops can handle the deployments
    • Total control of source code and commits - you never have to think about those things again
    Read full review

    Open Source

    • Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
    • Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
    • Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
    Read full review

    Add comparison