Alternative cyber models, at the edge.

With the hardware, operating system and harness to complete the cyber stack.

Request access →

Frontier cyber models are gated, and they run in someone else's cloud.

Security work needs models you can reach, on hardware you hold.

A cyber model is one layer.

Föhn builds the three beneath it, and runs all four on one machine.

L4 · Models

Cyber models that do the work.

Föhn's own tuned models, and open-weight models you own. A router picks one per task, inside the policy you set.

Föhn cyberopen weightsrouter
L3 · Harness

A harness built for security work.

It runs a campaign across the tools below it, keeps signed evidence and plugs into your SIEM.

campaignsevidenceplugins
L2 · Operating system

An operating system with the toolchain built in.

Arch-based. Pentest, fuzzing, reverse-engineering and radio tools, pinned and reproducible.

pentestfuzzingREradio
L1 · Hardware

Hardware that sits at the edge.

Inference runs on the device. SDR, LoRa, Wi-Fi and Bluetooth are built in, and the disk is keyed to you.

SDRLoRaWi-FiBluetoothkeyed disk

Four layers. One machine.

Föhn One is the complete cyber stack, at the edge.

Request access →

One machine runs the whole engagement. Scope, recon, fuzzing, evidence and report, with nothing leaving the device.

FÖHN ONE · HARNESS · ILLUSTRATIVE SESSION
operator@fohn-one:~$ fohn campaign start --scope lab-range.yaml --policy internal-red

 policy    internal-red · scope 10.20.0.0/24 · signed by you
 router    recon → föhn-recon (local) · analysis → föhn-cyber-1 (local)
 link      wired · radios idle · 0 bytes off device

 00:42  recon      14 hosts, 3 services worth a closer look
 06:10  fuzz       image parser harness, 2 unique crashes, triaged
 06:11  evidence   12 artefacts hashed and signed
 06:12  report     ./campaigns/2026-11-16/report.md

operator@fohn-one:~$ ▍

First units go to design partners. Tell us what you would run on one.

Request access →

request@fohn.ai