Technical answers for evaluating the 21Packets network fabric.

An Endlet is a lightweight 21Packets software endpoint. It can provide routing, connectivity, or an approved service function while remaining governed by cryptographic identity, machine validation, policy, and lifecycle controls. Endlets can be deployed as virtual machines, containers, Kubernetes workloads, bare-metal processes, or approved edge deployments.

A Route Endlet participates in the fabric’s logical connectivity and protected path relationships. A Service Endlet activates an approved function—such as segmentation, firewalling, DNS, proxy, telemetry, controlled access, confidential execution, or edge intelligence—close to the systems and data it serves.

The Elastic Network Fabric is the software fabric formed by authorized Endlets across sites, data centers, clouds, workloads, provider edges, and operational environments. “Elastic” describes the ability to place and scale software functions across approved infrastructure while preserving one identity, policy, and lifecycle model. It does not require one carrier, cloud, or proprietary appliance stack.

EdgeControl is the lifecycle and control plane for Endlets. It coordinates onboarding, identity, machine validation, admission, policy, re-attestation, replacement, retirement, and revocation so network participation remains an ongoing governed state rather than a one-time enrollment event.

Route Ledger maintains path awareness. Slip-Routing uses current conditions and policy to move protected traffic toward viable routes. DEFT provides the protected fabric tunnel relationship during path transitions. NOAN contributes optimization context. Together, they are designed to preserve logical service relationships while underlay performance, congestion, routes, or site conditions change.

Yes. The fabric is designed to span approved cloud, on-premises, branch, provider-edge, industrial, workload, and edge environments. Endlets abstract the transport beneath them, allowing one operating model across infrastructure without binding operations to a single cloud or carrier.

Not by default. Endlets are software runtimes that can operate on commodity compute and approved edge hardware in multiple packaging formats. Hardware-backed confidential execution may require supported processor capabilities for the selected workload, but it is not required for every fabric deployment.

Current product architecture supports point-to-point, hub-and-spoke, and full-mesh relationships. The right topology depends on application dependencies, segmentation policy, provider diversity, locality, and continuity requirements.

21Packets continuously evaluates transport health and policy-approved alternatives. Slip-Routing and DEFT are designed to transition protected traffic away from degraded paths while preserving the logical fabric relationship, rather than waiting for a static route to fail completely. During procurement, validate continuity against the actual applications, underlays, session behavior, and recovery criteria in scope.

The software deployment model supports placing Endlets into selected environments and expanding the governed fabric from there. The rollout sequence, coexistence period, and migration boundaries should be defined during architecture review; no universal implementation timeline or cutover pattern is assumed.