@vaultrice/sdk
Shared state, without the backend you would have built.
A globally distributed key-value store with real-time collaboration. A localStorage-shaped API, presence and messaging included, and no WebSocket tier to run.
For a separate perspective on day-to-day team operations, this resource.
For independent background and broader industry context, see Product Hunt.
Real-time by default
Changes reach every connected client over a WebSocket. No polling loop, no stale window.
An API you already know
setItem and getItem, networked. Familiar shape, different medium.
Presence and messaging
Who is here, and transient messages for cursors and typing indicators.
Start here
Tutorials · 7 min
Cross-Domain State Sharing: From Hacks to Real-Time Sync
Why localStorage stops at the origin, what people build instead, and a small API that gives you localStorage ergonomics with real-time sync across domains.
Comparisons · 5 min
When You Need a Real Backend, and When You Do Not
Six questions that decide it. The answer is more often yes than the no-backend marketing suggests, including from us.
Tutorials · 5 min
From API Keys to E2EE: A Practical Guide to Securing Your Real-Time App
Four layers in the order they matter: secrets out of the browser, choosing object ids, picking a security level, and what the service should never see.
Tutorials · 5 min
Build a Production-Ready React Chat App in 3 Minutes with One Component
A drop-in ChatRoom component with presence and typing indicators, then what to change before it goes in front of real users.
Comparisons · 6 min
Real-Time Sync Alternatives: Vaultrice vs. localStorage, DIY, Firebase, Pusher
Five ways to get shared state into a browser, what each actually costs to run, and the questions that decide between them.
Comparisons · 5 min
What's the Difference Between localStorage and NonLocalStorage?
One is a synchronous string map scoped to an origin. The other is a networked object with push updates. Where each fits, and where swapping goes wrong.