Training devices are the clearest case for hardware licensing in all of software: the device is the product, its configuration is often frozen by qualification, and it may sit on a network where cloud activation is not just impractical but prohibited by policy.
Networks where activation cannot go
Simulators for aviation, maritime, driving and defense training routinely run on closed networks — sometimes classified ones — where a component that wants to reach a license server is disqualifying no matter how good it is. A KeyNub never asks: verification is a local challenge–response against keys in the dongle’s secure element. No server, no periodic reactivation, no exception request to the network owner.
The device is the licensed unit
A training device is many computers — image generators, the instructor station, avionics and systems hosts — but it is one product, and it is bought and audited as one. That maps naturally to one dongle, typically at the instructor station or host: the device is licensed where the device is operated. What it is licensed for — vehicle or aircraft types, visual database regions, weather and motion options — lives as records on the key, so enabling an option is a maintenance-window record write, not a re-image of half a dozen machines.
Qualified means frozen
Once a training device is qualified, its software stack stops changing casually — every modification is paperwork, and a vendor component that auto-updates or demands periodic online renewal does not belong in it. KeyNub’s runtime footprint is one versioned library with published source for the bindings and checksummed releases: the kind of component you document once and leave alone for a decade, and because verification is local it will still verify in year ten without anyone’s server cooperating.
Flight-simulation add-ons
At the prosumer end — aircraft add-ons, scenery, cockpit hardware tooling — the market is global, enthusiastic and heavily pirated. Per-aircraft licensing is one record per product on the customer’s key, and the gate-the-data pattern works unusually well here: ship the flight model or systems-logic data encrypted and decrypt it through the dongle at load, and a copied add-on installs but does not fly. The ecosystem’s languages are covered — C++ for the sim platforms, C# for tooling, Lua where scripting engines rule, and Delphi in more long-lived cockpit software than you would guess.
All industries · All supported languages · Buy a KeyNub · Ask us something
