Skip to content

Software License Dongle for Scientific & Engineering Software

Scientific software is bought by institutions and used by whoever is in the lab this semester. Licensing here has to survive shared machines, rotating users, IT departments with strong opinions — and instruments that are never allowed near the campus network, let alone the internet.

A floating license without the license server

The traditional answer for labs is a network license server — the FlexNet kind: a dedicated machine, an open port, a daemon someone has to keep alive, and a queue of tickets when it dies. A dongle is the floating license with the infrastructure removed: the seat is wherever the key is, it moves between the shared analysis PC and a postdoc’s laptop by walking across the room, and nobody administers anything.

Lab machines are appliances

The PC attached to a microscope, a spectrometer or a test rig is managed like part of the instrument: imaged once, offline by policy, untouched for years. Software licensed to that machine cannot depend on activation servers or background services. A KeyNub is a standard HID device — no driver, no service — and one library beside your application, which is the entire footprint the instrument’s documentation has to mention.

Gate the science, not a boolean

The strongest protection for a solver or analysis package is to make the license the source of something the computation needs: material databases, calibration models, solver coefficients, trained networks — shipped encrypted, decrypted through the dongle at run time. A patched binary does not become a free copy; it becomes a solver with no physics in it. And for expensive operations sold by the run, the key’s built-in counters meter usage with one API call — no bookkeeping subsystem, no server.

The languages science actually uses

This is the industry that keeps our more academic bindings honest: Python for everything, MATLAB and Simulink for engineering, Fortran because the solvers never left it, Julia where the new work happens, and C++ underneath. Every one is published with a runnable sample — including the Fortran.

All industries · All supported languages · Buy a KeyNub · Ask us something

KeyNub

A project of AB-Tools GmbH.
Address: Marsstraße 78 · 80335 Munich · Germany
Phone: +49 89 38898588 · Fax: +49 89 38898589
E-mail: info@keynub.com

Managing Director: Andreas Breitschopp
Commercial register HRB 202859 · Amtsgericht München (Munich local court)
VAT ID DE268720895 · Munich tax office for corporations
Grenke Bank AG · IBAN: DE49201304000060270139 · BIC: GREBDEH1XXX

Developers · Payment Methods · Shipping · Terms & Conditions · Right of Withdrawal · Privacy Policy · Legal Notice