01
CAMP engine
Cilium-based networking as the Fusionative Enterprise default path: policy, observability, and multi-cluster mesh under FusioNetwork.
Fusionative Network · CAMP
Cilium-based CAMP is the Enterprise networking engine.
CAMP is Fusionative Enterprise’s Cilium-powered network engine under Fusionative Network (FusioNetwork): eBPF connectivity, NetworkPolicy, Hubble observability, Tetragon runtime signals, and Cluster Mesh. Estates that standardize on Calico or Kube-OVN remain supported as alternative CNI paths.
On this page
Fusionative Network only: CAMP on Cilium, supported Calico and Kube-OVN paths, Exposure Gateway, and Fabric planner.
Fusionative Network
Three surfaces. One networking product.
CAMP engine, Exposure Gateway, and Network Fabric planner—kept on Fusionative Network, not scattered across other suite pages.
02
Exposure Gateway
DNS, certificates, routes, and GitOps export for controlled north–south reach—kept on the same Network product surface.
03
Network Fabric planner
CIDR, MTU, and topology planning across sites so fabric intent stays visible beside day-2 cluster ops.
CAMP · Cilium engine
What the Cilium-based Enterprise path includes.
Named as Cilium actually provides—under the CAMP operating surface in Fusionative Enterprise.
eBPF connectivity
Cilium CNI for pod networking, load balancing, and identity-aware traffic paths without relying on iptables-only models.
Network policy
Cilium NetworkPolicy (and Kubernetes NetworkPolicy where applicable) enforced from the same control-plane operating model as tenancy and Shield.
Hubble observability
Flow visibility and network observability for troubleshooting and audit—wired into how operators see the estate, not a disconnected sidecar story.
Tetragon signals
eBPF runtime and network-adjacent signals that complement Fusionative Shield detect/respond paths—named as Cilium Tetragon, not a separate invented product.
Cluster Mesh
Multi-cluster Cilium Cluster Mesh patterns for connectivity across fleets when the estate design calls for it.
CNI choice
CAMP first. Calico and Kube-OVN supported.
CAMP/Cilium is the Enterprise networking engine. Calico and Kube-OVN are supported alternatives for estates already standardized on those CNIs—without claiming identical CAMP feature depth.
Enterprise engine
Cilium · CAMP
First-class Fusionative Enterprise path. Full CAMP surface: policy, Hubble, Tetragon adjacency, Cluster Mesh, plus Exposure Gateway and Fabric planner.
Supported CNI
Calico
Supported for estates standardized on Calico. Connectivity and NetworkPolicy lifecycle participate in the platform; CAMP’s Cilium-specific Hubble/Cluster Mesh depth applies when Cilium/CAMP is the chosen engine.
Supported CNI
Kube-OVN
Supported for estates using Kube-OVN. Underlay/OVN-oriented designs stay operable from the control plane; advanced CAMP capabilities remain Cilium-backed.
Operating path
From CNI choice to governed exposure.
Pick the datapath that matches the estate, then keep policy, observability, and north–south exposure on Fusionative Network.
01
Choose CNI
CAMP/Cilium, Calico, or Kube-OVN
02
Policy
NetworkPolicy aligned to tenancy
03
Observe
Hubble (CAMP) + estate telemetry
04
Expose
Gateway, DNS, certs, GitOps export
Clear hierarchy
CAMP depth vs supported CNI alternatives.
Use Cilium/CAMP when you want the full Enterprise networking engine. Use Calico or Kube-OVN when the estate already depends on them—without overclaiming Hubble or Cluster Mesh on non-Cilium paths.
01
CAMP (Cilium)
- Default Enterprise networking engine
- Cilium NetworkPolicy + eBPF datapath
- Hubble flow observability
- Tetragon runtime/network signals
- Cluster Mesh multi-cluster patterns
02
Calico · Kube-OVN
- Supported alternative CNI choices
- Fit estates already standardized on them
- Policy and connectivity under one plane
- Not a rebrand of CAMP feature depth
- Choose CNI per estate design—not slogans
Run networking on the same plane as your AI cloud.
Walk CAMP on Cilium, Calico or Kube-OVN choice, policy, Hubble, and Exposure Gateway with the platform team.