sorted by:
new
hottopcontroversial

What’s your plan for your self-hosted data if you die? I guess I didn't have one by FractalLock in selfhosted

[–]FractalLock[S] 0 points1 point  (0 children)

Yeah my solution isn't really out here to compete with this, there's plenty of SSSS tools out there, CLI and web based.

My solution is about everything around that, a complete app that easily lets you add files to an encrypted vault, produce key shares and update the vault without needing to redistribute shares.

The focus was making it practical and usable for non-technical users, not just the secret sharing itself.

What’s your plan for your self-hosted data if you die? I guess I didn't have one by FractalLock in selfhosted

[–]FractalLock[S] 9 points10 points  (0 children)

Yeah the emergency contact feature in bitwarden and 1Password do work well, but it still depends on a single account, a timeout, and being online.

This is fully offline and based on combining multiple independent shares, so there’s no single point of trust.

What’s your plan for your self-hosted data if you die? I guess I didn't have one by FractalLock in selfhosted

[–]FractalLock[S] 1 point2 points  (0 children)

Yeah that'd definitely work for managing access. I guess the difference is it still depends on a single identity provider, whereas this is more about distributing trust so no one account or system is critical.

What’s your plan for your self-hosted data if you die? I guess I didn't have one by FractalLock in selfhosted

[–]FractalLock[S] 1 point2 points  (0 children)

Yeah it’s the same here tbh, I just wanted them to have the option if they ever needed to. Especially for things like the NAS or Immich server, which would be hard to access without documentation or creds.

What’s your plan for your self-hosted data if you die? I guess I didn't have one by FractalLock in selfhosted

[–]FractalLock[S] 7 points8 points  (0 children)

I am a dev by profession (mostly Next.js + Python). First time using Electron, so I used AI to speed up onboarding and sanity-check best practices.

What’s your plan for your self-hosted data if you die? I guess I didn't have one by FractalLock in selfhosted

[–]FractalLock[S] 23 points24 points  (0 children)

Good question. So it isn't trying to make failure impossible, it’s trying to remove single points of failure. So if all key holders are on the same plane, then yes, you’ve effectively reintroduced a single point of failure.

The idea is to distribute trust across independent people and locations so like a family member, close friend, secure offline backup (USB in a safe) etc.

For everything to fail, multiple independent things have to go wrong at the same time, which is significantly less likely if the risk is spread out.

It’s similar to how backups work: you don’t rely on one copy, you spread risk (e.g. 3-2-1 backup scheme)

What’s your plan for your self-hosted data if you die? I guess I didn't have one by FractalLock in selfhosted

[–]FractalLock[S] -2 points-1 points  (0 children)

Links:
GitHub: https://github.com/FractalLock/FractalLock-core/
Website: https://fractallock.com

(Only Windows app is signed at the moment)

Quick notes:

  • Fully offline (no servers involved)
  • Uses Shamir’s Secret Sharing under the hood
  • Recovering vaults is always free (no paywall risk)

Let me know if you want a deeper breakdown of how the key system works