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
Pantheon
Score 9.8 out of 10
N/A
Pantheon is a WebOps platform where marketers and developers collaborate to drive results. The vendor states that with Pantheon, site owners maximize their capacity to update website design and functionality, responding to market trends, catering to consumer behavior, and adding real value to the business's bottom line. Today, companies compete on the basis of digital experiences, and the best results emerge from an agile build-test-learn process. Whether it's publishing content,…
$29
per month
Upsun
Score 9.9 out of 10
N/A
Platform.sh helps companies of all sizes, from SaaS entrepreneurs looking to build, run, and scale their websites and web applications.
Acquia was terrible. We use DigitalOcean for some all-purpose computing needs and Platform.sh for an application that does more computing and high-throughput processing where we do not want page views (API calls) to count against our usage.
We use several hosting solutions depending on the client needs or what they were already setup on. Pantheon is very similar to them and offers similar services however one of the main features we use is the Multidev service which allows us to test pieces of work separately and …
In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. …
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.
Pantheon is excellent for medium-large websites that require high availability and a managed workflow. It would be inappropriate for small websites because of the cost or for situations where more control of the environment is appropriate. We find it useful because we rarely do anything outside of the Drupal application.
In our organisation we are the only team that uses Platform.sh to host any site. This was a cost effective way for us as we were using Acquia Cloud earlier for these websites. We mostly use Platform.sh for those sites which are always in development as it is simpler and faster to handle these operations in Platform.sh. Then we do a lift and shift to Acquia as we move more towards the go live and post production maintenance side.
Platform.sh is not for beginners in my opinion. It has a good amount of learning curve in my opinion.
As this is a PaaS, teams habituated with cloud infrastructure may miss the server side support from their cloud teams. I believe you will have to work on server bugs more on your own.
During normal maintenance periods, integrations may fail if you are working on your sites in that time, in my experience.
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.
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
Pantheon is an easy system, especially to the users with previous experience with other similar platform and the interface is clear enough to easily understand how things operates. On the Cloud deployment everything also works effectively and the technical team from Pantheon community are very helpful on providing the necessary assistant to their customers.
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
Even tier 1 Pantheon chat and ticket support are knowledgeable, competent, and useful. They routinely understand and promptly resolve urgent, complex, and/or unusual issues that other hosts need to escalate to tier 2 or tier 3 support personnel. I honestly can't think of a truly negative or disappointing support experience in the years I've used Pantheon hosting for client websites.
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.
Although it may seem a good fit for a company that needs extra control over the deployment process and development process, for a firm that is mainly concentrating on SEO, it would be an overkill. Pantheon provides that sweet automation that allows us to shed some weight on development and focus on our business activities.
In our team we use Platform.sh mostly while sites are in developmental phase. Then we do a lift and shift to either Acquia or AWS depending on the type of sites we have. Platform.sh is really cost effective and more fluid in terms of Continuous Development hence the usage. After said development is done, we generally lift and shift to Acquia for more content heavy sites and to AWS for more transaction oriented sites.