sgit newsroom v0.1.29 · snapshot 2026-09-24

Reading room · sgit.ai · llms-full

Reading room / sgit.ai / llms-full.txt · section 141 of 358

Who holds the keys? A call for collaboration on vault key management, sgit.ai

An open call to password managers, identity providers and platform credential managers. sgit vaults are encrypted on the client and opened in a browser with one key, and keys now multiply faster than people can manage them by hand. We would rather use a key manager than build one. The page explains sgit for someone new to it, states what we are looking for (something that exists, a joint pilot, or an open specification), the requirements (browser first, key kinds kept apart, release only on approval, end-to-end sharing, names in plain words that are addresses and never keys, revocation, keys for agents), a sketch of the share flow, why the old word-based token was removed, and what we would bring.

Page: https://sgit.ai/partnerships/vault-key-management.html↗

Home↗ / Partnerships↗ / Vault key management

A call for collaboration · public material only · 24 September 2026