Parinita Corridor
Sovereign Highway — SD-WAN data plane with sub-50ms failover across every carrier.
Corridor is the SD-WAN data plane that owns WAN path selection. Where Crucible decides what is allowed and encodes identity into the packet, Corridor decides how the packet moves — scoring every available WAN path in real time on latency, health, cost, and sovereignty, then routing accordingly.
What it does
-
Four-dimensional path scoring
BFD probes (10ms × 5) plus active probes (100ms cadence) feed a real-time scorer on every path. Decisions reflect latency, health, cost, and sovereignty in under 10ms.
-
Sub-50ms failover
When a primary path degrades, NATS JetStream events deliver the health change to the scorer and a new path is selected in under 50ms — orders of magnitude faster than BGP convergence.
-
Every major WAN provider
Lumen (primary), Megaport (contracted dynamic cross-connect), AWS Direct Connect, GCP Cloud Interconnect, Azure ExpressRoute, plus direct mobile/broadband carrier peering — all arbitrated through one control plane.
-
Sovereignty-hard, fail-closed
HIPAA, ITAR, and Financial workloads disqualify public Lumen paths automatically. If no compliant path exists, the request is rejected — Corridor fails closed rather than open.
-
Anycast bootstrap, handoff to Crucible
Corridor selects the nearest POP via anycast; once selected, hands off to Crucible for tunnel establishment and identity assignment.
How it works
Corridor runs a per-site path-scoring engine fed by BFD probes (10ms × 5 multiplier) and active probes (100ms update interval) across every available path type at every POP. NATS JetStream events propagate health changes to the scorer in under 10ms. Failover is sub-50ms — vs. BGP’s 30 seconds to 15 minutes.
The interface to Crucible is bidirectional. Corridor reads Crucible’s
identity-to-path mappings — including sovereignty and circuit-type
constraints — to know which paths each workload class may use. It
publishes path-health events back to Crucible on parinita.corridor.health,
which Crucible uses to update CRDT routing decisions when a primary path
degrades. SLA breaches for regulated workloads with no compliant path go
to parinita.corridor.breach for Chrysalis logging and NOC escalation.
Corridor also manages the Megaport API for programmatic cross-connect provisioning, hyperscaler interconnects as dynamic SD-WAN paths, and mobile/broadband peering for iOS/Android apps and on-premises edge devices. Anycast bootstrapping — selecting the nearest POP — is Corridor-owned; after the POP is selected, Corridor hands off to Crucible for tunnel establishment.
When to use it
- Multi-jurisdiction deployments where some flows can cross borders and others can’t, and you don’t want to enforce that in application code.
- Operators who can’t tolerate BGP convergence latency on regulated workloads.
What it isn’t
A general-purpose VPN or load balancer. Corridor optimizes for sovereign path selection across many carriers with hard policy constraints — not for raw bandwidth or commodity connectivity.
Related products
Part of the Parinita AI Edge
Bring Parinita Corridor into your stack.
Every Parinita product runs on the same 9-plane fabric across 101 edge POPs. Talk to us about a pilot, or see how the pieces fit together.