A migration bridge to evaluate
EigenTunnel is software for direct or relayed connections between enrolled systems. A scoped evaluation investigates whether connection-level protection can support a longer application or equipment migration.
Application source changes may be avoidable in suitable deployments; routing, firewall, node (a machine running EigenTunnel) or gateway (an intermediate connection point) configuration can still be required. This is not a universal compatibility promise.
The private cnsa2 profile (a set of algorithms in the private Core software) combines X25519 (a widely used classical key exchange) with ML-KEM-1024 (a NIST-standardized quantum-resistant key exchange). ML-KEM establishes shared key material; it is not a bulk-data cipher (the algorithm that encrypts the traffic itself). The combiner (how the two key exchanges are mixed) and complete protocol require independent review.
The private profile uses ML-DSA-87 signatures (a NIST-standardized quantum-resistant digital signature) for identities. Production key lifecycle and revocation assurance remain separate review work.
AES-256-GCM (a widely used standard cipher) is the private profile’s bulk cipher. Encryption applies to configured paths, not unmanaged bypass traffic or a compromised endpoint.
Relay connectivity through Starlink satellite internet and its NAT (network address translation, which makes direct connections difficult) has been founder-tested. The relay trust boundary, metadata exposure and security properties must be verified for the deployed build.
The August binary packages predate September profile work. Do not assume the free evaluation package enables the private cnsa2 profile. Profile evidence and limits.
Public Python tools plus manually reviewed binary (ready-to-run program) access. Direct or prospect-operated gateway evaluation. Your organization pays for its infrastructure; package delivery remains under review.
Define a connection, integration scope, measurements and deliverables. Company-operated hosting requires a paid scope.
EigenTunnel Console is our paid, managed service for setting up and running EigenTunnel connections. Payment and provisioning unfinished; fleet enrollment (adding many devices together), approvals and dashboards remain roadmap. No production managed-service SLA (service-level agreement) claimed.
Good evaluation candidates include long-lived applications, vendor appliances, remote facilities and research links where a companion node or gateway can be installed. Use an approved lab environment with synthetic (made-up test) data.
Not offered for classified or life-safety operations, deployments requiring validated cryptographic modules or current CNSA/CSfC qualification (NSA Commercial National Security Algorithm Suite / Commercial Solutions for Classified program), or systems where no companion component can be deployed. We do not claim anti-jamming, low probability of intercept/detection, disconnected operation or resilience against compromised endpoints.
CBOM (cryptographic bill of materials: an inventory of where encryption is used) discovery is a prototype. OSCAL (a machine-readable format for compliance documents) SSP/POA&M/AP/AR (system security plan, plan of action and milestones, assessment plan and assessment results) are working drafts; the recorded v1.2.2 schema audit failed all four. Neither constitutes authorization. No tested GRC (governance, risk and compliance tool) import or complete compliance automation is claimed.
Review the claim register and evidence gaps