Calico Cloud: SaaS networking and network security for Kubernetes

Our primary use case for Calico Cloud is securing and monitoring Kubernetes workloads across multiple clusters, where we use it to enforce network policies, control pod-to-pod communication, gain visibility into network traffic, and detect security issues. It also helps with micro-segmentation, compliance, and troubleshooting connectivity problems in our containerized applications, which maintains a zero-trust networking model.

We use Calico Cloud to implement micro-segmentation across our Kubernetes clusters by defining fine-grained network policies for different namespaces and workloads. Instead of allowing unrestricted pod-to-pod communication, we enforce least privilege access so that only approved services can communicate with each other. This has helped us isolate applications, reduce the attack surface, and meet our internal security requirements. From a connectivity perspective, Calico Cloud has been particularly useful for troubleshooting network policy issues. When an application cannot reach another service, we use flow logs and policy visualization to quickly determine whether traffic is being allowed or denied, identify which policy is responsible, and resolve the issue without spending hours manually tracing Kubernetes networking.

The best features for us with Calico Cloud are a combination of Kubernetes network policy management with deep traffic visibility. Other features include real-time flow visualization for troubleshooting connectivity issues, policy recommendations and previews before enhancements, and rich flow logs that help quickly identify blocked or unexpected traffic.

Real-time flow visualization has been one of the most valuable features for our team when dealing with real-time scenarios. During application deployments or network policy changes, we use it to observe live communication between Kubernetes workloads and quickly identify whether traffic is being allowed or blocked. For example, when a newly deployed microservice was unable to communicate with the backend API, the flow visualization immediately showed where the communication was being denied. This allowed us to identify the specific network policy and restore connectivity within minutes instead of spending significant time analyzing logs or packet captures.

Calico Cloud has had a positive impact on our organization by improving both our Kubernetes security posture and operational efficiency. Overall, it has helped our platform and DevOps team deploy changes with greater confidence, respond to incidents more quickly, and maintain a more secure and reliable Kubernetes environment.

Calico Cloud is a very good product with well-defined usage. I would appreciate seeing more improvement on real-time analysis capabilities.

I have been working as a Senior Systems Engineer for more than five years. I have been using Calico Cloud in my project for more than a year.

Calico Cloud is stable.

Calico Cloud has scaled well with our Kubernetes environment and has many capabilities that make it easier to apply consistent security policies across multiple clusters.

Customer support is very good, and they have responded to us whenever we have encountered issues with the product.

I have experience with pricing, setup cost, and licensing.

The company has purchased Calico Cloud from the marketplace, though the implementation was not handled by me personally.

We have seen a positive return on investment. While the licensing cost is higher than using basic open-source networking alone, the operational benefits have outweighed the investment. It has reduced the time spent troubleshooting network connectivity issues, improved visibility into Kubernetes traffic, and helped us enforce consistent security policies across clusters. The biggest value has come from faster incident resolution.

The setup cost has been positive overall.

Calico Cloud has been very useful in our project, and I am very positive about it. I would rate Calico Cloud an eight overall because it has more requirements to be fulfilled.

Regarding Calico Cloud's AI capabilities, I have not used them much. When it comes to governance and security, Calico Cloud is useful for strengthening governance and security, particularly when identifying potential policy misconfigurations and unusual network recommendations. Our team validates network policies, detects expected traffic flows, and reduces the likelihood of human error during configuration changes. This serves as a helpful decision support tool rather than replacing manual governance and security controls.

The platform has been accurate and reliable in our experience. Calico Cloud has AI-assisted features, and we treat its recommendations as guidance rather than automatic decisions. We validate suggested changes through our normal review and testing process before applying them to production. This approach has made the insights dependable and has helped reduce troubleshooting time while improving the accuracy of network policy management.

I would suggest using Calico Cloud for the exact use case that I am using it for, as that is the best advice I can give. The benefits I have mentioned are real benefits. I assign a rating of eight to Calico Cloud based on my experience with the product.

My main use case for Calico Cloud is traffic management, which is the primary feature that I primarily use in my organization. We appreciate their recommendation system for security, and the service graph they provide gives us accessibility to our service graph, which is what we use it for.

A specific example of how I use Calico Cloud for traffic management and the service graph is that they provide us visibility, which is one of the things I appreciate about Calico Cloud. A similar product is Jaeger when you are using Istio, so they essentially do the same thing. You look at the service graph and you will see how, for example, we have several microservices. For me to communicate with another, normally you would not know how the full communication works. However, with Calico Cloud, you are able to see that this service communicates with these services and how they communicate. You can see the latency that is occurring at a particular junction. You can basically see all your services that make up your application that were developed for different vendors in our company, and you can see how each and every one of them communicates for this product. All the services that make up that microservice are what we use the service graph for. Their micro-segmentation helps to provide functionality similar to AWS Security Hub or a security advisor. You are able to be told that for a particular product and particular communication, these are the communications that occur on a day-to-day basis, and therefore, they recommend that you put in this kind of policy. If you agree with them, then you go and enforce the policy, and they provide a place to test it so that it does not affect your real-life traffic, allowing you to confirm that the feature really helps you.

Regarding my main use case and how Calico Cloud fits into my workflow, they have observability. I am able to combine all the different logs, DNS logs, so that I can see what actually happens from flow logs, DNS logs, and the other logs. That way I can make sense of what is going on in my cluster. For observability, they are doing good work. They provide insights that I have used with Istio, which is another product that also takes care of observability, not necessarily network policies in the way Calico Cloud supports. It is a good job overall.

In my opinion, the best features Calico Cloud offers are micro-segmentation, particularly the zero-trust micro-segmentation, which stands out the most for me. Being able for them to look at my traffic and recommend the best network policy for me means I do not have to think about it. That is what I value about Calico Cloud.

Micro-segmentation has helped my team greatly. Some use cases we never thought of with Calico Cloud help increase the security of our application. Micro-segmentation has assisted us with observability as well.

Calico Cloud has positively impacted my organization, especially on the security front, as it helped us anticipate security threats. It aids in making sense of what is happening in the cluster in terms of the logs, the DNS logs, and the other various logs that occur in the system.

For the moment, I think they could possibly add AI for human reporting for observability. Rather than just providing data, adding a speech feature on top of it, such as a summarization of what has actually happened, would be useful for troubleshooting faster. They should still allow users to drill down to see the actual issue, but that quick summary can indeed come in handy.

I have been using Calico Cloud for over a year and a few months.

Calico Cloud is stable.

For the traffic we handle, I consider it quite scalable. We have not had issues with scalability.

I think we have not had time to reach out to customer support as Calico Cloud is quite a usable product.

With Calico Cloud, it was our first product; I never used it previously. However, I have tried Cilium and Istio on my private cluster. That is why I can make this informed decision. Calico Cloud are the first ones that work with network policies, so that is the default when trying to work with Kubernetes clusters.

My experience with pricing, setup cost, and licensing is that the pricing is moderate. The setup cost was basic because there are many helpful resources available that I could reference. The licensing was payable with the best pricing based on what they are offering.

I have seen a return on investment with time saved and fewer employees needed. We are able to reduce the number of times needed for debugging through the service graph and the recommendations for the micro-segmentation of their security tool, helping us identify necessary network policies. We also observe our traffic with the recommendations provided by Calico Cloud, which results in good savings in return on investment, which includes time saved and fewer troubleshooting and debugging times.

My experience with pricing, setup cost, and licensing is that the pricing is moderate. The setup cost was basic because there are many helpful resources available that I could reference. The licensing was payable with the best pricing based on what they are offering.

Before choosing Calico Cloud, I evaluated Cilium, which is their competitor.

My advice to others looking into using Calico Cloud is that it is worth the fee. I give Calico Cloud a rating of seven because there are places for improvement, as I recommended. For what they do, they do it well, especially with zero-trust micro-segmentation and their security plus observability tools. They may not have all the features that their competitor Cilium has, and they are doing a portion of what Cilium does and a portion of what Istio does. For what they do, they do it well, and that is why I give them a seven.