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.
$15
per month
Datadog
Score 8.8 out of 10
N/A
Datadog is a monitoring service for IT, Dev and Ops teams who write and run applications at scale, and want to turn the massive amounts of data produced by their apps, tools and services into actionable insight.
$1.27
per month (billed annually) per host
Pricing
CircleCI
Datadog
Editions & Modules
Server
Contact Sales
Performance
starting at $15
per month
Scale
starting at $2000
per month
Log Management
$1.27
per month (billed annually) per host
Infrastructure
$15.00
per month (billed annually) per host
Standard
$18
per month per host
Enterprise
$27
per month per host
DevSecOps Pro
$27
per month per host
APM
$31.00
per month (billed annually) per host
DevSecOps Enterprise
$41
per month per host
Offerings
Pricing Offerings
CircleCI
Datadog
Free Trial
No
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
Discount available for annual pricing. Multi-Year/Volume discounts available (500+ hosts/mo).
CircleCI shines with its specialized infrastructure. Its dedicated macOS runners ensure blazing-fast iOS builds, while intelligent Docker layer caching significantly reduces backend build times and costs. The ability to SSH directly into failed builds dramatically accelerates …
Based on the cost for feature set that we needed we went with CircleCI. There were also more people on our team that knew how to use CircleCI already compared to other products which made it a preferred choice for ramp up. Other products were not as robust and quick to …
We use CircleCI when we need a good, independent CI/CD provider in an existing workflow. That said, we've begun investing more heavily in GitHub actions as it's closer to where our code is stored. CircleCI is a feature of a workflow, and can be filled by many different service …
CircleCI is a sass product which means you don't need to maintain your own servers. This can also be a negative as you are dependent on their service. This also means you can't ssh into a machine to see what went wrong like you can with Jenkins. However for most users this …
Because the Travis CI features are not very good, it has a lot of problems with concurrency and the uptime of the on-cloud solution was the worst we have ever tried.
CircleCI seemed to have a quicker setup than other similar products, with a good integration with GitHub repos. Projects are quick and easy to set up within the UI, and workflows can then be created off the back of those fairly intuitively. Clever interpretation of commit …
CircleCI is the company that is innovating compared to the other ones. I think it's a great piece of software compared to other open source options that don't have as much functionality and improved capability over time.
While the UI on CircleCI is not my favorite, it's leagues better than Travis CI. I really like Heroku CI much better, but the functionality is much more limited there. If Heroku CI had the same functionality as CircleCI, I probably wouldn't use CircleCI.
Jenkins and Teamcity both have additional features that maybe you require, but they are also a lot more work to get set up and working. There's a much longer learning curve to getting these configured for a simple build. They're not hosted, so you have to maintain the …
CircleCI does a lot of what we need it to do; however, I believe Jenkins is a better Continuous Integration tool. Jenkins has more capabilities and integrations. In addition, Jenkins is a much more widely used tool, which means more developers are familiar with it and have …
Not having to manage / deal with a Jenkins server is fantastic. I don't have much personally against Jenkins. I've set up and run a Jenkins server before. It's just complexity that doesn't really have much to do with the business beyond getting our software to our customers. My …
Since CircleCI gave us its infrastructure we don't have to worry about servers, provisioning and maintenance. Also CircleCI provides us great features to increase speed of builds by adding more containers to the build. Jenkins is the best open source alternative but it requires …
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 …
It was our CTO who did the evaluation, not me, but as I recall other services weren't as parallelizable. We knew we wanted to run on many containers simultaneously for fast test results.
For us it really came down to CricleCI being the fastest and simples tool to get started with. The GitHub integration is slick and seamless and the scripting config file allowed us to configure our entire build system, including tests, in less than a day. It's very light weight …
Circle was the first CI with simple setup, great documentation, and tight integration with Github. Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when …
Travis has full YML configuration in areas where CircleCI is slightly lacking still, which is great, but CircleCI offers more features, settings, and potential performance.
Codeship is simpler to use, you can use it entirely from their UI without modifying your Git repository at …
Travis CI is great for open source projects – it's completely free, but CircleCI offers some support for closed projects as well. CircleCI has cheaper pricing plans, and you are able to customize them as much as you want. At Travis CI you can select only a predefined amount of …
The biggest downside to CircleCI is that it doesn't support parameterized builds, that is testing your code against language version X and Y, or framework version A and B. Beyond that, it is really a great product.
I had used Travis CI in some of my open source projects. However, it was too expensive for us so I looked for an alternative that was in our budget. Scrutinizer is also very useful, but also out of our budget. When we get larger I could see myself using Scrutinizer for quality …
I think these three tools are just as good as the other except that Travis CI supports mobile a lot better but price wise, CircleCI is the best that I have found and is supports the need for a startup. For a long while, CircleCI had Docker support before Codeship but now, …
Datadog is significantly more user-friendly than CloudWatch.In terms of capabilities, they're similar. I would not call either of the best-in-class for any single feature, but Datadog feels more polished and ready to use overall.Multi-cloud monitoring is a clear differentiator …
I use Datadog because it concentrates all these features into a single tool, facilitating the learning curve that my platform and development engineering team needs in order to be able to set up the monitors/alerts/SLIs/SLOs as well as to diagnose a production issue. Its easier …
Datadog seems to be the most feature-rich of all the alternatives we've considered, however due to problems outlined earlier, some of the others have benefits. OpenTel can give us a way to make our platforms compatible with a variety of vendors, and can be done without …
Datadog is a more complex but complete solution than any of the other Log Aggregation, monitoring, or general observabilty tools that we have trialed. I found it easier to setup following useful and up-to-date documentation provided directly by Datadog instead of scattered …
Kibana Datadog … because within our usecase we have all the events in kibana but sampled traces in Datadog … but if we had all the traces it would have been much more useful
I think Datadog and sentry serve different needs. I like sentry to keep track of errors on our systems. And then I'll jump into Datadog to investigate those issues.
We have utilized a SIEM in the past, but it was a very manual process to set it up. Content packs make it very easy to set up and get alerting instantly. Datadog takes out a lot of headaches for our security team, since they no longer have to create custom alerts for every …
First think first - it's easy to use, and very easy to implement in any infrastructure. It provides a custom dashboard and monitors. I’ve used or evaluated Grafana, Prometheus, Amazon CloudWatch, and Dynatrace, and each tool has strong capabilities. Prometheus + Grafana provide …
All other tools dont have all the features which Datadog provides. Easy to use from UI where other may have complicated UI or no UI at all to create monitors. Consider like AWS grafana, we have limitation to create monitors from UI. There is no recurring downtime for monitors. …
UI of the Datadog is easy to understand and integration steps are easy to understand. It also provides the troubleshooting steps which are easy to understand. Supports multi cloud integrations which is very important for all the customers to know about the cloud service's …
we primarily use Kubernetes, and Prometheus is great for collecting time series metrics, especially in Kubernetes. and Grafana is used for dashboards. As these are open source, we host them and manage them internally. We choose Datadog because of its logs, traces, and …
I selected Datadog because of its features and the wide range of integration support. As I already told it supports more that 600+ integrations which helps and organization to keep everything in a single place and also its AI feature which is reducing the time for root cause …
1. Grafana is good, but a lot of integration is required for it to work. .that not the case of Datadog 2. Faster to set up Datadog instead of Grafana 3. Alerting in Datadog feels much easier thanin Grafana.
Datadog is best for cloud-native and fast-setup. It is more mature for infrastructure and real-time observability. The UI is more user-friendly and provides wide coverage of app insights.
I have tried and used a number of other tools similar to Datadog such as New Relic, Splunk, Prometheus, AWS cloudwatch and Dynatrace. New Relic and Splunk provide excellent monitoring and analytics, but Datadog’s consolidated dashboards and ease of setup combined with a wealth …
Our logs are very important, and Datadog manages them exceptionally well. We frequently use Datadog services for our investigations. Use case: Monitor your apps, infrastructure, APIs, and user experience.
ease of use and implementation, other than new relic (which I think is terrible in every possible way), the other two support opentelemetry better, have more manageable costs and comparable basic services, but they do not have the breadt of services dd does.
We moved to Datadog from Microsoft's Application Insights. Application Insights did a fine job in allowing us to view our application data, but it lacked the holistic view of all our infrastructure and other platforms that could not use Application Insights. Being able to …
In terms of usability, I’ve found Datadog significantly more approachable and powerful compared to Elasticsearch, especially for day-to-day operational monitoring. Datadog offers a much more cohesive, user-friendly interface out of the box, with built-in support for metrics, …
CircleCI is perfect for a CI/CD pipeline for an app using a standard build process. It'll take more work for a complex build process, but should still be up to the task unless you need a lot of integrations with other tools. If you have a big team and can spare someone to focus full time on just the CI/CD tools, maybe something like Jenkins is better, but if you're just looking to get your app built, tested, and delivered without a huge amount of effort, CircleCI is probably your preferred tool.
Datadog works really well with complex microservices architecture like any E-commerce platform which will be having multiple services but they all are interdependent to others so in this scenario Datadog will be best to monitor these as it will show the transactions also between those microservices. If you are using multiple services in your architecture whether it will be cloud services or on prem services Datadog will be the best choice to monitor all those service with in Datadog so that you can see everything in a single place. But if you are having small architecture and few services in that then in that scenario you can use Datadog but it will be little costly as compared to other but obviously the features are very well.
GitHub integration is seamless. Never had a problem with it missing commits.
Robust test environment. I used Travis in the past but tests would sporadically time out for no clear reason, haven't had that happen with CircleCI
Poweful YAML-based configuration in the GitHub repo itself. I don't like CI tools like Semaphore that push you into managing your CI/CD through a web UI, I prefer managing a config file and never having to log in to the CI tool.
It would be nice if you could configure everything via the YML file. Some things are only available via YML, and some things are actually only available in the UI, and many other things have full overlap between the two. I'm sure there are good reasons for this, but this is a pretty confusing situation. For example, certain PHP versions are only available on certain Ubuntu releases. Configuring the PHP version is done via the .yml file, but configuring the Ubuntu release being used for the build has to be done in the UI. This can easily lead to things not building properly.
Alert windows cause lag in notifications (e.g. if the alert window is X errors in 1 hour, we won't get alerted until the end of the 1 hour range)
I would appreciate more supportive examples for how to filter and view metrics in the explorer
I would like a more clear interface for metrics that are missing in a time frame, rather than only showing tags/etc. for metrics that were collected within the currently viewed time frame
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.
There is some room for improvement, but the Datadog team sends out updates frequently, and the UI is user-friendly for engineers, with no significant loading issues or region-specific problems. That was one of the key reasons we preferred Datadog; our company has employees worldwide, and it wasn't difficult to transition to the tool.
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.
The support team usually gets it right. We did have a rather complicate issue setting up monitoring on a domain controller. However, they are usually responsive and helpful over chat. The downside would be I don’t think they have any phone support. If that is important to you this might not be a good fit.
CircleCI shines with its specialized infrastructure. Its dedicated macOS runners ensure blazing-fast iOS builds, while intelligent Docker layer caching significantly reduces backend build times and costs. The ability to SSH directly into failed builds dramatically accelerates debugging. Furthermore, its certified Orbs provide standardized, secure integrations with AWS and Slack, reducing the stability and security risks often associated with unverified community plugins on competing platforms such as GitHub Actions.
Datadog is a more complex but complete solution than any of the other Log Aggregation, monitoring, or general observabilty tools that we have trialed. I found it easier to setup following useful and up-to-date documentation provided directly by Datadog instead of scattered around many blogs or articles. I would love to have my own Grafana + Prometheus expert to setup all the peices we need but you're paying for expertise there instead of an experience with Datadog.