06 / Company and trust

A UK company, clear about its current stage

Omnimesh Ltd is developing application-integrated secure transport software for high-threat network environments. The company is registered in England and Wales, and its architecture and software-development work is currently carried out by a UK-based team.

The product remains at architecture and protocol-specification stage. It is not presented as production-ready.

Company facts

Corporate identity and current status

Registered company details, current product maturity, organisational certification and the direct contact route.

Legal entity
Omnimesh Ltd
Company number
17095535
Registered in
England and Wales
Product stage
Architecture and protocol specification
Organisational assurance
Cyber Essentials certification
Founder contact
support@omnimesh.co.uk

The official Cyber Essentials verification badge and public certificate link appear in the site footer. Certification scope remains organisational, not product assurance.

UK-developed

Development work is carried out by a UK-based team

Current development locationEvery individual currently carrying out Omnimesh architecture and software-development work is based in the United Kingdom.
Supply-chain boundaryThird-party tools, dependencies, hosting services and other supply-chain components are not represented as universally UK-origin or UK-hosted.

Current team

Experience across systems, identity and infrastructure

Omnimesh combines company and product direction from the founder with technical experience spanning large-scale security engineering, identity governance and enterprise infrastructure.

FounderLeads company and product direction.
01

Senior systems architect

Steve

Steve brings 20 years of IT experience spanning security architecture, security engineering and operational security in complex financial and enterprise environments.

His technical background includes Splunk. At Barclays Capital, his remit expanded from security architecture into responsibility for security engineering. He also led integration work associated with Lehman Brothers across two banking environments.

His Army background includes electronics work with the British Army’s Royal Electrical and Mechanical Engineers and five years supporting a special forces unit.

  • Security engineering operations
  • DLP and IAM
  • SIEM and threat detection
  • Complex banking integration
02

Solutions architect / security engineer

Adeeb

Adeeb is an IAM and security engineer with around eight years of experience owning identity governance, privileged access and security-control strategy across highly regulated public-sector and enterprise environments, including NHS England and Tesco.

He specialises in Azure and Microsoft 365 security, Entra ID, Conditional Access, MFA, PIM, RBAC, SSO, Identity Protection and zero-trust architecture. His work combines hands-on engineering with governance, remediation and audit-ready control evidence aligned with ISO 27001, NIST and CIS frameworks.

  • 68,000+ role assignments audited
  • Privileged-access reduction through PIM
  • Sentinel and KQL control validation
  • Joiner–Mover–Leaver automation
03

Infrastructure engineer

Zain

Zain is an infrastructure engineer with more than seven years of experience supporting, maintaining and improving enterprise IT environments for secure, reliable business operations.

His experience spans virtualisation, cloud services, networking, cybersecurity and Microsoft platforms, including VMware, Windows Server, Active Directory, Microsoft 365, Entra ID, Cisco networking, backup and disaster recovery, endpoint management and security operations.

  • Enterprise infrastructure
  • Cloud and virtualisation
  • Networking and identity
  • Resilience and recovery

Named organisations describe previous professional experience only; they do not endorse Omnimesh or validate its product.

Security contact

Report a security concern

General enquiries are handled at support@omnimesh.co.uk.

Potential vulnerability reports should follow the responsible-disclosure guidance. Do not include sensitive exploit details in an initial email; an appropriate exchange route can be agreed first.

Review responsible disclosure