One substrate, the entire data-systems landscape
Every row is a category the industry built a separate engine for, paired with its signature public benchmark. One 64-byte-container substrate does them all in one pass. Live now or loading, every number measured on data you can download.
★ collapse
fused query
graph + vector + search in ONE pass, one copy
vs the entire stack
run ▸
★ compute
SAOPS
SNN synaptic-activation throughput at max concurrency
vs GPU inference
run ▸
★ their benchmark
Bitcoin value-flow
the live 684M-edge Bitcoin graph, deep k-hop
vs graph databases
run ▸
★ their benchmark
Bitcoin address vectors
behavioural address vectors, exact recall off disk
vs vector databases
run ▸
★ their benchmark
Bitcoin tx / address
pattern-scan the raw chain, index-free
vs search engines
run ▸
graph
Bitcoin value-flow
6-hop deep fund-trace + provenance
vs graph databases
run ▸
graph
Bitcoin value-flow
684M-edge live chain, k-hop
vs graph databases
run ▸
graph
Bitcoin value-flow
address clustering, k-hop
vs graph databases
run ▸
search
Bitcoin tx / address
index-free pattern scan, zero index
vs search engines
run ▸
vector
Bitcoin address vectors
binary Hamming recall, 32× density
vs vector databases
run ▸
key-value
Bitcoin address keyspace
seqlock RAM-ring GET, no separate cache
vs in-memory KV stores
run ▸
SQL
Bitcoin value-flow
aggregate the value-flow, no ETL
vs SQL databases
run ▸
OLAP
Bitcoin value-flow
full-chain SIMD aggregation
vs columnar warehouses
run ▸
graph
Bitcoin value-flow
weakly-connected components over the chain
vs graph databases
run ▸
document
Bitcoin tx / address
nested tx-record field query, no schema
vs document stores
run ▸
wide-column
Bitcoin address keyspace
the cloud-serving read/write workload
vs wide-column stores
run ▸
RDF
Bitcoin value-flow triples
tx→pays→address triples, SPARQL-style traversal
vs triple stores
run ▸
time-series
Binance live ticks
as-of join + VWAP + windowed OHLC
vs tick databases
run ▸
object
Bitcoin tx objects
content-addressed tx-bytes PUT/GET
vs object stores
run ▸
proximity
Bitcoin address clusters
range + nearest over value-flow neighbourhoods
vs geo databases
run ▸
embedded
Bitcoin address keyspace
the LSM read/write workload
vs embedded LSM stores
run ▸
streaming
Binance trade stream
native append-only event log
vs log / stream brokers
run ▸
run ▸ live now, click to run the real benchmark ·
dataset ingesting the corpus is still loading into the substrate, not clickable yet ·
a demo showing measuring… in a tier means that tier's telemetry is still warming or its NIF has not reported yet, not a failure.