What is Keybase Teams?
Who uses Keybase Teams?
Why developers like Keybase Teams?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Keybase Teams in their tech stack.
Even decided to use Keybase Teams because we needed a BYOK solution to securely sharing critical data, which could be expired, and was TOFU-safe.
- BYOK ensured that we could rotate keys, and be in control of those keys rather than delegating them to a service to hold the masters.
- Expiry was important, because we needed messages with certain risky information to disappear, to ensure against hacking (even despite our procedures).
- TOFU means 'trust on first use' and is reflected int he way that information is inaccessible to a use if they needed to do anything that interrupts the ability to trust their account — such a password reset.
These together allowed us to use this tool within our data security chain.
We've used Keybase Teams since day 1 because it's end-to-end encrypted, fast, and does everything we need - secure team chat, KeePass management, encrypted Git, and a LinkedIn of sorts for the cryptocurrency community.