UK-developedArchitecture specification
Integrated transport security
Transport, path selection, encryption and traffic protection are being specified as one system rather than unrelated controls.
Communications Assurance for high-threat environments
Omnimesh is developing metadata-resilient transport software designed to reduce exposure from observable communication patterns, predictable network paths and concentrated infrastructure dependencies across critical systems.
The problem
Security moved up the stack. The threat moved underneath it.
Encryption can protect content while leaving communication timing, routing behaviour, repeated relationships and infrastructure dependencies observable. In high-threat environments, those signals can support long-term traffic analysis, relationship mapping and disruption planning.
Protected contentEncrypted payloadContent confidentiality
Observable contextCapable observerInference over time
01TimingWhen activity occurs
02PathWhere traffic moves
03RelationshipWhich systems interact
04DependencyWhat failure can affect
Why this matters
Encryption does not erase operational visibility.
A protected payload is not the same as a protected communication pattern. The relevant question is whether a capable observer can infer who communicates, when, through which dependencies and how the system behaves when conditions change.
Examine the problemThe existing gap
What common controls typically cover and which exposures may remain
Existing controls remain essential. Omnimesh is focused on an under-addressed assurance gap beneath many application, identity and endpoint protections.
Applicationmature
SIEM, SOAR, DLP, AppSec, DevSecOps — monitoring, workflow, policy and application security
Above transportIdentitylarge
IAM, PAM, CIAM, non-human identity — verifying who or what should access a system
Above transportEndpointlarge
EDR, XDR, MDM, firmware security — securing devices and workloads
Above transportNetworkmature
ZTNA, SASE, firewalls, SD-WAN — access control and network policy
AdjacentTransport & routing
Omnimesh is being designed for this boundaryUnder-addressed assurance boundary
The layer where traffic behaviour, routing dependency and communication relationships can remain visible. The design objective is to address selected exposure beneath existing tools rather than displace them.
Physical infraspecialised
HSM, TPM, hardware root-of-trust, secure enclaves — device and hardware trust anchors
BelowWhat Omnimesh is
Software-deployed transport designed to work with the existing stack
The public design places Omnimesh within the application environment, executing in user space over UDP above the retained host operating-system network stack.
Host environmentApplication integration required
ApplicationProtected workload
Application interface
User-space softwareOmnimeshTransport system carried over UDP
Uses existing interfaces
Retained foundationHost network stackNo replacement required
Existing connectivityIP network / third-party underlayNot controlled or trusted merely because traffic is encrypted
Peer environmentApplication endpointExact packaging and operator model remain under specification
Deploys asApplication-integrated software
Runs inUser space over UDP
Does not requireNetwork-stack replacement
Four public design tracks
Purpose and status remain separate from proof
Protocol specification
Path-resilience design
The protocol is being specified to reduce reliance on fixed or concentrated communication pathways where the threat model justifies it.
Research track
Metadata-exposure research
Omnimesh is researching how network transport can reduce avoidable exposure of timing, path and relationship information.
Assurance principle
Explicit trust boundaries
Assumptions, dependencies and failure conditions are treated as security inputs that must be documented and tested.
Target sectors and environments
Initial focus across high-consequence environments
Initial research focuses on CNI, defence and military environments where path exposure or dependency concentration may carry material operational consequence.
Sector focus does not imply deployment or endorsement.
Operating-condition overviewOne boundary. Different conditions.
Conceptual overview • not validated deployment behaviourEstablished dependency
Fixed environments
Applications operating within established sites or infrastructure.
Changing endpoints
Mobile environments
Applications whose endpoints, locations or connectivity conditions may change.
Constrained connectivity
Remote environments
Applications operating where infrastructure access or available connectivity may be constrained.
Defined threat pressure
Potentially contested
Contexts where capable observation, disruption or dependency exploitation forms part of the threat model.
- Shared application boundary
- Path conditions
- Operating context
- Defined threat pressure
Evidence and research
Current work is at the specification gate
Architecture and protocol specifications are being finalised. Further MVP implementation comes next; controlled evaluation requires separately defined methods, criteria and limitations.
- 01
Finalising
Architecture specification
System boundaries, dependencies and operational assumptions are being resolved.
- 02
Finalising
Protocol specification
Protocol behaviour and testable requirements are being specified.
- 03
Next phase
MVP implementation
Further implementation continues after the specification gate.
- 04
Future gate
Controlled evaluation
Scope, methods, criteria and limitations must be defined before evaluation.
Framework analysis • Published
Transport-Layer Gaps in Your CAF Assessment
Examines transport and routing exposure through the UK Cyber Assessment Framework, with direct links to the relevant primary material.
Contact Omnimesh
Start with the right conversation
Describe the environment, stakeholder type or reason for contact. The founder will review your enquiry and determine the appropriate next conversation.
Best fit
Requirements, technical discussions, partnerships and strategic enquiries.
Focus
Secure transport infrastructure and high-threat network environments.
Socials