VAERNSYSTEMS
Contact
Home / Platform The platform

One fused air picture. One accountable decision.

VAERN's platform turns whatever sensors are available — ours, yours or third-party — into one explainable picture of the drones in your airspace, and leaves every decision that matters to a person. Software-defined, vendor-independent and built to deploy forward.

The layer

A decision & control layer — not a weapon.

VAERN is the software-defined layer between sensors and response. It fuses what stands on the site or in the field into one track picture, classifies each track with explainable edge-AI, and gives the operator one clear choice — with both the evidence and the decision logged. VAERN supplies no effect: if an effector is needed, it is a later-phase integration through an authorised partner.

  • Multi-sensor fusion — radar, passive RF and EO/IR, from VAERN or third-party sources, combined into one air picture.
  • Explainable edge-AI — classification you can audit, at the edge.
  • Operator supported by AI — a person authorises every consequential decision.
  • Dual-use by design — effectors via an authorised partner, later phase.
  • Vendor-independent — the fusion layer does not require VAERN hardware.
01SENSORSradar · passive RF · EO/IR · third-partyEXISTING3RD-PARTYVIGILDATA02MESHresilient datalink · store & forwardNEXUSSCOUTDATA03EDGE AIfusion · classification · audit trailCOREDATA04OPERATORone fused picture · one accountable decisionHAMMERSYSTEM BOUNDARYEFFECTOR — PARTNEREFFECTOR — PARTNEREFFECTOR INTERFACEAUTHORISATION — HUMANAUDIT LOGFIG · PLATFORM ARCHITECTURE
FIG. 01Technical figure — drawn from the system, not photographed.AI CONCEPTThe operating environment the platform is built for. AI-generated scene.
Architecture

Six modules, mapped to the loop.

A / 01

The six modules are what we build. CORE and HAMMER carry it: they fuse whatever is available — your existing radar, RF or cameras included — and hand the operator one picture. Sensing, forward nodes and mesh are added where the site needs them. Status today: early prototype, TRL 3–4 — what is built and what is still design intent is on the Investors page.

Module register

What each module does — and what it does not.

A / 01.1
Six modules — function, name, boundary
Function Name Does Does not
Sensor VIGIL Detects and tracks: radar for range and speed, passive RF for the control link, EO/IR for identification. Third-party sensors enter through the same interface. Does not classify, and does not decide. Detection is the start of the loop — never the decision.
Forward sensor node SCOUT Carries the sensing forward — tripod or vehicle — so coverage follows the force rather than the map. Is not a precondition. The fusion layer also runs on the sensors already standing on the site.
Datalink / mesh NEXUS Links the nodes into one network. Routes around a lost link, and the node buffers locally until it is back. Does not replace your existing comms, and does not require one central point everything must see.
Edge AI CORE Fuses every source into one track and classifies it — with the evidence behind each call kept for audit. Does not act on its own conclusion. It produces a recommendation, not an engagement.
Command & control HAMMER Shows one fused air picture and one clear choice — and records who authorised what, when. Does not automate the decision. No consequential call happens without a person.
Effector interface STRIKER Hands an authorised decision to whichever effector the operator already holds. Effector-agnostic by design. VAERN supplies no effect and describes none. Integration is later phase, through an authorised partner under national regulation.
How it works

From detection to accountable decision.

A / 02
01DetectVIGIL

Multi-sensor detection: radar, passive RF and EO/IR — VAERN's own or existing third-party sensors.

02ConnectNEXUS · SCOUT

Resilient mesh links forward nodes into one network.

03UnderstandCORE

Explainable edge-AI fuses sensors and classifies tracks.

04DecideHAMMER

The operator sees one air picture and authorises the response.

05EffectPartner

Effectors integrate later via an authorised partner — effector-agnostic by design.

Deployment

Built mobile, forward-deployed and open.

Fixed sites or on the move, the same layer travels with the force. A modular sensor mesh scales from a single node to a network and takes in what is already there: your existing sensors and C2, third-party radar, RF or cameras, and whichever partner effectors you already operate. Dynamic deployment & architecture, vendor-independent, no rip-and-replace.

  • Open / interoperable architecture — no vendor lock-in.
  • Fixed & mobile deployment.
  • Modular sensor mesh — scales with the task.
  • Integrates with existing C2 and existing sensors.
  • Partner-effector flexibility — effector-agnostic interface.
Compliance

Built to the rules on ownership, supply chain and human control.

A / 03
≥60%
Danish capital — design target under the Danish ownership rules
≥80%
Danish board — design target under the same rules
Art. 10(6)
human in the loop — the condition for eligibility under the EDF
European
/ Western supply chain

Design targets, set against the Danish and EU rules on ownership and funding eligibility — not certifications. VAERN holds no certifications today, and the company is still a sole proprietorship: capital and board belong to the planned ApS.

Guided walkthroughHAMMER · C2
See what the operator sees

Thirty minutes in the console says more than the rest of this page.

We run the HAMMER operator console with you: five deployment scenarios, from airport to mobile convoy, multi-sensor fusion, and the decision the operator has to authorise. The scenarios are synthetic and the commands simulated — we say so before you ask.