Product / Auth-X New

Trust every device before it earns a session.

Auth-X is a lightweight identity layer for IoT systems that need reliable trust decisions without the weight of enterprise infrastructure.

View observed results See how it works

DEVICErequest origin VERIFIERtrust decision

01 Identity requestDevice → verifier

02 Fresh challengeVerifier → device

03 Proof responseDevice → verifier

04 Session confirmationVerifier → device

Authentication flow

Four stages from device identity to a live secure session.

This is the implemented sequence: the device identifies itself, receives a fresh challenge, proves the session, and completes confirmation before traffic is trusted.

01 Identity

Start with device proof

The device opens with its identity, a fresh nonce, and an integrity check.

02 Challenge

Receive a fresh challenge

The verifier returns a session-specific challenge before any trust decision is made.

03 Proof

Prove the session

The device answers with a challenge-bound proof; identity, freshness, and integrity are checked together.

04 Confirmation

Confirm and install

Both sides confirm the session context, then the protected device session is installed.

Cryptographic foundation

Established primitives. A distinctive composition.

Auth-X brings together existing cryptographic primitives in a purpose-built, lightweight approach for connected devices.

4 PRIMITIVES / ONE APPROACH

HKDF-SHA-256

HMAC-BLAKE2s

X25519 / Curve25519

Ascon-AEAD128

Built from existing cryptographic primitives and brought together in a purpose-built lightweight approach.

Security properties

Guardrails around every trust decision.

These are properties of the authentication flow above—not additional handshake steps.

BOUND

Device-specific trust

Separate device identities let the verifier make an intentional decision for every endpoint.

FRESH

Replay-aware by design

Fresh challenge material keeps old proofs from becoming new permissions.

STOP

Fail-closed handoff

Invalid, stale, or mismatched proofs stop the flow before a trusted session is installed.

Observed lab evidence

Proof you can put next to the promise.

Results below come from the recorded 16 April EDS-3 server run and are shown as observed engineering evidence, not a universal performance guarantee.

156ms average to authentication success server-side observation

88–279ms observed authentication range across observed runs

427ms average to full session installation including secure handoff

Timing comparison

Authentication stays lightweight before session unlock.

same scale · 0–500 ms

Authentication confirmed156 ms

Secure session installed427 ms

Lower is faster. Both measures use the same observed server-side time scale.

Latency spread

The full observed authentication band.

observed runs · 0–300 ms

156 ms avg 88 279

observed range average

Each point is an observed successful server-side authentication run.