Partners

A defined boundary is worth more than a broad claim.

Tunnel builds one layer and states where it ends: endpoint cryptography, mission authority, bundle format, custody logic and administration. Radios, satellites, hardened handsets, hardware security modules and accredited data centres belong to partners who build them properly. Partnership works because that line is written down.

  • Defined interface
  • Joint delivery
  • Customer data rights
  • Technical workshop
The partner integration boundaryTunnel supplies the application layer: endpoint cryptography, mission authority, bundle format, custody and delivery logic, and administration. Partners supply the layers Tunnel does not build: hardened devices, radio and SATCOM links, waveform behavior, hardware security modules and sovereign hosting. The boundary between them is an interface, and each side is accountable for its own layer.TUNNEL PROVIDESEndpoint cryptography and key rolesMission and communication authoritySecure Mission Bundle formatCustody, scheduling and expiration logicAdministration and device lifecycleSigned software and policy distributionINTERFACEPARTNER PROVIDESHardened and purpose-built devicesRadio and SATCOM linksWaveform, LPI/LPD and jamming resistanceHardware security modulesSovereign and accredited hostingField integration and sustainmentJoint customer value comes from a defined interface, not from either side overstating the other’s layer.
Radio-layer performance and protection depend on qualified communications hardware and integration partners. Tunnel makes no waveform-layer claim.

Who we work with

Where Tunnel fits into an existing program

Tunnel is usually one layer of a larger program: the layer that determines whether the rest of the solution can be trusted with what it carries.

Prime contractors
Tunnel supplies the secure communication layer inside a larger program, under the prime's delivery structure and the customer's accreditation path.
Systems integrators
Tunnel integrates with the identity, directory, operational and monitoring systems the integrator is already responsible for.
Hardened-device manufacturers
Tunnel Mobile runs on the device; the manufacturer supplies platform integrity, secure elements and the physical security posture.
Radio manufacturers
The Secure Mission Bundle is transport-independent. The radio supplies the link and every property of the link.
SATCOM providers
Store-carry-forward and priority scheduling are designed for constrained, intermittent, high-latency links of exactly this kind.
HSM providers
Sovereign deployment holds the enrollment and signing authority in customer-managed hardware security modules, under the customer's key ceremony.
Sovereign hosting providers
Deployment into hosting the customer's own authority has approved, inside the jurisdiction the customer requires.

The interface

What each side is accountable for

The integration boundary is not a diplomatic formula. It determines who answers which question during a technical evaluation, and who carries which risk in delivery.

Tunnel provides

  • Endpoint cryptography and the key-role model
  • Mission and communication authority
  • The Secure Mission Bundle format
  • Custody, scheduling, expiration and replay logic
  • Administration, enrollment and device lifecycle
  • Signed software and policy distribution

The partner provides

  • Hardened and purpose-built devices
  • Radio, SATCOM and proximity links
  • Waveform behavior and physical-layer protection
  • Hardware security modules and key ceremony support
  • Sovereign, accredited or on-premises hosting
  • Field integration, deployment and sustainment

Radio-layer performance and protection depend on qualified communications hardware and integration partners. Tunnel makes no waveform-layer claim, and expects the same precision in return.

Commercial model

How a partnership is structured

Integration discussions move faster when the commercial and data questions are answered early rather than at contract.

01

Joint customer value

The customer buys an outcome. A defined interface lets a partner bring Tunnel into a program without either party inheriting the other's technical risk or making claims on the other's behalf.
02

Data rights

Customer data, enrollment authority and audit records stay inside the customer's domain in a sovereign deployment, including where a partner operates the surrounding program.
03

Deployment model

Partners deliver against Managed or Sovereign deployment. Programs with accreditation requirements are usually Sovereign, and that shapes the integration from the start.
04

Controlled evaluation

A joint evaluation with defined scope and defined questions, so the customer sees the combined system rather than two separate demonstrations.
05

Technical workshop

A working session between engineering teams to establish the interface, the responsibilities on each side and what integration would actually require.
06

Interface documentation

The boundary is documented as an interface with named responsibilities, so a customer's evaluator can see which organization answers which question.

How we talk about partners

Partnerships built on documented responsibilities.

This site publishes no partner logos, customer names, contract values or evaluation outcomes, because none has been agreed for publication. In this market a fabricated reference is not an embellishment. It is a disqualifying finding, and in some acquisition contexts it carries legal consequence.

  • No partner, customer or program is named without that organization's agreement.
  • No evaluation outcome, endorsement or past performance is represented that does not exist.
  • No claim is made on a partner's behalf about their layer.
  • Tunnel expects the same standard in joint material.

Strategic integration

Start with the interface, not the announcement.

Tell us what layer you supply and which program you are pursuing. If the boundary is clean, the next step is a technical workshop between the engineering teams.

Discuss Strategic IntegrationTactical Profile