Limited offer 3 free on-site scans. Each runs for 1 to 2 weeks on a network you choose. No hardware to buy: we bring the EigenTunnel Scanner, which works fully air-gapped.

Claim a free scan
ET EigenTunnel

OEM and integrators

Evaluate quantum-resistant connections for your product.

OEM (original equipment manufacturer) access is for organizations that want EigenTunnel, our software for encrypted connections between systems, inside a product, appliance, managed service, or delivery motion. That requires commercial terms, support boundaries, and a clear IP (intellectual property) line.

Good fits

Where OEM licensing makes sense

Industrial appliances

Add protected remote access and cryptographic inventory support around legacy or hard-to-patch assets.

MSP and MSSP (managed IT and security service provider) delivery

Use EigenTunnel as a specialist capability inside a broader cyber, OT (operational technology, such as industrial control systems), or compliance service.

Defense and infrastructure integrators

Pair Core (the commercial EigenTunnel software) and EigenTunnel Console (our paid, managed service for setting up and running EigenTunnel connections) with program delivery, field evidence, and controlled deployment workflows.

Commercial package

Define the integration, license and support you need.

AreaOEM expectation
Private CoreCommercial license for product-grade features, hardened functions, packaging, and integration hooks.
ConsoleRelay/gateway connectivity has been founder-tested through Starlink satellite internet and its NAT (network address translation, which makes direct connections difficult). The Console’s payment and provisioning are unfinished; service scope and operational support must be defined per engagement.
SupportDefined engineering support, update rights, security reporting, and escalation path.
IPNo sublicensing, redistribution, reverse engineering, or publication outside the agreement.
Field useNamed pilots, approved environments, and written limits on claims.

Become an OEM

Suggested path

  1. Start with a technical fit call.
  2. Sign NDA and define the product or service boundary.
  3. Run a private Core or Console pilot against a named use case.
  4. Agree on license scope, redistribution rights, support, and claim language.
  5. Move into co-delivery or embedded product work.