Decentralized Database Tools
Distributed, multi-writer databases without one operator holding the only copy.
Decentralized.Host offers no database product. Its own control-plane state is replicated with Raft across 3 or 5 members (with an optional Postgres mirror that is never the source of truth) -- replicated, not decentralized in this topic's sense.
What makes a database "decentralized"
Most distributed databases (CockroachDB, YugabyteDB, Cassandra) are decentralized in an operational sense -- data is sharded and replicated across multiple nodes so no single machine holds the only copy -- but still trust-centralized: one organization runs and owns all the nodes. A smaller set of blockchain-adjacent databases (OrbitDB over IPFS, or ledger-style databases like those behind some DeFi protocols) go further, distributing both the data AND control across mutually untrusting parties, using consensus rather than a trusted operator to agree on writes.
Why this distinction matters in practice
Operational distribution (multiple nodes, no single point of failure) solves availability and scale; it doesn't require giving up control of who can write. Trust distribution (no single party controls the data) solves a different problem -- collusion-resistance and censorship-resistance -- at a real cost in write latency and complexity (consensus rounds are slower than a single node committing a transaction). Raft-replicated systems (etcd, Consul, the Decentralized.Host control plane) sit in between: operationally distributed across 3 or 5 members, but run by one operator, so they tolerate crashes, not a malicious majority.
Distributed, multi-writer databases without one operator holding the only copy. Decentralized.Host offers no database product. Its own control-plane state is replicated with Raft across 3 or 5 members (with an optional Postgres mirror that is never the source of truth) -- replicated, not decentralized in this topic's sense.