Web UI
Good for one-off workflows and visual confirmation.
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.
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.
CLI
Good for automation and repeatable runbooks.
TUI
Good for offline machines and interactive terminal workflows.
Open the web app
Do this once with a fake secret so you learn the flow before you trust it with a real key.
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.
Encodings
Choose between machine-friendly and human-friendly share formats.
Security
Threat model and safe handling rules.
Troubleshooting
Common failure modes and fixes.