Rondo is an open source networking platform designed to simplify how teams manage multi-cloud connectivity and on-premise routing. It provides a programmable control plane that abstracts complex network topologies into intuitive policy-driven overlays.
Engineers and architects use Rondo to enforce security zones, optimize traffic paths, and accelerate service deployments across hybrid environments. The tool focuses on declarative intent, making network changes safer and more reproducible.
Global Reach and Data Center Presence
Where Rondo Operates
Rondo runs both as a managed SaaS control plane and as on-premise appliances, enabling organizations to keep sensitive routing on-site while still leveraging global coordination features.
| Region | Deployment Type | Typical Use Cases | Latency Profile |
|---|---|---|---|
| North America | Managed SaaS + Appliance | Enterprise backbone, hybrid cloud | Low latency to major metros |
| Europe | Managed SaaS + Appliance | Data sovereignty, dense peering | Sub-5 ms intra region |
| Asia Pacific | Managed SaaS | Edge aggregation, CDN anchoring | Variable based on PoP density |
| South America | Appliance preferred | Local compliance, long haul optimization | Higher due to geography |
Architecture and Control Plane Design
Distributed Control Plane
The Rondo control plane runs as a strongly consistent cluster, distributing route calculations and policy enforcement across regions. This design avoids single points of failure and supports graceful degradation during partial outages.
Data Plane Integration
Rondo integrates with Linux eBPF, Open vSwitch, and white box switches to program forwarding state based on the latest control plane decisions. This tight coupling enables fast convergence without requiring changes to existing device firmware.
Security, Compliance, and Policy Enforcement
Zero Trust Segmentation
Security teams define micro perimeters using identity, workload, and geography tags. Rondo then enforces encryption in transit and micro segmentation rules across both cloud and on-premise fabrics.
Regulatory Alignment
For regulated industries, Rondo supports audit trails, policy dry-run mode, and export-controlled algorithm options. This helps meet frameworks such as NIST, ISO 27001, and regional data protection laws.
Operational Workflow and Tooling
Day 2 Operations
Operators interact with Rondo through a versioned REST API and a CLI that supports autocomplete, rollback, and plan-apply cycles. Integration with CI/CD pipelines enables safe, automated network updates.
Observability and Telemetry
Built-in metrics, distributed tracing, and flow export provide end-to-end visibility. Teams can correlate routing changes with application performance to quickly isolate faults and optimize paths.
Deployment Planning and Next Steps
- Map your compliance requirements to the region support matrix in the table
- Run a small scale trial with one workload cluster to validate data plane performance
- Define policy tags and identity sources before scaling to production
- Integrate the REST API and CLI into existing CI/CD and monitoring stacks
- Set alerting on control plane health metrics and path convergence times
FAQ
Reader questions
How does Rondo decide where traffic leaves the control plane and hits the data plane?
Rondo keeps control logic in the SaaS or on-premise cluster and pushes programmed rules to local agents running on hosts and switches. Traffic is forwarded by the data plane using those rules, avoiding hair-pinning through the controller unless policy requires centralized inspection.
Can Rondo manage connectivity between on-premise data centers and multiple public clouds?
Yes, Rondo treats hybrid environments as a single policy domain. It builds encrypted tunnels between sites, chooses paths based on latency and cost metrics, and can steer traffic away from congested or failing links automatically.
What happens during a control plane node failure or split brain scenario?
The Raft consensus protocol ensures that a new leader is elected without route blackholes. During partitions, only the majority partition can progress, preventing conflicting state from being propagated to the data plane.
How often does the control plane reconcile desired versus actual state?
Reconciliation runs continuously, comparing the declarative intent stored in the cluster store with the actual forwarding state reported by agents. Drift is detected within seconds and remediation actions are triggered based on severity levels.