Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Sync and Cloud

AxiomVault is designed to encrypt data before it touches cloud storage.

Current remote support

  • Google Drive with OAuth2 and resumable uploads
  • Local filesystem storage for offline or self-hosted workflows

Planned remote support

These are roadmap items, not current capabilities:

  • iCloud
  • Dropbox
  • OneDrive

Sync behavior

The sync engine supports:

  • On-demand sync runs
  • Periodic background sync
  • ETag-based conflict detection
  • Conflict resolution strategies such as keep-both, prefer local, prefer remote, and manual handling
  • Retry with exponential backoff

Simplified sync flow

flowchart LR
    L[Local plaintext changes] --> E[Encrypt locally]
    E --> V[Update local vault state]
    V --> S[Sync engine]
    S --> R[Remote encrypted objects]
    R --> S
    S --> C{Conflict detected?}
    C -- no --> D[Sync complete]
    C -- yes --> H[Apply selected resolution strategy]
    H --> D

Typical flow

axiom remote gdrive auth --output ~/gdrive-tokens.json
axiom sync run --vault-path ~/my-vault --strategy keep-both
axiom sync status --vault-path ~/my-vault

Caveats

  • Sync correctness matters as much as encryption correctness for real users.
  • Remote providers may differ in metadata, retry, and error behavior.
  • Treat backend support as evolving until compatibility guarantees are documented.