What is being built. What is on the floor.
The honest answer for each line. What Varn can ship today, what is in build, and what is in the proposal stack. No future-state collages, no slides that have never been demonstrated.
Three programmes. Different stages.
Each line carries its real stage label. If something here moves to the next stage, the label moves with it. Nothing is dressed up.
- L-01 · Platform · software
Heimdall
OperatingOne picture across every sensor and asset.
The operating system. Detect, classify, task, engage, and account — under operator authority — across radar, EO/IR, RF, AIS, and satellite. Heimdall ties everything Varn ships into a single picture and a single chain of action.
- L-02 · Air · counter-UAS
Gjall
In buildAutonomous interceptor for one-way and group-launched UAS.
Aerodynamically conventional, software-defined. Designed for cost-per-engagement that matches the threat we are shooting at. Built in Denmark; first units flying. Heimdall handles the cueing.
- L-03 · Air · strike
Gungnir
ConceptLong-range autonomous strike under doctrine yet to be written.
The next step after Gjall. Range, payload, and an honest concept stage — not a marketing render of something we have already shipped. Open for partnership conversations.
The work, said plainly.
Capability claims worth a procurement officer's time. No adjectives we cannot demonstrate.
- Counter-UAS
Defeat what is being launched today.
Detection, classification, and kinetic interception of small UAS and group-launched swarms. Heimdall cues, Gjall flies. Built around the cost-per-engagement that matters in a real war.
- ISR & sensor fusion
One picture, not five screens.
Radar, EO/IR, RF, AIS, and satellite collapsed into a single track table. Operators stop translating between consoles. Heimdall is the only display in the room.
- Autonomous tasking
Humans decide. Software does the bookkeeping.
Heimdall recommends sensor moves, asset reassignments, and engagement options. The operator accepts, overrides, or vetoes. The kill chain stays under human authority, end-to-end.
- Sovereign supply
Designed and assembled in Europe.
Hardware, firmware, and software developed in Denmark. Component sovereignty wherever it can be qualified inside the European supply base, with an honest plan for everything that cannot.
- Interoperability
Speak the standards the alliance speaks.
Link 16, JADC2 patterns, OPMET feeds, and the NATO STANAGs that matter. Heimdall is built to ride into an existing operational picture, not to replace it.
- Manufacturing posture
Build rate, not unit count.
Designed for output the moment a programme of record signs. Two Danish sites, qualified European suppliers, and a deliberate focus on producibility from the first CAD review onward.
The fixed bits.
These do not move between programmes. They do not move with the customer.
- Whom we work for
- Democratic states, their armed forces, and their allies. We will not engage outside that circle under any framing, at any price.
- Where the kill chain lives
- Authority for use of force stays with the human operator. Heimdall recommends. People decide. Doctrine, not marketing.
- Classification posture
- Programmes can run up to NATO SECRET on opt-in deployments, with national-caveat handling where the customer requires it.
- Industrial footprint
- Headquartered in Copenhagen. Hardware works in Aalborg. Liaison cell in Brussels. EU and NATO interoperable by default.
Ask for the document.
The full capabilities brief is not posted publicly. It goes out by hand, to procurement offices and allied defence ministries inside the democratic circle.
Write to us from a desk we can verify. We will reply with the brief, a route to a demo, and the name of the person who will run the conversation from our side.