Access
Verification Process
Access to sensitive unmanned systems, payloads and mission technologies must be controlled, documented and appropriate to the end user. Our verification process is designed to confirm organisational legitimacy, intended use, procurement authority and compliance context before access to restricted product information or supplier engagement is granted. The process supports responsible sourcing for public safety, civil protection, border security and defence organisations.
Who it is for
This page is for government agencies, defence procurement teams, police, fire and rescue services, border authorities, civil protection organisations and authorised public-sector buyers seeking controlled access to drone, robotic, mission software, payload or counter-UAS sourcing information.
The challenge
Public safety and defence buyers need to identify reliable systems and manufacturers without exposing sensitive procurement activity, receiving inappropriate supplier access, or bypassing compliance obligations linked to end use, export control and restricted technical information.
How we help
We provide a structured verification pathway that confirms the end user, clarifies the mission requirement, checks compliance context, aligns with supplier access rules and creates a documented trail before restricted information or supplier introductions are provided.
Why verification is required
Many drone systems, payloads, communications components and counter-UAS capabilities are subject to access controls, export-control considerations, manufacturer restrictions or national procurement rules. Verification helps ensure that information, quotations and supplier introductions are provided only to appropriate organisations and authorised representatives. It also creates a traceable record of who requested access, for what purpose, and under which organisational authority. This is not a sales formality; it is a compliance and trust requirement.
Step 1: Organisation and role confirmation
The process begins with confirmation of the requesting organisation and the individual’s role within it. This may include validating an official email domain, agency or unit affiliation, procurement responsibility, operational mandate and country of operation. Where relevant, we may request supporting documentation such as an official letter, procurement reference, government identification channel, or confirmation from an authorised supervisor. Requests submitted from personal email accounts or without a clear institutional mandate may be declined or held for further review.
Step 2: Intended use and mission context
Once organisational legitimacy is established, we review the intended use. This includes the mission category, operating environment, required capability, deployment context and whether the request relates to evaluation, procurement, integration, training or sustainment. At this stage we avoid collecting unnecessary operational details, but we do require enough context to determine whether a requested system or supplier category is appropriate. Sensitive technical specifications, controlled documentation and operationally detailed content are only shared after the relevant level of access has been approved.
Step 3: Compliance, export-control and supplier alignment
Requests are assessed against applicable compliance considerations, including destination, end user, end use, manufacturer restrictions and any relevant export-control or sanctions concerns. We also consider whether the requested capability aligns with the supplier’s own end-user policies and distribution rules. Where a request requires additional review, we may coordinate with the manufacturer or request further documentation before proceeding. No access decision should be interpreted as legal advice or as a substitute for formal licensing, import, export or procurement approvals.
Step 4: Access level and audit trail
Approved users may receive access to different levels of information depending on their verification status, project maturity and compliance requirements. Public information remains broadly available; verified-account access may include product overviews, non-sensitive comparisons and supplier background; project-verified access may be required for controlled technical documents, restricted quotations, integration details or manufacturer-led discussions. Verification records are maintained to support traceability, responsible supplier engagement and accountable procurement workflows.
Possible outcomes of a review
Depending on the review, a request may be approved, limited, redirected, placed on hold, require additional non-sensitive information, or be declined.
Frequently asked questions
Who can request verified access?
Verified access is intended for authorised representatives of government agencies, public-safety organisations, defence bodies, civil protection authorities and approved institutional procurement or technical teams. Requests from private individuals or organisations without a clear lawful mandate may be declined.
What information is required during verification?
We typically request organisational identity, professional role, official contact details, country of operation, intended use, mission category and procurement or evaluation context. Depending on the sensitivity of the requested capability, additional documentation may be required.
Does verification guarantee access to all products and suppliers?
No. Verification determines whether a requester may be eligible for a defined level of access. Some manufacturers, systems or documents may require additional review, project-specific validation, export-control assessment or direct supplier approval.
How are sensitive technical details handled?
Operationally sensitive specifications, integration details, restricted datasheets, pricing structures and controlled documentation are not distributed through open public pages. They are provided only where the requester, end use and project context have been reviewed and approved.
Is this process a substitute for export-control or procurement approval?
No. Our verification process supports responsible sourcing and supplier engagement, but it does not replace legal, licensing, import, export, budgetary or procurement approvals required by competent authorities.