
Overview
CircleCI's leading continuous integration and continuous delivery platform enables teams to deliver quality code, quickly.
CircleCI is SOC II and GDPR compliant, and FedRAMP certified and supports Windows, Linux, Docker, and macOS, and runs in the cloud or behind your firewall. Teams can orchestrate complex workflows to move code through their ideal delivery pipelines with one of our usage-based plans in the Cloud (managed by CircleCI) or our Server plan (self-hosted by you).
Managed by CircleCI in our multi-tenant SaaS on CircleCI: Custom Plan - access to all premium resource classes, unlimited concurrency, optional 24x7 Premium Support available Scale Plan - access to hybrid Runners, all premium resource classes, unlimited concurrency, optional 24x7 Premium Support available
Managed by you with our support: Self-Hosted - run CircleCI within your AWS VPCs, Kubernetes-based install on EC2 or EKS, includes 24x7 Premium Support - Silver (optional upgrades available)
To discuss any of the available or customized packages, please contact AWS-Marketplace@circleci.com .
Highlights
- Incredible performance - the speed and reliability you need when building, testing, and deploying code. Choose the resources you need for optimal performance.
- Complete control and scale - everything great teams need to delivery quickly and confidently with unlimited scale. Never wait for a build server to be available again!
- Unmatched security - the CircleCI hosted CI/CD platform is both FedRAMP-authorized and SOC-2 compliant, providing peace of mind to companies in every industry.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Description | Cost/12 months |
|---|---|---|
Scale Plan | Scale: custom credits, custom # of users, custom concurrent job runs | $24,000.00 |
Custom Plan | CircleCI Custom Plan | $6,000.00 |
The following dimensions are not included in the contract terms, which will be charged based on your usage.
Dimension | Cost/unit |
|---|---|
Usage Credits Refill @ $0.0006 per credit (charged in increments of 10) | $0.006 |
Vendor refund policy
No refunds provided. For inquiries, please contact AWS-Marketplace@circleci.com .
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Automated container builds have accelerated our Go deployments and simplified AWS workflows
What is our primary use case?
My main use case for CircleCI involves different CI capabilities, mostly building containers and general applications. I use CircleCI for building containers and applications, specifically for our GoLang application. We have an ECS application written in GoLang which runs scans against the infrastructure. Regardless, it is completely built and managed. The configs are also stored in Bitbucket , and CircleCI is connected to it, running all the builds, processes, and deployment in the end to the ECS.
What is most valuable?
The best features CircleCI offers are probably the modules, which have great extendability. I use the modules or extendability in CircleCI primarily for classic pushes to AWS , and those include registry sign-ons and other cases.
CircleCI has positively impacted my organization by allowing us to build quicker and do things quicker. It does the job really well. These extensions are called Workflows. I have used some AWS Workflows, and there are multiple others.
CircleCI helps you build and do things quicker. It is difficult to say if there were specific improvements, but there is general reliability and probably improvements overall.
What needs improvement?
I have no idea how CircleCI can be improved. I am a user, not a developer of CI tools. I do not really have anything to add about the needed improvements, even small things that could make my experience better.
For how long have I used the solution?
I have been using CircleCI for around a year.
What do I think about the stability of the solution?
CircleCI is stable.
What do I think about the scalability of the solution?
CircleCI's scalability is great. I have never had any problems with it.
How are customer service and support?
I did not deal with CircleCI's customer support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I previously used multiple solutions. The very first one was GitLab , but it was just an experiment, because there are quite a few limitations that we had with GitLab , so we had to switch.
What was our ROI?
I cannot say if I have seen a return on investment. It is very difficult to tell.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that I only used CircleCI on the free tier.
Which other solutions did I evaluate?
Before choosing CircleCI, I evaluated other options, specifically Jenkins .
What other advice do I have?
My advice for others looking into using CircleCI is to read more documentation. The documentation is really good. I would rate this review an 8.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automated pipelines have accelerated deployments and dashboards now reveal clear pricing and security gaps
What is our primary use case?
For a specific example of how I use CircleCI for deployments in my projects, I utilize it for continuous integration and automation to have the builds. I create YAML pipelines with it, and we first have some steps such as installing Node if it is a front-end build or installing the dependencies. After that, I build the project. Following the build, I deploy it on AWS Elastic Container Service of the image. After the image is deployed, I deploy that image on the running EC2 , either in EC2 or within the S3 bucket. Then, the environment is ready, and I run the tests against that environment.
Additionally, I use CircleCI for insights and dashboards, doing some dashboarding and monitoring the results, duration, and how the runs have been, including the output and generation of reports or sending notifications to email addresses. I also connect it with Azure DevOps and GitHub .
What is most valuable?
Among those features, I find the most valuable in my day-to-day work the automation aspect, as we have a large product team with many developers who continuously create branches and push code, necessitating automation that builds the pipeline and the branches automatically while giving faster feedback. There is speed, flexibility, and intelligent pipeline orchestration possible with CircleCI, which we appreciate. Additionally, we have hooks and can run tasks on commit or push, which allows executions based on those events, and the self-hosted runners to run jobs on our infrastructure or use provided agents by CircleCI itself are also beneficial.
CircleCI has positively impacted my organization by bringing in faster deployments, which means we can release faster, receive quicker feedback, and enhance collaboration and communication across the entire team. We benefit from really good dashboards, build performance analytics, and optimization of resources, which allows for multiple containers or virtual machines, significantly reducing build time. Additionally, the security and vulnerability scanning provided out of the box helps tremendously, as we just need to push the code and everything is managed by our CircleCI YAML scripts.
What needs improvement?
I believe CircleCI should leverage the growing trend of AI by offering an out-of-the-box AI-driven dynamic YAML file creation feature using natural language processing. Instead of having users define pipelines manually, users could simply use natural language to define their needs and let the AI generate the YAML configuration automatically. Implementing a multi-agent architecture could also enhance usability.
I rated CircleCI six out of ten because I think they need more transparency in pricing, as there are instances of unclear network data transfer and storage costs related to caching and workspaces. Additionally, there are sporadic platform security incidents that need addressing, and pipelines require good protection. Secret rotation should also be prioritized. There are occasionally long-running workflows that can be difficult to debug, and improvements could be made in job startup times and cache management.
For how long have I used the solution?
How was the initial setup?
What other advice do I have?
To ensure that security and compliance requirements are met while using CircleCI, we utilize restricted contexts for secrets along with short-lived credentials. We follow some regulatory guidelines, ensuring that every job runs in an isolated environment, either in a Docker container or a virtual machine. Furthermore, we maintain secret rotation and use secure API tokens while implementing appropriate access controls.
I rate this product six out of ten.
Fast, User-Friendly, but Keep an Eye on Costs
Intuitive, Easy, and Effective for CI/CD
Automated deployments have streamlined cloud releases but configuration orbs still need simplification
What is our primary use case?
CircleCI is used primarily as the pipeline for application deployment. When a pull request is created in GitHub , it triggers a CircleCI pipeline because of the GitHub integration. During the CircleCI pipeline, the application goes through building and deployment to the appropriate destination, which can be a Lambda or AKS microservices.
What is most valuable?
CircleCI's GitHub integration is the best feature offered. The GitHub integration is most valuable because of its ease of use, as it only requires integration with the GitHub repository and then creating the pipeline as a YAML file within the repository code.
CircleCI has positively impacted the organization, as it has been used for many years and serves as the main source for application deployment. Every deployment is conducted through CircleCI, and this is what keeps the company functioning.
What needs improvement?
CircleCI's Orbs are not as easy to use as they could be. If CircleCI implemented a function approach similar to GitHub Actions , it would be significantly better.
CircleCI could be improved if it could function without Orbs. Instead of Orbs, using a function approach like GitHub Actions would be beneficial.
For how long have I used the solution?
CircleCI has been used for two years.
What do I think about the stability of the solution?
CircleCI is stable.
What do I think about the scalability of the solution?
CircleCI's scalability is easier to manage, but it comes at a high cost.
How are customer service and support?
A customer support ticket has never been opened.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
This company already had CircleCI running for several years before starting at this position.
How was the initial setup?
CircleCI was purchased through the AWS Marketplace .
What about the implementation team?
The company does not have a business relationship with this vendor beyond being a customer.
What was our ROI?
A return on investment with CircleCI has not been observed, and no relevant metrics such as time saved or fewer employees needed can be shared.
What's my experience with pricing, setup cost, and licensing?
There is not much experience with pricing, setup cost, and licensing because that is managed by the legal team.
Which other solutions did I evaluate?
Other options were not evaluated before choosing CircleCI, but after choosing CircleCI, GitHub Actions and Harness are already being evaluated.
What other advice do I have?
For others looking into using CircleCI, study thoroughly about CircleCI's Orbs because they are quite complicated. The overall review rating for CircleCI is 6 out of 10.