Features¶
What you can do with Gako, and where each capability is documented today. Every feature is built so the server stays unable to read your secrets — see the zero-knowledge model for the guarantee they all rest on.
This guide is still filling in
Dedicated, walkthrough-style feature pages are coming as the workflows settle. For now this page maps each capability to the section that already covers it.
| Capability | What it is | Where it's documented |
|---|---|---|
| Secrets | Store and retrieve passwords, API keys, certificates, and notes, encrypted end to end. | CLI client → Commands (the list / get / create / edit group); a web-client walkthrough is planned. |
| Sharing and access | Grant other identities access to a secret without the server ever seeing its content. | CLI client → Commands (share, grants); team-wide sharing in Administration → Organizations. |
| Machine authentication | Non-human identities for automation and CI — read-only and tightly scoped. | Administration → Machine identities. |
| Recovery | Recover access after a lost master password, without handing keys to the server. | Administration → Recovery basics. |
See Concepts for the model these features are built on, and Security for what they do and do not protect against.