What KB-1 Cloud stores
KB-1 Cloud stores different things depending on which operating mode you choose. The main rule is simple: Cloud login data is not the same thing as hosted vault data.
Local-only daemon
Section titled “Local-only daemon”In local-only mode, KB-1 Cloud is not required.
Your machine owns:
- Vault files.
- Local API and editor state.
- Local agent access.
- Backups and runtime lifecycle.
Self-hosted full experience
Section titled “Self-hosted full experience”In the self-hosted full experience, KB-1 Cloud stores and processes the data needed for login and routing.
KB-1 Cloud owns:
- Account and organization records.
- Identity and signed entry.
- Access control records.
- Relay routing state.
- Presence and collaboration coordination needed by the shared experience.
Your machine remains the vault home for durable vault content.
Hosted full experience
Section titled “Hosted full experience”In the Hosted full experience, KB-1 Cloud provides the same login and org surface, and KB-1 also operates the vault engine.
KB-1 Cloud owns:
- Account and organization records.
- Identity and signed entry.
- Hosted vault lifecycle.
- Hosted durability and runtime.
- Vault content stored in the hosted vault environment.
- Bounded hosted hot-cache state for repeated reads and hot documents.
The hosted hot cache is not a separate search or indexing product surface. It is an optimization for KB-1 operated Hosted vaults, scoped to the hosted org. Daemon-produced cached state is reconstructible from the daemon; pending hot-document edits may be stored there temporarily until replay or ack.
What to ask before choosing
Section titled “What to ask before choosing”- Do I need a Cloud account for this workflow?
- Where should durable vault content live?
- Who operates the vault runtime?
- Who is responsible for backups and recovery?
- Do people and agents need shared organization access?
Those answers determine whether local-only, self-hosted, or Hosted is the right path.