Endpoint-assisted
Endpoint clients initiate outbound authenticated control and telemetry sessions. Ordinary application traffic continues through existing enterprise paths.
Best for remote users and device estate controlNetwork and traffic architecture
Explore direct user requests, indirect event-driven workflows, SD-WAN service insertion, endpoint control, and disconnected-site operation through live two-dimensional traffic animations.
Status at Baseline v1.0.0. The flows on this page illustrate the baseline design. Direct, governed requests through a site node are Available now. Network Truth (read-only) and endpoint telemetry are Included, enabled per qualification. Service chaining is qualified for each site before use. Disconnected operation, cross-site content reuse and the full endpoint fleet are Planned.
Placement models
The deployment mode is selected according to traffic class, latency, privacy, resilience, control, and evidence requirements. Direct AI use is only one path; many workflows are triggered indirectly by telemetry, events, systems, or endpoint state.
Endpoint clients initiate outbound authenticated control and telemetry sessions. Ordinary application traffic continues through existing enterprise paths.
Best for remote users and device estate controlUsers, applications, and systems call EL-Ai-NE through APIs, agents, connectors, DNS names, or a managed AI gateway—not transparent packet interception.
Best for AI mediation and workflow orchestrationA dedicated management interface controls a bridge pair used for selected traffic. Service interfaces remain unnumbered in transparent mode.
Best for controlled inspection and local servingThe SD-WAN edge steers selected tunneled or branch traffic through EL-Ai-NE while approved DIA traffic can retain a separate breakout path.
Best for branch and multi-site policy pathsInteractive traffic lab
Choose a scenario, switch the operating mode, then pause or change the animation speed. The moving packets show request, context, policy, action, verification, and evidence paths.
The user asks EL-Ai-NE directly. Identity and policy determine whether local knowledge, a local model, or an approved external route may be used.
Direct and indirect participation
Direct use begins with a person or application request. Indirect use begins with operational state: telemetry, alerts, tickets, scheduled workflows, source changes, device posture, or a policy event.
Direct path
Indirect path
Proxy and distributed cache
EL-Ai-NE checks the local cache first, then an approved regional or peer hotset, and only then the source origin. Every reuse decision rechecks tenant, permissions, source revision, freshness, classification, and tombstone state.
An eligible website asset, document, Wiki page, attachment, or software package is fetched once, scanned, hashed, chunked, and stored under an approved content manifest.
The Site B edge performs a local lookup, discovers an eligible manifest, pulls only missing verified chunks from the nearest approved regional or peer source, and reconstructs the object locally.
ETag, Last-Modified, source revision, Cache-Control, policy epoch, and invalidation state determine when the origin must be revalidated or fetched again.
Implementation guidance
The deployment guide covers management and service interfaces, IP addressing, DNS, DHCP, NTP, certificates, firewall rules, MTU, path symmetry, SD-WAN insertion, failure behavior, and acceptance testing.