About
BetterSign gives people, servers, services and subsystems stable cryptographic identities whose keys and protected metadata can change safely over time.
About › Overview
The protocol. This page describes the BetterSign protocol and its open-source core. For what the BetterSign app and products do today, see Products.
BetterSign is a decentralized PKI and secure change-monitoring system. It treats an identity as a stable VLAD with an append-only provenance log behind it, rather than as one static key file.
Keys, SSH access, TLS material, WireGuard metadata, admin policy, certificates and protected application data are state inside that log. Peers verify the log before trusting the current state.
Key rotation is usually avoided because the operational blast radius is high. SSH keys, API tokens, deploy keys and service credentials are copied into many systems, then become fragile to replace.
BetterSign separates identity from the current secret. Rotation becomes a signed log update that following systems can verify and apply automatically.
A peer can start with a VLAD, fetch the matching provenance log, replay and verify it, and derive the current keys and protected data without asking a central authority to vouch for the result.
The network distributes records. Trust comes from the VLAD, hash-linked log entries, authorization scripts, and signatures or proofs inside each accepted update.
The whole system is one loop: a stable name, a signed history behind it, and anyone able to replay that history to reach the current truth. There is no authority in the middle.
Three short looping demos make it concrete: how a key rotates and every follower converges, how anyone verifies a log by replaying it, and how BetterSign gives AI agents a verifiable identity. Watch key rotation, watch verification, and watch agent identity.
| Identity | Stable VLADs survive key rotation |
| State | Append-only provenance logs |
| Transport | VLADemlia DHT |