Parinita  /  Products  /  Parinita noBGP
Foundation Layer

Parinita noBGP

The Identity-Routing Overlay That Replaces BGP Inside Your Fabric

Zero BGP east-west. Identity-driven path selection. Sub-50ms failover.

noBGP is Parinita's identity-routing overlay for east-west traffic across the 101-POP fabric. Where legacy BGP is route-table-driven, slow to converge, and vulnerable to hijacking, noBGP is identity-driven, real-time, cryptographically secured, and natively multi-tenant.

101
Sites Worldwide
<50ms
Failover Time
5
Traffic Classes
~3s
Policy Reflection
01 / The Problem

BGP Was Never Built for AI Fabric

Enterprise AI infrastructure requires routing that understands workload identity — not just AS paths.

BGP takes 30 seconds to 15 minutes to converge on a failure, has no concept of tenant isolation, and carries no cryptographic defense against route hijacking.

  • BGP Convergence Is Too Slow

    Legacy BGP takes 30 seconds to 15 minutes to reroute traffic after a failure — unacceptable for GPU-to-GPU inference workloads.

  • BGP Has No Identity Awareness

    BGP routes on AS path, not workload identity. Two tenants can share an overlay path with no cryptographic separation.

  • BGP Is Hijack-Vulnerable

    BGP route hijacking is a well-documented attack vector. There is no cryptographic defense in the protocol itself.

Capability
Current / legacy
What's needed
Failover time
30s to 15 min (BGP reconvergence)
Sub-50ms (centralized overlay controller update)
Identity awareness
None — BGP routes on AS path only
Full workload identity via Crucible Ed25519 keypairs on every packet
Tenant isolation
Shared routing tables, no per-tenant VRF by default
Hardware-enforced VRF isolation per tenant, per flow, at the NIC
Class of service
Best-effort or manual DSCP marking, no lossless guarantee
5 CoS classes with lossless RoCEv2 for GPU and NVMe-oF traffic
Policy reflection
Hours to days (manual router reconfiguration)
~3 seconds (one Chrysalis block confirmation)
Hijack protection
None cryptographic — route advertisements can be forged
Cryptographic identity on every packet — unauthorized paths XDP_DROP'd before kernel
02 / Core Capabilities

Identity-aware overlay routing that BGP was never designed to provide.

noBGP sits above Crucible's per-packet identity enforcement to make identity-aware path decisions — without reconfiguring the underlying BGP edge routers.

Path selection uses workload identity and Chrysalis VRC policy — not AS path — so two tenants' overlay paths never share a VRF or routing decision.

  • Identity-Driven Routing

    Path selection uses workload identity and Chrysalis VRC policy — not AS path. Two tenants' overlay paths never share a VRF.

  • Sub-50ms Failover

    Centralized P8 AmpereOne controller pushes overlay updates instantly via API — vs BGP's 30 seconds to 15 minutes.

  • Per-Flow Class of Service

    RoCEv2 GPU traffic on CoS 3 lossless, NVMe-oF on CoS 4 lossless, control plane on CoS 2 with ECN, management on CoS 1, best-effort on CoS 0.

  • Cisco and Arista API Integration

    Signals Cisco Crosswork for North-South Fabric 1 and Arista CloudVision for East-West Fabric 2. noBGP decides; the switches enforce.

  • Cross-Tenant Path Isolation

    Cross-tenant Nexus collaboration, multi-agent Chorus workflows, and Atma twin-to-twin negotiation all run on a single physical fabric without any shared overlay path.

  • 3-Second Policy Reflection

    A VRC smart-contract policy change reflects on the overlay within one block confirmation (~3 seconds). Insider-threat isolation executes in 30-60s.

  • Automated Incident Response

    When Secure signals an incident, noBGP isolates the relevant overlay path within 30 seconds — no manual intervention required.

  • Native Multi-Tenancy

    Every tenant's traffic operates in its own VRF. No shared paths, no shared routing decisions, enforced at the NIC by Crucible.

  • Chrysalis Policy Enforcement

    VRC smart-contract policy changes anchor on-chain and reflect on the overlay within one block — tamper-proof by architecture.

03 / Architecture

The Plane Model

Orchestra introduces "planes" — logical groupings of hardware optimized for a specific workload class. Unlike Kubernetes node pools, planes represent fundamentally different hardware architectures with different drivers, network requirements, and scheduling semantics.

The plane model is what makes Orchestra different from every other orchestration tool. Kubernetes sees nodes. Orchestra sees purpose-built hardware tiers and routes workloads accordingly.

P1
Reasoning Cortex
AMD Instinct MI350P
Primary AI inference · LLM serving
1,450+ nodes · 288GB HBM3e · high-bandwidth accelerator
P2
Training & Generation
NVIDIA RTX PRO 6000 Blackwell
Training · TTS · creative compute
950+ nodes · 96GB GDDR7
P3
Chain & CPU Compute
AMD EPYC Turin 9005
Chrysalis validators · CPU inference
700+ nodes · Zen 5c
P4
Knowledge & Retrieval
Intel Sierra Forest
Almanac vector search · RAG anchor
1,250+ nodes · 144 E-cores
P5
Long-Term Memory
NVMe Storage
Enclave · Stratum immutable object
850+ nodes · ransomware-resistant
P6
Media & Acceleration
RTX 4500 BSE · Alveo MA35D
Four tiers · GPU + FPGA + CPU
2,150+ nodes · 4K/8K hardware acceleration
P7
Edge Reflex
Qualcomm Cloud AI 100 Ultra
Ultra-low-latency edge inference
2,000+ nodes · sub-10ms response
P8
Coordination Layer
AmpereOne A128
Orchestra · Chorus routing · agents
2,400+ nodes · 128 ARM cores
P9
Nervous System
Cisco 8000 · Palo Alto · Arista
Routing · firewall · dual fabric
3,500+ devices · ConnectX-7 NICs
04 / Path Decision Model

Eight identity factors. Sub-50ms decisions.

noBGP's overlay path decisions account for workload identity, tenant VRF, class of service, DSCP marking, policy authorization, geographic affinity, threat posture, and failover path — encoded per flow.

  1. 01
    Workload identity
    Cryptographic identity of the originating workload and tenant, enforced by Crucible at the NIC via Ed25519 keypairs.
  2. 02
    Tenant VRF
    Each tenant operates in an isolated virtual routing and forwarding domain — overlay paths never cross between tenants.
  3. 03
    Class of service
    CoS 0 (best-effort) through CoS 4 (lossless NVMe-oF) — encoded per flow and enforced end-to-end across the fabric.
  4. 04
    DSCP marking
    Per-flow DSCP marking aligns with CoS assignment for consistent QoS treatment across Cisco and Arista switches.
  5. 05
    Policy authorization
    Chrysalis VRC smart-contract policy determines which overlay paths are authorized for this workload identity.
  6. 06
    Geographic affinity
    Path selection accounts for POP proximity and jurisdictional data residency requirements.
  7. 07
    Threat posture
    Active security events from Secure or Sentry trigger overlay isolation without manual intervention.
  8. 08
    Failover path
    If the primary overlay path becomes unavailable, alternate paths activate within 50ms.
python
import nobgp

client = nobgp.Client(seat_token='your_seat_token')

# List active tenant VRFs
vrfs = client.vrfs.list(tenant_id='your_tenant_id')
for vrf in vrfs:
    print(f"VRF: {vrf.name}, CoS: {vrf.cos_class}, Policy: {vrf.policy_hash}")

# Monitor overlay path health
for path in client.paths.active():
    print(f"Path: {path.src} -> {path.dst}, Latency: {path.latency_ms}ms")
05 / Proof

Proven at scale. Not in a lab.

Parinita AI Edge is the production deployment of the Parinita platform and the largest heterogeneous AI infrastructure deployment in the United States.

Reference Deployment

Parinita AI Edge

The most complex heterogeneous AI infrastructure in the United States. 101 sites, 9 planes, 12,000+ nodes, 4 accelerator vendors, dual network fabrics, four-layer tenant isolation — all through a single sovereign control plane.

101
Points of Presence
4 tiers: T1 (32), T2 (29), T3 (19), T4 (21)
909+
K8s Clusters
101 sites x 9+ plane types
12K+
Compute Nodes
Supermicro, Dell, Ampere, Cachengo
4
Accelerator Vendors
Intel Habana, NVIDIA, AMD, Qualcomm

Network & Security Infrastructure

2,491+
Cisco Switches
+ 303 routers (EVPN-VXLAN)
1,734+
Arista Switches
Lossless GPU backend fabric
367+
Palo Alto Firewalls
PA-5580/PA-5560 series
152+
Petabytes Storage
NVMe over RDMA
  • Multi-vendor accelerators
    Four accelerator vendors — Intel Habana, NVIDIA, AMD, Qualcomm — orchestrated through one control plane with unified scheduling, monitoring, and lifecycle management.
  • Dual-fabric networking
    Cisco production fabric and Arista GPU backend fabric operating as a coordinated system, bridged by identity-aware routing.
  • Nationwide scale
    101 sites across 42 U.S. states, each operating autonomously with a local control agent and a sovereign cross-site routing plane.
  • Multi-tenant isolation
    Four-layer defense-in-depth: VXLAN VNIs, identity-routing, Palo Alto firewalls, and Cilium eBPF — validated across every plane and site.
  • Compliance readiness
    FIPS 140-2 at launch, with FedRAMP Moderate, CJIS, and IL4/IL5 certification paths active through Parinita compliance profiles.
  • Sub-millisecond routing
    Every request classified and dispatched in under 1ms, enabling real-time SLA enforcement without perceptible overhead.
06 / Use Cases

Built for networks that carry identity-aware AI workloads.

noBGP removes BGP from inside your AI fabric without touching your WAN edge routing.

Any organization where two tenants' AI traffic must never share an overlay path — even on the same physical fabric.

  • Multi-Tenant AI Platforms

    Run multiple enterprise tenants on one physical fabric without any shared overlay paths or VRFs between them.

  • Regulated AI Workloads

    HIPAA, ITAR, and PCI tenants require traffic isolation that BGP cannot provide by design.

  • High-Performance GPU Clusters

    RoCEv2 lossless GPU-to-GPU traffic requires class-of-service enforcement that noBGP delivers natively at the per-flow level.

  • Incident Response Automation

    Automated overlay isolation within 30 seconds of a Secure incident signal — no human step in the response chain.

  • Cross-POP AI Inference

    Identity-aware path selection across 101 POPs ensures inference traffic routes to the right hardware, tenant, and jurisdiction.

07 / Getting Started

Deployment Models

noBGP deploys as part of the Parinita fabric. No separate provisioning step required.

Integrated Deployment
Part of the Parinita Fabric

noBGP deploys as part of the Parinita 9-plane fabric. No separate provisioning required — it comes with the platform.

API-Driven Switch Control
Cisco + Arista Integration

Signals Cisco Crosswork and Arista CloudVision via API. noBGP makes the path decision; the underlying switches enforce it.

Overlay-Only Migration
Non-Disruptive Rollout

BGP continues running at the WAN edge. noBGP takes over east-west. Migrate traffic class by class without disruption.

08 / Get Started

Talk to Us

Our network engineering team can walk through how noBGP integrates with your existing Cisco and Arista infrastructure.