Buddy (formerly Springloops) is a SVN/Git source code management tool focused on web development teams. It allows users to code in parallel and share code safely concentrating on results, not on lost changes or overwritten files. With quick deployments, users get rapid collaboration in protected space.
$75
per month
Heroku Platform
Score 8.0 out of 10
N/A
The Heroku Platform, now from Salesforce, is a platform-as-a-service based on
a managed container system, with integrated data services and ecosystem for deploying modern apps. It takes an app-centric
approach for software delivery, integrated with developer tools and
workflows. It’s three main tool are: Heroku Developer Experience (DX), Heroku
Operational Experience (OpEx), and Heroku Runtime.
Heroku Developer Experience (DX)
Developers deploy directly from tools like…
$85
per month
Pricing
Buddy
Heroku Platform
Editions & Modules
Free (for freelancers)
$0
per month
On-premises (for teams)
$35
per month per user
Pro (for teams)
$75
per month
Hyper (for teams)
$200
per month
Production
$25.00
per month
Advanced
$250.00
per month
Offerings
Pricing Offerings
Buddy
Heroku Platform
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Buddy
Heroku Platform
Features
Buddy
Heroku Platform
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
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.
Heroku is very well suited for startups looking to get a server stack up and running quickly. There is little to no overhead when managing your instances. However, you'll need a background in basic DevOps or system management to make sure everything is set up correctly. In addition, it's easy to accidentally go crazy on pricing. Make sure you're only creating the server instances you need to run the base application and set up an auto-scaler plugin to handle peaks.
Heroku has a very simple deployment model, making it easy to get your application up-and-running with minimal effort. We can focus on our efforts the unique aspects of our application.
The robust add-on marketplace makes it easy to try out new approaches with minimal effort and investment -- and when we settle on a solution, we can easily scale it.
Heroku's support is quite good -- their staff is quite technical and willing to get into the weeds to diagnose even complicated problems.
Large price jumps between certain resource tiers (2x Dyno for $50 per month versus Performance Dyno for $250). Free Postgres next jumps to $50 per month.
Marketing/Branding to non-technical stakeholders. As the years pass, I've had to fight more to convince stakeholders on the value of Heroku over AWS.
Improve Buildpack documentation. This is one area where Heroku's documentation is fairly confusing.
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.
Heroku is easy to use, services a ton of functions for you out of the box, and provides a means to get a software product off the ground and managed quickly and easily. The tools provide allows a small to medium size org to move very quickly. The CLI tools provided make managing an entire technical infrastructure simple.
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
Easy to use web based console and easy to use command line tools; deployment is done directly from a GIT repository. What more could you ask for? The one thing that keeps me from giving it a 10 is that custom build packs are almost incomprehensible. We used one for a while because we needed cairo graphics processing. Fortunately, I was able to figure out a different way to do what we needed so that we could get off the custom build pack.
Heroku availability correlates pretty strongly to AWS US EAST availability. We had a couple of times where there was a Heroku-specific issue but not for the last 7-8 months.
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
I've used it for many years without facing any major problem. It's not hard at all to get used to it, it's documentation is outstanding and simple. We are close to 2020 and I don't think most of the existing companies or startups should still face old problems such as wasting time deploying code and calculate computing resources.
Be ready to pay a bit more than expected in the beginning if you're migrating from a big server. The application is probably not ready for the change and you have to keep improving it with time.
It's also important to consider that you can't save anything to the disc as it will be lost when your application restarts, so you have to think about using something like S3.
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.
Heroku is the more expensive option for hosting compared to some of the cloud platforms we investigated, but it's worth it for us because of the plug-and-play nature of Heroku deployment. We can be up and running in a few minutes and know with precision how much it will cost us each month to run the application, unlike Amazon Web Services where you have to go to great pains to configure it correctly or else you might end up with a shocking monthly bill. Overall, spending the time to configure Amazon Web Services or one of its competitors is likely the more affordable and powerful choice, because you have control over so many specifics of the configuration. But it also requires the burden of continuing to maintain and update your AWS instance, whereas with Heroku they take care of security fixes and platform upgrades. It's a great service and we are happy to pay the extra cost for the value-adds Heroku provides.
