Hosted vaults

Hosted vaults are the full-experience path where KB-1 operates the vault engine for you. People still enter through KB-1 Cloud, and the durable vault home is a KB-1 operated hosted environment.

What Hosted provides

Cloud login, org membership, signed entry, and presence.
A KB-1 operated daemon runtime for the org.
Managed lifecycle: start, idle park, and wake.
Hosted durability and restore mechanics for the daemon runtime.
A bounded hosted hot cache for repeat reads and hot documents while the hosted daemon wakes.

What stays the same

Hosted uses the same product model as self-hosted Cloud login:

the app routes by organization and vault slug,
the daemon resolves the vault slug behind the data plane,
content operations go through the KB-1 vault service contract.

Wake behavior

Hosted runtimes can park when idle and wake when a user opens or edits a vault. A short wake overlay is expected after idle. Persistent wake failures should be troubleshot as a hosted lifecycle issue, not as data loss.

Recent hosted paths can answer some repeated vault list, tree, plain-file, and hot-document reads from the org’s Cloud coordination layer while the daemon is parked. The daemon is still the source of truth. Cache misses, search, cold documents, and uncertainty fall back to waking or waiting for the daemon.