# FrigadeHQ/remote-storage

remoteStorage is a simple library that combines the localStorage API with a remote server to persist data across sessions, devices, and browsers. It works as a simple key value database store and backend with support for React, Next.js, Vue, Node, or any Javascript stack

Repository: https://github.com/FrigadeHQ/remote-storage
Canonical: https://ross.abutalabs.com/products/remote-storage
Homepage: https://remote.storage
Language: TypeScript
License: MIT
License Family: permissive
Topics: caching, database, javascript, keyvalue, keyvalue-db, localstorage, web, backend, local-storage, nextjs, remote-storage, preferences-datastore, settings-storage
Last push: 2024-03-27T00:36:02+00:00

## Health v2 (maintenance only)
Score: 17/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 70
- inputs: {"age_days": 984, "days_push": 890, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1398, forks 45 (observed 2026-08-28T04:04:36.828328+00:00)

## What it is
remoteStorage is a lightweight (~1 kB) TypeScript library that mirrors the localStorage API but persists key-value data on a remote server, so state survives across browsers, devices, and sessions. It includes built-in JWT-based auth, works with any JavaScript stack (React, Next.js, Vue, Node), and ships with an open-source server plus a free hosted community server.

## Use cases
- persist user preferences across devices and browsers
- show a welcome modal only once per user regardless of device
- sync feature flags and user flags between browser sessions
- replace localStorage with a remote-backed key-value store
- store app settings server-side without building a backend
- share lightweight state between web and Node clients

## When to choose
- you want a localStorage-like API but data must follow users across devices or browsers
- you need a tiny dependency for simple key-value persistence without a full database
- you want self-hostable storage with JWT auth and an MIT license
- you're tracking one-time UI states like seen-modals or dismissed banners per user

## When to avoid
- you need relational queries, indexing, or large datasets rather than simple key-value pairs
- you require strong consistency or offline-first conflict resolution
- you're storing sensitive data that shouldn't live on a third-party or simple remote server
- you need high-throughput server-side storage rather than lightweight client preferences

## Facets
- artifact type: library
- maturity: active
- function: caching, database, http-client
- domain: web-development, frontend, backend, developer-tools
- platform: browser
- tags: localstorage, key-value-store, cross-device-sync, typescript, react, nextjs, vue, jwt, user-preferences, nodejs, web-server, javascript

## Member repositories
- FrigadeHQ/remote-storage (main) score 17

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:36.828328+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:39:12.076936+00:00, confidence not recorded.
  - readme: https://github.com/FrigadeHQ/remote-storage (fetched 2026-08-28T04:04:36.828328+00:00, sha 6c164339da5c)
  - homepage: https://remote.storage (fetched 2026-08-29T11:53:43.272944+00:00, sha 11de55495898)
  - registry_npm: https://registry.npmjs.org/remote-storage (fetched 2026-08-29T11:53:43.281984+00:00, sha 88390c1643e6)
- Data as of 2026-08-30T08:39:29.467469+00:00.