Note from the publisher: You have managed to find some of our old content and it may be outdated and/or incorrect. Try searching in our docs or on the blog for current information.

As some of you in the CI/CD and DevOps communities may have seen, Snap CI will be end-of-lifed in August 2017. Snap CI will be providing service and fixing major bugs until then. While they are offering a migration path to GoCD (on-premise), this might not be the right fit for your projects.

Get Started with CircleCI

Getting started with CircleCI is straightforward: more than 75% of CircleCI users are able to get from connecting GitHub or Bitbucket to a green build in 1 hour or less. CircleCI is free to start and gives you one free container (4 GB / 2 CPU) monthly.

Setting up CircleCI usually takes only three mouse clicks:

  • Sign up for CircleCI SaaS or on-premise
  • Give CircleCI permission to access GitHub or Bitbucket on your behalf
  • Click on a project

If this doesn’t work, please check out our documentation or contact our wonderful support desk at

Similarities and Differences

For Snap CI customers who want to get started transitioning to CircleCI, here’s an explanation of some of the key differences and similarities between the two products.


[^1]: Available in closed beta. Closed beta of CircleCI 2.0 also offers native Docker support and support for all tools in the Docker ecosystem. Users can pull containers from any public registry, and build and push images to any public registry. CircleCI 2.0 supports all languages. You can request access to CircleCI 2.0 closed beta here.

Update: As of Jully 11, 2017, CircleCI 2.0 is out of beta and live. Click here to get started.

Why is this so easy?

Our inference engine automatically determines what environment you need by looking at your code and any frameworks you’re using. If you’ve (roughly) followed best practices in your project, then CircleCI will simply work out-of-the-box.