Arqen Trust Protocol
The Trust Protocol is the covenant between your edge nodes and the Control Plane: nothing moves without a signature, nothing executes without verification, nothing is deleted from the audit.
Back to Arqen PlatformA continuous trust loop
The protocol is not a checklist. It is a living cycle that signs, distributes, verifies, audits and governs every exchange — on every action, every sync, every node.
Core
- 01
Signature
Every manifest, license and migration is Ed25519-signed by the Control Plane. The private key lives only in the cloud; edges know nothing but the public one.
- 02
Distribution
Signed packages travel over TLS on the edge periodic pull cycle. Versions are monotonic: a stale or tampered manifest is rejected at the root.
- 03
Verification
The edge verifies the signature before executing any payload. Invalid signature, expired license or unauthorized action: fail-closed, no exceptions.
- 04
Audit
Every action enters an append-only SHA-256 hash chain, verified on schedule. Altering one row invalidates the whole chain: tampering is visible, not hideable.
- 05
Resilience
Automatic pre-migration snapshots, transactional outbox and contractual grace period: the system is designed to degrade safely, never to fail silently.
- 06
Governance
Persistent admin sessions, RBAC roles and an append-only log of administrative actions: who did what is always traced, on both sides of the channel.