One core under every product: identity, cryptography, authorisation, communications, integrity.
Every Avano product is a client of one engine, the same one the messenger runs on. A maker integrates it as a library and keeps its own product; nothing here replaces a radio, a sensor or a console.
What exists of Avano Core today.
An identity nobody issues: twenty-four words make a post-quantum key pair on the device, with nothing to register and nothing to look up.
Every message is sealed end to end; relays hold same-sized sealed blocks in memory only, and a device with no relay at all can still pair and talk over its maker's own radio.
The engine as a C library for Linux on x86_64 and 64-bit ARM, with a C++ header over it since 5 November 2026: device identity, pairing, sealed messages, lock and wipe. Its headers and its C and C++ programs are compiled by strict compilers and run automatically.
A firmware image is checked against the maker's signed release before anything trusts it, and what a device produces can be signed, so a receiver can tell which device made it and that it has not changed. A signature names the device, not the truth.
A module hands its maker's code only the commands a permission signed at the maker's bench allows; a recorded command sent again, altered or forged commands nothing.
Since 4 November 2026 two devices paired through Avano can move a link the maker already runs (a serial line, its own network service) to a post-quantum key exchange signed by both devices, through one call of the library. In our tests a message changed on the way, a stranger's opening and a frame replayed or out of order were each refused, and a C program does it in our automatic checks.
What we build next, with no hardware.
The device protocol written as one specification a maker can implement against, beside the device-trust profile.
What it still needs, and from whom.
An independent audit of the core, which is the company's to commission and has not been done.
Avano Core: built.
Pre-release. Built and tested in our own laboratories: not deployed with any customer, not audited by a third party and not certified. The engineering record behind every line here is in the source, under docs/CORP/DEFENCE-INTELLIGENCE-LINE-2026-10-29.md.
All products: Products. Who they are for: Industries. How they are checked: Trust.