01
Offline-first
Built for air-gapped networks. No cloud services, no accounts, no telemetry — and any AI runs locally.
What NOKTRA is.
A brand of offline-first desktop instruments for test and verification engineering — built for defense, aerospace, industrial and semiconductor sites where the network is deliberately absent.
NAMENOKTRA
READSnok · tra
MAKESDesktop instruments
PROMISEProof, not consensus.
01
The name
NOKTRA comes from nox — Latin for night. The night here is not a mood; it is a place: the room where the internet is switched off on purpose. Classified programs, flight-test benches, fab floors. Where other software goes blind without a connection, these instruments are built to work.
That is the whole metaphor, and this page is where it stays. Product pages and the front page say it plainly: verification tools for air-gapped environments.
nox
nightoffline by design
offlineno cloud, no telemetry
deterministicsame input, same verdict
02
How to describe it
ONE LINE
Verification tools for air-gapped environments.
SHORT
NOKTRA builds desktop instruments for defense, aerospace, industrial and semiconductor test engineering. Single-file deploys, golden-vector suites, no telemetry — everything runs where the internet doesn't reach.
FULL
NOKTRA builds desktop instruments for test and verification engineering — interface definition, MIL/SIL execution, test sequencing, telemetry, protocol work and reliability analysis. Every instrument is offline-first: it ships as a single executable with its golden-vector suite embedded, phones home for nothing, and any AI runs locally on the engineer's own machine. Deterministic checkers issue every verdict; AI only proposes; a human approves what ships. Proof, not consensus.
Fixed phrases
SloganProof, not consensus.
WordmarkNOKTRA
NeverNoktra.io™, NOKTRA Suite
Principles
Three commitments, one order.
Every instrument keeps all three, and authority always flows the same way: AI proposes, deterministic checkers judge, the engineer approves.
02
Deterministic
Golden-vector suites ship inside every build. The same input gives the same verdict today, next quarter, and in the audit.
03
Single-file
One executable, copied onto the target machine. No runtime installs, no package managers, no IT ticket.
Structure
Five verbs organise the catalog.
Every instrument answers to exactly one verb — what it lets an engineer do.
DefineICD RefineryNK-01
RunSIL RuntimeNK-02 · Test SequencerNK-03
ObserveTelemetry ScopeNK-04 · Ch10 ViewerNK-05
ConnectProtocol BridgeNK-06 · SECS/GEM WorkbenchNK-07
AssureRAM ToolkitNK-08 · Local Test CopilotNK-09
Visual identity
Dark canvas, one accent, zero radius.
The look is an instrument panel, not a landing page. Values live in styles/tokens.css; nothing is styled ad hoc.
--accent
#31A9BC / #12707F
The single accent. Links, ticks, Available.
--bg
#0B0E0F / #F3F2EE
Page ground.
--surface
#151A1C / #FBFAF8
Raised cells and panels.
--text-strong
#F4F6F6 / #0E1213
Display type, product names.
--amber-text
#D2A253 / #7E5A12
Beta state. Never decorative.
--mute-text
#8A9396 / #646B69
In development.
Type
DISPLAYNewsreader (serif)
UIIBM Plex Sans
DATAIBM Plex Mono
Rules
RADIUS0 — always
LINES1px hairline
LABELSmono · uppercase · tracked
Voice
How it speaks
States, plainlyShort declaratives. Concrete nouns. A claim is either backed by a golden vector, a spec citation or a repository — or it is not made.
Admits limitsIn-development means in development. What a tool deliberately does not do is stated on its page, up front.
Never says"Revolutionary", "AI-powered" as a virtue, "coming soon" with a date it cannot keep, or any claim that requires trusting us instead of running the vectors.
One brand, five verbs, nine instruments — and a promise every page repeats: run it yourself, with the network unplugged.