StillPointRemote Vaults and Homebase Vaults.
StillPoint works offline by default, but grows with you when you want sync, shared access, or a zero-trust storage model. Remote Vaults and Homebase Vaults are two paths to that future.
Pick the vault model that matches your workflow.
Remote Vaults
A live server-backed vault with user management. Great for teams, shared spaces, and centralized administration. Think of it like a collaborative vault hosted on infrastructure you control.
Homebase Vaults
A personal-first sync model with encrypted blobs on the server and keys kept local. Built for multi-device continuity without giving up privacy.
Both feel local
StillPoint keeps the same interface, the same flow, and the same speed. The mode changes the sync and security model, not the way you think.
When to use Remote Vaults
Remote Vaults are best when multiple people need to work in the same vault, or when your organization wants central control over access and storage.
Team collaboration
Shared notes, shared structure, and a single source of truth.
Admin control
Admins manage users, roles, and write permissions.
Infrastructure-owned
Host it on your own servers or keep it local to your network.
When to use Homebase Vaults
Homebase is built for personal continuity across devices. It gives you sync and backups without handing your plaintext to a server.
Think of Homebase like a Git model for notes: each device keeps a full local copy, works independently, then pushes and pulls changes through the Homebase server with eventual consistency.
Private by design
Encrypted blobs live on the server; your passphrase stays local.
Multi-device flow
Use StillPoint on your laptop, desktop, or travel machine.
Offline first
Work anywhere, sync later, keep full local performance.
Different threat models, both intentional.
Remote Vaults
Access is controlled with user roles and permissions. The server stores the vault content directly and enforces authentication on every request. Best for shared environments where the server is trusted and access is managed.
Homebase Vaults
The server stores encrypted blobs and metadata. The encryption passphrase stays on your device, so the server cannot read plaintext. Tokens authenticate access, but do not reveal your content.
Practical takeaway
Remote Vaults optimize for collaboration and administration. Homebase optimizes for privacy and personal control. Choose the model that matches the trust boundary you need.
Remote Vaults vs Homebase Vaults
| Feature | Remote Vaults | Homebase Vaults |
|---|---|---|
| Best for | Teams, shared workspaces, central admin | Personal or small-team sync across devices |
| Permissions | Admins, read, read+write per user | Admin roles, local-first control |
| Security model | Server-enforced auth and access control | Client-side encryption, server stores encrypted blobs |
| Offline use | Designed for connected use | Fully offline, syncs when available |
| Sync model | Live server-first pull/push | Git-like local-first push/pull with eventual consistency |
| Setup | Connect to a remote server and vault | Pair devices with Homebase and a passphrase |
| Why choose it | Collaboration, governance, shared structure | Privacy-first sync with zero-trust storage |
If you're unsure, start local.
You can begin with a local vault and move to Remote or Homebase later. StillPoint keeps your notes in plain files, so the path forward is always open.