Classical
- AES-256-GCM
- ChaCha20-Poly1305
- X25519
- ECDSA
Every company has its own security representation. The ONE SDK stands up a private sandbox around yours: existing primitives, hybrids, and ONE inventions, picked from a factory that already proved them.
Capabilities do not exist until the handshake is yours.
sandbox flow · 01 invite
Closed room01
Invite
02
Map
03
Select
04
Compile
05
Prove
06
Unlock
A private sandbox. Named principals only. Nothing is public, and nothing is on until you are in.
Named seats. A sealed environment. The kit is not a download.
A private sandbox. Named principals only. Nothing is public, and nothing is on until you are in.
invite-only sandbox · unique representation
sealedAcme Global · Production
spec v7 · hybrid ML-KEM ∥ X25519 · ONE handshake
01
Invite
02
Map
03
Select
04
Compile
05
Prove
06
Unlock
pick and choose. existing primitives, hybrids, ONE inventions. capabilities unlock after proof.
Devices, agents, rails, residency, and the threat model you actually run, not a generic profile.
The estate
Sensors to GPU. Agents to humans. Every class named.
02 · map · then select
Classical, post-quantum, constrained, ONE inventions, hybrids. Clients pick and choose. Nothing is invented at the edge.
See the factoryClassical
Post-quantum
Constrained
ONE
Hybrids
The factory signs a spec unique to this estate. A version, not a template. Diffable. Revocable.
Your representation
spec vN · hybrid ML-KEM ∥ X25519 · ONE handshake
04 · compile · then prove
Machine-checked composition. Known-answer tests. Quantitative complexity shipped with the version.
No proof, no ship
Known-answer · composition · bound 2^λ
05 · prove · then unlock
Screenshot control, tiny-cloud meshes, shadow VPNs, AI-to-AI clauses. They open inside your sandbox, under your policy, not before.
Every estate is unique. The sandbox compiles a security representation that matches how you actually run, not a generic profile.
Screenshot control, tiny-cloud meshes, shadow VPNs, AI-to-AI clauses. They unlock inside your sandbox, under your policy.
Known-answer tests. Signed versions. No proof, no ship. You see the construction before it ever touches live traffic.
We did not replace cryptography. We extended it. Classical, post-quantum, constrained, and ONE inventions compose. Hybrids are first-class.
The architecture is a construction kit. Same proved library, a signed spec per device class. Clients pick and choose. Nothing is invented at the edge.
A private environment with your threat model, your devices, your policies. Capabilities unlock when the handshake is yours, not before.
A private sandbox. Your primitives. Your threat model. Proof before production.