CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.
$0
for up to 6,000 build minutes and up to 5 active users per month
GoCD
Score 8.0 out of 10
N/A
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.
N/A
Vultr
Score 8.8 out of 10
N/A
Vultr is an independent cloud computing platform on a mission to provide businesses and developers around the world with unrivaled ease of use, price-to-performance, and global reach.
$2.50
per month
Pricing
CircleCI
GoCD
Vultr
Editions & Modules
Server
Contact Sales
Performance
starting at $15
per month
Scale
starting at $2000
per month
No answers on this topic
Block Storage
$1
per month
Cloud Compute
$2.50
per month
Object Storage
$5
per month
Kubernetes Engine
$10
per month
Load Balancers
$10
per month
Managed Databases
$15
per month
Optimized Cloud Compute
$28
per month
Cloud GPU
$90
per month
Bare Metal
$120
per month
Offerings
Pricing Offerings
CircleCI
GoCD
Vultr
Free Trial
No
No
No
Free/Freemium Version
Yes
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
Pricing is based on specifications chosen in each product category. Bandwidth is also included up to a certain amount per month.
Based on our experience, CircleCI is well-suited for automating mobile app release cycles. For example, to release an iOS app, you would need to build, sign, and upload it to TestFlight, which requires a dedicated Mac in the office. But with CircleCI, you can have macOS executors, so you don't have to manage a physical build machine. Another benefit is that CircleCI's certified AWS Orbs abstract away complex authentication and deployment logic, allowing us to build, push, and deploy Docker containers to Amazon ECS with minimal configuration and high reliability. CircleCI is less suited for smaller projects where the development and deployment are not that extensive, for example, a static site. Once you have built a static site, you probably won't make any further changes, so there's no point in paying for it.
Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
I've been with Vultr over 5 years hosting multiple businesses and email related services. I never experienced a significant outage or data loss. Migration has always been successful as well. Support is top tier and IP reputation is clean. I like the choices of OS, ease of platform use and multiple hosting/ region options.
Automated builds! This is really why you get CircleCI, to automate the build process. This makes building your application far more reliable and repeatable. It can also run tests and verify your application is working as expected.
Simple. Unlike Jenkins, Teamcity, or other platforms, CircleCI doesn't need a lot of setup. It's completely hosted, so there's no infrastructure to set up. The config file does take a bit to understand, but if you follow their example and start with something small and add to it, you can get it up and going quicker than it first looks.
Scales easily. Again, since it's all cloud-based, you don't have to manage or scale infrastructure. Simply subscribe to the number of containers you want, and scaling up just means buying more containers.
Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
Just a great product with no bells and whistles, which is the advantage. We spend very little time learning and using Vultr and more time using the systems we have in Vultr to complete our tasks. Not having to worry about the IT overhead is huge and saves a great deal of time
The reliability & speed, it just works. The ability to spin up macOS runners and Docker containers on demand without managing hardware is a huge win. The Orbs system makes integrating with AWS and Slack incredibly easy, saving us weeks of custom scripting and providing real-time updates in our Slack channel. This makes it easy for us to track and ensures that everyone involved knows the status. Of course, it has drawbacks related to configuration complexity and, in some cases, cost transparency, but overall, it is an industry-standard, robust tool that solves our core infrastructure problems well.
easy to use and configure. great bang for the buck. I need an affordable solution to host in the cloud data from systems installed at our client's site with the ability to drill down and change the configuration remotely. Vultr enabled us to do that in an efficient and affordable way.
It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
Unless you have a reasonably large account, you're going to be mainly stuck reading their documentation. Which has improved somewhat over the years but is still extremely limited compared to a platform like Digital Ocean who invested in the documentation and a community to ensure it's kept up to date. If you can't find your answer there, you can be stuck.
Vultr makes it easy to contact technical support. The techs are very competent. In a number of occasions they have bounced the responsibility back to me when they could have saved us all time and heartache by simply implementing the solution directly
Vultr implementation seemed based on open-source tools and basic cloud principles - some things were more complicated to do compared with more developed cloud providers, but on the other hand it was more extensible by open-source tools.
Jenkins is usually self-hosted, Travis CI's infrastructure is largely unreliable (lots of tests time out for no discernable reason), and Semaphore encourages you to configure your CI/CD from a web UI. We like CircleCI because its hosted, our tests run largely as expected on their infrastructure, and we can configure it from a config file that we track in GitHub.
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
Linode is a more old-school offering. Linode pricing model and infrastructure rely on classic Virtual Machines. What we like about Vultr is that they offer the same at the front, but in the back, the machines are much more flexible and can be tailor-made to our needs, which of course also impacts the costs of running the infrastructure.
We pay over $5K/ month and we have high expectations for service. Sometimes I feel that we don't get the value, but only sometimes.
We have had to build our own application to keep state and broker releases and deployments. We call our app deployer. I feel that CircleCI could do more to understand our needs and possibly build additional features that would enable us to invest less in build and deployment infrastructure and justify paying more for Circle.
Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date
