Research Partners and Pilot Sites

Who we are looking for

R&D, testing and prototype sites

Sites with direct exposure to espionage and know-how loss, clearly delimited sensitive areas and an existing security organisation. This is the segment being developed for first.

Selected sensitive industrial facilities

High-value production and technical installations with a concrete drone risk and a defined response process – initially as point or sector protection.

Sites with security staff or a control room

What matters is less the industry than the structure: a named security manager and a process that can actually act on a verified alert.

Integrators, installers and VMS partners

Security installers and video management partners who can judge what will genuinely integrate into an existing installation – and what will not.

Measurement and specialist partners

University institutes, test houses and radar/RF specialists for independent range calibration, antenna and RCS questions, and technical review.

User interviews with no pilot intention

A conversation with no trialling intent is valuable too: real protection geometries, approach sectors, response times and current practice are decisive for defining requirements.

The terms, stated plainly

Ozense is in the pre-founding research and development stage. What that means for working together:

Nothing is for sale. There is no orderable product, no released price and no delivery dates.
Research pilots are unpaid and explicitly non-exclusive.
No customer-specific contract development. A pilot is not an individual requirements specification.
No assured performance. What is demonstrated so far is field tracking of small drones in the region of 14–20 m; classification and PTZ integration are development goals.
Frequency clearance before any operation. Fixed-site operation on third-party premises requires its own clearance with the German Federal Network Agency. That stage is still open.
No active countermeasures. Ozense detects, assesses, documents and alerts.

This openness is deliberate. A project at this stage gains nothing from overstated promises – and a partner who agrees on a false premise does the development no good.

What partners get out of it

Early insight into a technical approach and its demonstrated limits – including the results that did not work.
Site-specific findings from real measurements about your own drone exposure, whether or not it ever leads to a procurement.
Influence on requirements while they are still open.
Traceable measurement reports instead of a performance assertion: version-bound evaluation with stated limits.

How a conversation runs

01

First conversation

30 to 45 minutes: current practice on a drone sighting, concrete incidents, protected assets, existing camera and control-room technology. No product pitch.

02

Technical assessment

A joint check of whether the required warning time and protection geometry fit today's and the forecast performance level at all. If they do not, we say so.

03

Trialling framework

If it makes sense for both sides: agreeing area, access, time window, data protection and works-council questions, and the outstanding frequency clearance.

Research partners and pilot sites