Free lab · Paid evaluations · Commercial licensing
Try one connection. Pay for a defined next step.
Start by exploring technical fit in your own lab. When you need engineering help, a deployment plan or integration rights, agree a scope with Eigen-Systems, Inc.
Free binary (ready-to-run program) access is manually reviewed; current package availability is confirmed before delivery. Commercial engagements are individually quoted.
Choose your next step
What you get—and why you would pay.
01 · Free evaluation access
Free lab
Explore whether EigenTunnel, our software for encrypted connections between systems, fits a connection you control.
- Public Python tools available now
- Request evaluation binaries and a two-machine quick start
- Direct node-to-node (machine-to-machine) or customer-hosted gateway (an intermediate connection point) testing
- You supply and operate the machines and network
Cost: No software evaluation fee for the standard free lab. Your infrastructure costs remain yours.
Binary delivery and included capabilities are confirmed individually. Historical builds do not establish that the latest private cryptographic profile is included.
View tools and request lab access →
02 · Quoted scope
Paid evaluation
Turn a technical question into evidence for an investment decision.
- A named connection scenario and agreed acceptance criteria
- Installation assistance within the agreed scope
- A test plan, recorded findings and explicit limitations
- A review of integration needs and next steps
You pay for: Engineering time and agreed evaluation deliverables.
Fee, schedule, responsibilities and support are written into the scope before work begins. A successful evaluation does not certify the product or establish readiness elsewhere.
Discuss an evaluation →
03 · Availability assessed per engagement
Commercial deployment
Determine what it would take to operate an agreed configuration with vendor support.
- Specified licensed capabilities and deployment boundary
- Agreed installation and operating responsibilities
- Defined update rights and support coverage
- Readiness requirements reviewed before a deployment commitment
You pay for: The agreed software rights and contracted services.
This is a scoped commercial discussion. Payment and provisioning for EigenTunnel Console (our paid, managed service for setting up and running EigenTunnel connections) are unfinished; no generally available managed service or standard response-time commitment is offered.
Discuss deployment requirements →
04 · Negotiated scope and rights
Integration / OEM
Assess incorporating EigenTunnel into your equipment, product or service (OEM: original equipment manufacturer).
- Technical fit and integration requirements
- Engineering assistance and hooks scoped to your application
- Negotiated embedding and distribution rights
- Defined maintenance, updates and support responsibilities
You pay for: Integration work and the commercial rights your product needs.
Interfaces and deliverables are assessed individually. Existing customer integrations or ready-made enterprise connectors are not implied.
Explore OEM engagement →
Before you commit
What is free, and what requires approval?
The public Python tools are available on GitHub. Standard free binary lab access requires manual registration review, with no payment or NDA required. Use a work, government or academic email; independent consultants can request individual review. Core (the commercial EigenTunnel software) source remains private and requires separately approved access terms.
Who hosts the gateway?
For the free lab, you host and pay for every node, including any gateway in your own private cloud or cloud account. Eigen-Systems-hosted infrastructure requires a paid agreement before resources are provisioned. Self-hosting a gateway does not require buying the managed Console service.
How much does a paid engagement cost?
We quote the defined scope. Connection count, environments, integration work, evidence requirements and support needs inform the quote. The written offer identifies fees, deliverables and any recurring charges; there is no self-service checkout or published standard subscription price today.
What does the license cover?
The agreement specifies the permitted capabilities, environments, endpoints or sites, term, update rights and support. Redistribution and OEM embedding require explicit rights. A lab evaluation does not grant production or redistribution rights.
What happens when an evaluation or agreement ends?
Continued binary use, renewal, updates, support and any hosted-service shutdown are addressed in the written terms before purchase. Indefinite use of paid binaries is not currently a published entitlement. The public Python tools remain subject to their published open-source license.
Does payment buy certification or authorization?
No. Payment buys the rights, work and deliverables in the agreement. Developer tests, a pilot result or draft compliance artifacts do not confer independent assurance or an agency authorization. Review the evidence and limitations before selecting a scope.
Current capability status
Private Core and the Console
The private cnsa2 profile defaults to hybrid X25519 plus ML-KEM-1024 (a classical and a quantum-resistant key exchange used together). Full PQ-only dataplane (traffic protected by quantum-resistant algorithms alone) evidence remains pending. FRA (Federal Railroad Administration) rail use is a proposed research evaluation. These capabilities do not confer FIPS 140-3 validation, ATLAS (the Department of War CIO’s Cryptographic Acquisition, Testing, and Licensing Authorization for Security review) or FedRAMP authorization.