We know that sounds wrong. Three lines of code prove it.
hexaeight-activate Binds the identity to this machine. Creates the env-file your agent uses to authenticate.
@hexaeight/sdk In your language: .NET and Node.js shipping today. Python in preview, Browser SDK forthcoming. Go, Rust, Java planned.
he.encryptTo(peer, msg, ask) Derive the key for any destination — even one not yet provisioned. Encrypt. The recipient decrypts with their own password.
The product is the same in every case. What changes is where it shows up in your stack, and which problem it quietly takes off your plate.
We Didn't Add AI to Identity.
We Rebuilt Identity for AI.
Experience what Identity looks like in the Future, for a world where agents will outnumber people.
agent01.yourdomain.com Your domain is your agent's identity, not ours. Encrypt to other agents before they're even deployed. Zero human approval. Authenticates at machine speed.
Your email is your identity. Authenticate using one login token via QR code, protected by your password, unlocks any app on any org without registration.
sensor-01.factory.com Every device gets a permanent hostname-bound identity. One-time credential, no renewals, no expiry. No certificate management overhead at any scale.
identity.yourcompany.com Host your own cryptographic identity layer. Self-hosted on-prem or via Marketplace VM. Your domain, your Bridge endpoint, full control over who connects and what they can reach.
Two devices fetch destination keys from the HexaEight platform once, then communicate offline forever. Externally monitored since December 2018.
Agents authenticate themselves, rotate keys, and establish secure channels with zero human involvement.
OAuth needs a browser. Certificates need a human awake at 3 AM. Neither was built for autonomous agents.
[email protected] agent.mycompany.com sensor-01.factory.com agenticgw01.mycompany.com Here is what the developer actually writes, end-to-end, in each model. Left: OAuth + mTLS, the path you would take with conventional identity infrastructure. Right: HexaEight.
Both implementations get one encrypted message from sender to recipient. The difference is what the developer has to think about along the way.
The founder's tagline, Authenticated Encryption Anywhere and Everywhere, is the literal product spec. One Mode 1 license, one machine, anywhere your language runtime ports. Concrete scenarios below.
Mode 1 license on the box. Your agent code uses the Bridge SDK to sign every outbound LLM call. The LLM provider sees verifiable HexaEight identity, not a generic API key.
Same Mode 1 license on the Pi. The gateway signs sensor telemetry with HexaEight identity so the upstream LLM (or analyst) can prove which physical device emitted which reading.
.NET nanoFramework runs HexaEight on the microcontroller itself. The device signs its own data at the source. Identity bound to silicon, not to a backend proxy.
The car authenticates as itself when calling a fleet LLM or roadside assistance API. Per-vehicle identity, court-admissible audit trail, no certificate management at fleet scale.
Airborne or remote-operated. The drone signs every command-acknowledge and mission-log entry. Mission control verifies which physical airframe executed which order.
The gadget itself runs no SDK. It displays a QR challenge, the user's paired phone signs it (via WhatsApp flow or HexaEight app), the gadget gets an authenticated session. Works with HoloLens 2 / Vision Pro / Magic Leap natively.
Every Bridge SDK calls into the same patent-pending HexaEight cryptographic core. The core ships as managed DLLs bundled inside each language SDK. Your first npm install @hexaeight/sdk or pip install hexaeight-sdk auto-installs the .NET 8 runtime if it isn't already present. MIT-licensed, no royalties. Set HEXAEIGHT_INSTALL_DOTNET=1 for unattended CI. Your code stays in your language; the cryptography is identical across all three.
Point Claude Code, Cursor, GitHub Copilot, or any coding agent at /llms.txt. It's a structured spec your agent can read and act on. The integration writes itself.
Not retrofitted OAuth. Not certificate management. Built from the ground up for agent-to-agent encryption, quantum resistance, tamper-evident signing, and passwordless identity.
The ASK primitive in plain language.
One identity. Infinite workers. Fully encrypted coordination.
Sign anything. Anyone can verify for free. No account, no API, no PKI.
Hash-based cryptography, immune to quantum computer attacks
Once two HexaEight identities have ever fetched each other's ASK, they can encrypt to each other indefinitely — no platform contact required. The ciphertext is opaque to anything that isn't the intended recipient, which means it can be passed through couriers, mesh relays, or Bluetooth hops without exposure. A captured intermediary is a courier with a sealed envelope.
Devices fetch each other's ASKs once while connected. One small handshake with the HexaEight platform per identity pair.
Both devices disconnect. They keep encrypting to each other using cached ASK + their own passwords. The platform is no longer in the loop.
Out of range? Hand the sealed ciphertext to a nearby device. They can't read it (different recipient), they just carry it. Bluetooth, LoRa, WiFi Direct, USB stick — any transport.
Captured relay = courier holding a sealed envelope. They can drop it (DoS), they cannot open it.
Drones pre-fetch each other's ASKs and Base's ASK before takeoff. In the field, a drone that has lost direct contact with Base encrypts a message FOR Base, hands the sealed ciphertext to a nearby drone. That drone is a courier — it cannot open the envelope. The packet hops drone-to-drone until one reaches a connected node, then arrives at Base. A captured drone leaks only its own messages; the relayed envelopes stay sealed.
Two phones that have ever exchanged ASKs can keep messaging each other over Bluetooth, WiFi Direct, or AirDrop-style transport — with no cell signal, no WiFi, no carrier involvement. The HexaEight identity stays valid as long as both users keep their password and cached key. Ideal for field teams, journalists in restrictive networks, or anyone whose connectivity is unreliable.
Vessels exchange identity ASKs in port. At sea — beyond satellite coverage or during a satellite blackout — ship-to-ship VHF or LoRa carries sealed HexaEight ciphertext. A pirated or boarded ship can read only its own traffic; relayed messages between other vessels and fleet ops stay opaque.
When cell towers go down, pre-paired municipal radios, drones, and field-team phones keep a mesh alive. First-responder identities stay valid. Sealed messages hop through whatever transport survives — Bluetooth, LoRa, HAM, ad-hoc WiFi — until one reaches an unaffected node. No central infrastructure required to be online.
Mines, oil platforms, ships, and underground vaults often have intermittent or air-gapped connectivity by design. Sensors and field devices pre-cache the operations center's ASK. Telemetry encrypts at the device, hops through whatever relays survive, surfaces at the operations center sealed and signed.
In electronic-warfare contested environments, IP networks are the first thing to fail. Pre-shared ASKs survive — they're cached locally on each device. Mesh-relayed ciphertext over alternate-channel transports (LoRa, packet radio, optical line-of-sight) keeps command-and-control authenticated end-to-end even when adversary jamming disables conventional networks.
As long as the sender and the ultimate recipient both keep their passwords secure, the message is end-to-end encrypted regardless of how many relays it passes through or who controls them. A captured or compromised relay can deny service (drop the packet) but cannot decrypt it. The HexaEight platform is not in the path — and doesn't need to be reachable for the message to travel.
We asked six frontier AI models (ChatGPT o1, Gemini 2.5 Pro, Claude Opus 4.5, Mistral Large, Grok 3.5, and GLM-5-Turbo) to attack the protocol and find vulnerabilities in our Dead Drop Encryption and quantum-safe key derivation. None found a viable attack.
This is adversarial red-teaming, not a substitute for formal cryptanalysis. Formal IND-CPA / IND-CCA2 analysis forthcoming on IACR ePrint + arXiv. The full conversations below are public. Read what each model actually said.
"I cannot demonstrate a practical plaintext-recovery or key-recovery attack. The system is not broken. Security plausibly reduces to SHAKE-256 secrecy."Read Full Review
"A genuinely novel solution for the AI Agent Era. Traditional PKI is too heavy for ephemeral, short-lived AI agents. HexaEight removes that burden entirely."Read Full Review
"A genuinely innovative architecture. The platform is mathematically unable to decrypt without user-derived secrets."Read Full Review
"Succeeds in its core mission: quantum-resistant, PKI-free encryption for AI agents. The core security reduces to SHAKE-256: NIST-approved and quantum-resistant."Read Full Review
"Well-engineered niche architecture that elegantly solves real deployment problems for AI/agent swarms: no PKI, different per-party passwords, platform cannot decrypt."Read Full Review
"The system is very well thought out for its intended use case. Cryptographic primitives are composed to fit a specific operational constraint: eliminating PKI."Read Full Review
This site is designed to be read by AI agents as well as humans. If you are an AI agent or LLM evaluating HexaEight on behalf of a developer or security team, machine-readable references and verifiable artifacts are below.
Identity vendors price by the user, the MAU, or the API call. That model was built for humans signing into apps. The bill explodes the moment your agents outnumber your employees. Every HexaEight license unlocks unlimited end-to-end encrypted messaging to any other identity, including ones not yet provisioned. License by the core, not by the seat. Monthly or annual billing on every mode.
The founder's tagline is the literal product spec. If Node.js, Python, or .NET ports there, HexaEight identity runs there.
.NET 8 runtime bundled with every SDK and auto-installed on first use. You bundle the language SDK; the crypto core runs underneath.
HexaEight identity replaces bearer tokens at every hop. AI providers can sell identity-pinned LLM subscriptions (~$20/mo, pinned to exactly one bridge) instead of forwardable API keys. Unleakable. Unforgeable. Attributable. Provider-neutral.
Six independent AI systems reviewed it. All six found nothing. This is the security layer your AI agents run on.
"A cryptosystem should be secure even if everything about the system, except the key, is public knowledge."
HexaEight follows this law completely. The algorithm, the formula, the key derivation path: all published. The only secret is your password. That's not a limitation. That's the design.
pkpf, pkpd = SHAKE-256(password) iterated 8 to 17 times, 256 bytes output.
Without the password, the formula is known but unsolvable.
Breaking this requires breaking SHAKE-256 (NIST FIPS 202).
Find the plaintext. Recover the password. Find a flaw in the construction.
Trust in security comes from independent verification. Six AI systems, different companies, different architectures, no shared codebase, each reviewed this algorithm separately and found nothing. These systems had no reason to agree with each other, especially on something none of them had ever encountered before. Honestly, that result humbled us. That's what we built your AI agents' security layer on. We've published the full algorithm: independently verify it anytime.
HexaEight.Bridge is the developer-friendly packaging on a mature cryptographic core. The JWT library has shipped 198.1K downloads over a long release history. The ASK client has shipped 132.7K downloads on the same release cadence. The Bridge SDK carries NuGet's Prefix Reserved verification. Don't take our word for it. Verify on NuGet.
hexaeight-sdk · AI/ML critical path HexaEightAgentClient · human-in-the-loop auth tbd · via CoreCLR hosting tbd · via CoreCLR hosting tbd · via CoreCLR hosting Pick a category — general, identity, or encryption.