Assembla vs. Beanstalk

Assembla works well when you are working with multiple groups or entities. We dealt with different time zones, different levels of involvement with the projects, etc so this allows for us to have responses back in a quicker fashion. It also helps us clue in the appropriate people and rely less on following multiple email chains

Incentivized

For business or personal applications, where you wish your code to remain private and/or proprietary, Beanstalk could be a good fit. If you are also interested in beginning to automate with relative ease, their tools can be a great help. Code reviews can also be a key factor in the decision, as they provide a good framework for accountability.

Incentivized

• Assembla assists in the workload balancing of our programmers.
• We are able to use Assembla to manage sprints and sprint planning in our agile format.

Incentivized

• Automation
• Code Review
• Support

Incentivized

• The ability to export the tasks or run metrics on them.
• Mobile ability.

Incentivized

• Interface is not always intuitive, some areas are easier than others to navigate.
• Price plans are a little odd. However, they do seem to be flexible if a plan does not quite fit your needs.

Incentivized

We selected Assembla because the ticket functionality worked well with our agile planning format that we use company wide.

Incentivized

If you are creating open source applications, there is almost no reason not to use GitHub. If you do need private repositories (for proprietary or private, business or personal use), Bitbucket could be an excellent solution. Beanstalk's main advantages lie in the support (which is excellent), deployment tools, and code review features.

Incentivized

• We were able to spend less time tracking down the status of projects.
• We could become more self-sufficient on reviewing prior resolutions to help with current problems.
• Tasks were responded to quickly because we did not have to email one person, wait for an out of office email and then try someone else. Our task got assigned to the next available person.

Incentivized

• Increased automation => better accuracy and efficiency of maintenance/launches
• Better insights into ongoing work and past modifications to code => lower chance of error and more efficient troubleshooting

Incentivized