Who a joint project is 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 performance assessment, 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.

What a pilot project means today

Ozense is in the pre-founding and development stage. A joint project is intended to assess operating requirements and prepare the next performance evidence under real conditions.

  • Development project. There is currently no series-ready or orderable product.
  • Jointly defined criteria. The operating scenario, relevant target types and measurable assessment criteria are set before a trial.
  • Site-specific validation. Range, robustness and integration are assessed for the site's actual protection geometry.
  • Unpaid and non-exclusive. Pilot projects in the current development phase are structured as joint trials.
  • Legal assessment before operation. Frequency use, data protection and operational requirements are reviewed before installation.
  • No active countermeasures. Ozense detects, assesses, documents and alerts.

What partners get out of it

  • Early insight into a technical approach and its traceable development status.
  • 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 results from reproducible tests with assessment criteria defined in advance.

How a conversation runs

01

First conversation

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

02

Operating scenario and criteria

A joint review of protection geometry, relevant target types, response paths and measurable criteria for a site-specific trial.

03

Pilot framework

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

Assess a pilot project for your site.

A short message with your role, site type and operating scenario is enough for an initial assessment.

Enquire about a pilot project

Frequently asked questions

Which enterprise sites is Ozense developed for?

For mid-sized civilian high-value sites with their own security or control-room organisation, existing or integrable PTZ/VMS technology, a concrete drone, espionage or disruption risk, and a spatially limited protection need. Priority goes to R&D, testing and prototype sites, selected sensitive industrial facilities and selected data centres. Airports, public authorities, public spaces and consumer applications are deliberately not the first market.

Is Ozense already a deployable product?

No. Ozense is a pre-founding research and development project. There is no orderable product, no released price, no series hardware and no completed field validation. The goal of the planned funding phase is a pilot-capable proof of concept.

All answers: FAQ