Skip to content

Getting started

Safeparts splits one secret into recovery shares so recovery requires cooperation, not one perfect backup.

Safeparts turns one secret into n shares. Recovery requires any k shares.

  • Fewer than k shares: an attacker learns nothing useful.
  • Any k shares: you can reconstruct the original secret.

Practical limits: 1 <= k <= n <= 255.

The hard part is logistics: who holds which share, how you contact them, and what you do when someone is unavailable.

Start with Use cases to choose k/n and a distribution you can actually run.

Web UI

Good for one-off workflows and visual confirmation.

Web UI guide

CLI

Good for automation and repeatable runbooks.

CLI guide

TUI

Good for offline machines and interactive terminal workflows.

TUI guide

Open the web app

Do this once with a fake secret so you learn the flow before you trust it with a real key.

  1. Pick k=2, n=3.
  2. Split a synthetic secret such as example-secret.
  3. Store the 3 shares in 3 different places (even temporarily).
  4. Recover using any 2 shares.
  5. Delete the synthetic shares.

Read Security and follow the storage rules there. Safeparts can remove single points of failure, but it can’t fix a bad distribution.

Use cases

Pick k/n and a realistic share distribution.

Use cases

Encodings

Choose between machine-friendly and human-friendly share formats.

Encodings

Security

Threat model and safe handling rules.

Security