Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

What makes Deveo different GitHub, GitLab, or BitBucket?


Published on

There are a lot of different software configuration management (SCM) tools out there. When you are choosing a right platform, you need to know how one tool differs from another.

Since Deveo is still a rather new player in the field, we decided to open the key differences between Deveo and GitHub, GitLab, and BitBucket in this slide deck.

We covered the same topic in our blog post more thoroughly:

The best way to find out the differences is, of course, to sign up to Deveo! Get your free lifetime use of Deveo here:

Published in: Software

What makes Deveo different GitHub, GitLab, or BitBucket?

  1. 1. What makes Deveo different from GitHub, GitLab, or BitBucket?
  2. 2. Deveo? Deveo is a code management and collaboration platform that supports Git, Subversion, and Mercurial. You can install Deveo on- premise or use it directly from the cloud. Deveo's cloud version is natively multi-tenant, so your code is always private and secure. In addition to code hosting, Deveo offers code reviews, issue tracking and documentation capabilities.
  3. 3. Sounds just like another SCM tool. How is it different?
  4. 4. Reason 1
  5. 5. Enterprise level needs differ from the open source community needs. • Privacy is priority no. 1 • Multiple version control systems in use • Legacy source code
  6. 6. Deveo’s background is in building SCM solutions for some of the biggest companies in the world. Those learnings have been implemented in Deveo, and scaled to meet the needs of all-sized teams.
  7. 7. Reason 2
  8. 8. A bunch of awesome features that others lack! Such as:
  9. 9. Multi-tenancy In Deveo, users are always added to a private company-specific space, to which they log in. In other services: Users have access to the whole service, which is limited by “organisations” and repositories.
  10. 10. Benefits of multi-tenancy • IPRs are safe and secure • User accounts are always company specific • No ambiguous user names like “Excalibur2000” or “powercowboy1986” • Removing employees is easy • Once the user is removed from the company- specific space, all access is revoked
  11. 11. SAML 2.0 configuration for each company Deveo allows you to authenticate against your organisation’s SAML 2.0 based SSO provider. • Limit Deveo usage to only those users who are in the organisation’s user directory • Deveo automatically creates the user account upon successful authentication against the SAML 2.0 identity provider.
  12. 12. Customisable issue management Define issues’ states and priorities according to your own preferred workflow. In other SCM tools, the states and priorities are given, and cannot be altered.
  13. 13. Support for multiple version control systems Native support to not only Git but also to Subversion and Mercurial.
  14. 14. Multiple repositories in one project In Deveo, you create a project and multiple repositories under the project, which also includes the shared issue tracking and wiki. This allows you to have e.g. front-end and backend repos in on project and access all the project related information from one place.
  15. 15. WebDAV repositories WebDAV is a cross-platform network share that works seamlessly in Windows, OSX and Linux alike. Use it to store all of the files that you shouldn’t put into your version control systems, such as: • Release binaries • Large graphical assets
  16. 16. Various account types External Collaborators with limited access rights Need to invite a user from outside your organisation to your development environment? Use Deveo’s collaborator accounts, which have no visibility outside of the project scope they are added. Bot Accounts When you want to integrate an external tool, (e.g. CI or CD servers) with your SCM, you shouldn’t use your personal credentials. Bot accounts are non-user accounts that can be used to allow programmatic access to different components of Deveo, so the ownership can be shared.
  17. 17. Triggering repository hooks based on reference and file patterns Notify your team chat tool, such as Slack, HipChat or Flowdock about new commits only to your main branch, or start different automation runs based on the branch. With file patterns, you can notify about changes to release notes or trigger certain builds if, for example, migration scripts have changed.
  18. 18. Support for Android open- source projects With Deveo, it is possible to setup and host a mirror for the android open-source project repositories without any additional modifications to any configuration files. In, or this would require complex modifications.
  19. 19. Reason 3
  20. 20. Flexible and responsive team As a small company, we listen our potential and existing customers carefully. Our roadmap is created together with our customers, and they have a real say in the features we develop.
  21. 21. Want to share your thoughts with us? Pick your preferred channel: @deveoteam deveoteam