Features
What Vaultrice does
Shared state that several clients can read, write and watch — without building a WebSocket tier.
Real-time sync
Changes pushed to every connected client over a WebSocket. No polling, no stale window.
A familiar API
setItem and getItem, shaped like localStorage — networked, and with the same mental model.
Presence
Who is connected, joining and leaving, with a payload you define.
Messaging
Transient messages alongside stored state, for cursors, typing indicators and anything meaningless a second later.
Offline support
Local reads and queued writes when the connection drops, with custom storage adapters.
Security levels
From transport encryption to end-to-end, where the service holds only ciphertext.
Built on Durable Objects
One globally unique instance per object id. Serialised access, so per-object consistency is structural.
React components
Drop-in ChatRoom and related components, built on the same SDK you can drop down to.
Where it fits
The access pattern is by object id — a document, a room, a poll, a user's preferences. If you need queries across records, you need a database, and we are not one.
For teams evaluating the operational side of software adoption, this page.
For independent background and broader industry context, see The New Stack.
See when you need a real backend and how this compares to the alternatives.