# IceFireDB/IceFireDB

@IceFireLabs -> IceFireDB is a database built for web3.0 It strives to fill the gap between web2 and web3.0 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.

Repository: https://github.com/IceFireDB/IceFireDB
Canonical: https://ross.abutalabs.com/products/icefiredb
Homepage: https://www.icefiredb.xyz
Language: Go
License: MIT
License Family: permissive
Topics: redis, storage, golang, key-value, distributed-systems, raft, kvstore, distributed-database, nosql, database, high-performance, blockchain, ipfs, web3, cloudnative, oss, p2p, sql, sqlite, crdt
Last push: 2026-08-24T12:45:58+00:00

## Health v2 (maintenance only)
Score: 67/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 8, longevity 100
- inputs: {"age_days": 2007, "days_push": 9, "days_rel": 479, "gap_med": null, "n_releases_24m": 1}
- flags: prerelease_only
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1154, forks 93 (observed 2026-08-28T04:03:47.764247+00:00)

## What it is
IceFireDB is a decentralized, high-performance distributed database written in Go that bridges Web2 and Web3 ecosystems. It offers Redis-compatible NoSQL and MySQL-protocol SQL interfaces, with Raft consensus for local consistency and P2P CRDT synchronization across sites, plus storage drivers for disk, OSS, and IPFS.

## Use cases
- run a redis-compatible distributed database with raft consistency
- sync database data across sites via p2p crdt
- store web3 application data on ipfs-backed storage
- give web2 apps a friendly database path to decentralization
- self-host a nosql database with oss and disk storage drivers
- use pubsub messaging in a decentralized database cluster

## When to choose
- you need redis or mysql protocol compatibility with decentralized storage backends
- you want cross-site data replication without centralized coordination
- you are building web3/dapps that need familiar database interfaces

## When to avoid
- you need a battle-tested production database with mature ecosystem support
- you require strict ACID transactions across distributed nodes
- you only need a simple single-node redis or sqlite instance

## Facets
- artifact type: service
- maturity: active
- function: database, search-engine, message-queue, caching, p2p
- domain: databases, microservices, blockchain, web-development, self-hosted
- platform: go, self-hosted, cross-platform
- tags: redis-compatible, raft, crdt, ipfs, kvstore, nosql, web3, mysql-protocol, decentralized-storage, linux, macos, docker

## Member repositories
- IceFireDB/IceFireDB (main) score 67

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:47.764247+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-30T06:32:15.403788+00:00, confidence not recorded.
  - readme: https://github.com/IceFireDB/IceFireDB (fetched 2026-08-28T04:03:47.764247+00:00, sha 3e680c8f38f2)
  - homepage: https://www.icefiredb.xyz (fetched 2026-08-29T12:37:35.424653+00:00, sha a44dcd26e6f8)
- Data as of 2026-08-30T08:39:29.467469+00:00.