@happyvertical/smrt-vault-relay
A blind snapshot relay: a deployable service that stores encrypted snapshots per account, signed by devices and gated by the backup.vault feature.
What it gives you
A blind snapshot relay: a deployable service that stores encrypted snapshots per account, signed by devices and gated by the backup.vault feature.
- 01The relay stores opaque ciphertext and holds no key material
- 02Each device route needs an Ed25519 device signature and the backup.vault entitlement
- 03A primary-writer lease with a fencing token controls who publishes
- 04A lapsed entitlement stops writes at once and keeps restores open for a retention window
Blind by construction
The relay never parses, decrypts, or validates blob content. It logs an account handle, never a body, a signature, a nonce, or an account id. It still observes framing, sizes, sequences, identifiers, and traffic activity.
Chunked upload and commit
A device begins an upload with the fencing token, uploads fixed-size chunks, and commits. The relay checks every chunk and the SHA-256 digest of the whole ciphertext. A commit makes the snapshot the newest one in one atomic step.
Lapsed subscriptions
When the entitlement lapses, begin, chunk upload, commit, and device delete answer 402. List, latest, download, abort, and lease routes stay open. After the retention days, reads answer 410 and writes keep answering 402. Only an operator sweep deletes lapsed data.
Schema and deployment
The deployment applies migrateVaultRelayV1 and migrateVaultRelayLeasesV1. The relay deploys as a container. The operator sets the quotas, the retained snapshot count and age window, the bucket, the databases, and the domain. The relay has no default for these. The lapse retention days (90), the sequence jump limit (1000), and the lease lifetime (300 seconds) have defaults.
Package UI
No UI layer to carry
This package stays focused on models, runtime behavior, or tooling. Build its interface with smrt-ui, or use a related domain package that exposes a /svelte entry point.
Intentionally headless
Package previews
No playground module yet
This package does not currently export a ./playground module. Its component names and import path remain available in the Components tab.
Intentionally not registered
Generated interface
REST
The exact route set comes from each model's @smrt({ api }) policy
and the application manifest—not from a second controller definition.
The package registers no models. It has no generated REST, CLI, or MCP surface, and its device routes live under /v1.
Generated interface
MCP
AI tools are generated from the methods you explicitly include. Their inputs are validated against the same model metadata used by REST and CLI.
The package registers no models. It has no generated REST, CLI, or MCP surface, and its device routes live under /v1.
Browser-native agent interface
WebMCP
The generated web definitions carry the same tool names, descriptions, and JSON Schema
inputs as MCP. smrt-web registers them with document.modelContext.
The package registers no models. It has no generated REST, CLI, or MCP surface, and its device routes live under /v1.
Generated interface
CLI
The app CLI turns manifest resources into predictable operator commands while keeping package-specific actions close to their models.
The package registers no models. It has no generated REST, CLI, or MCP surface, and its device routes live under /v1.