gruns/ImmortalDB

Health v2 · maintenance only

Adoption not part of the score

3058 stars · 60 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

ImmortalDB is a resilient key-value store for the browser that redundantly persists data across Cookies, IndexedDB, and LocalStorage. It uses a consensus mechanism to detect and self-heal deleted or corrupted data via a simple Promise-based API.

Use cases

• persist key-value data in the browser that survives cache clearing
• store user preferences reliably across cookies, IndexedDB, and localStorage
• protect browser storage from eviction under storage pressure
• replace evercookie-style persistent storage with a modern Promise API
• self-heal corrupted or deleted browser storage data

When to choose

• you need highly persistent client-side key-value storage in the browser
• you want redundancy across multiple browser storage backends with automatic healing
• you want a simple Promise-based API using only standard HTML5 storage APIs

When to avoid

• you need server-side or structured/relational storage
• you need to store non-string data types or large binary blobs
• you want storage that users can fully and easily purge, since redundancy makes deletion harder

Facets

library · maturity active

database caching web-development frontend databases privacy browser key-value-store localstorage indexeddb cookies self-healing redundant-storage promise-api javascript

Member repositories

For agents

markdown · JSON · MCP: product_card(name="gruns/ImmortalDB")