Data that can prove itself.

Hyphae is a local-first data engine written in Rust. One process owns one data directory and exposes relational SQL, native structures, lexical search, and vector search over a shared transaction, WAL, MVCC, recovery, and proof substrate. The engine runs offline and does not embed PostgreSQL, Valkey, OpenSearch, a cloud service, an embedding provider, or an LLM.

Stable Native release: v1.1.0 is the active architecture. G0 through G8 are closed for their versioned, bounded profiles. G7 uses an environment-bound operational-scale authority; G8 binds the release archives, SBOMs, signatures, provenance, and fault matrices to the exact release commit. The native gate status is the current status authority; temporary workflow artifacts alone do not close a gate.

Published release: all 24 Rust crates are available at 1.1.0 on crates.io, all 23 library crates built successfully on docs.rs, and the GitHub Release contains signed native archives for four platform targets. The exact checksums, source identities, workflow runs, and consumer verification are in the 1.1.0 publication receipt.

G8 release evidence binds publication to the exact release commit. The G7 closure certifies the C-60 operational-scale control matrix but makes no canonical dedicated-hardware latency, interference, or bare-metal claim.

What Hyphae does

• Executes bounded SQL DDL, DML, prepared queries, secondary-index reads, and transactions over a Hyphae-owned relational engine.
• Provides native strings, counters, hashes, lists, sets, sorted sets, streams, TTL, scans, algebra, and atomic structure batches.
• Owns lexical, exact-vector, incremental ANN, filtered, faceted, metric, and same-snapshot hybrid search without an external search engine.
• Commits SQL, structure, and search mutations under one catalog, WAL, MVCC root set, commit sequence, scheduler, and stable object-ID namespace.
• Exposes one embedded Rust facade, local UDS/named-pipe protocol, CLI, optional loopback HTTP /v2, and typed Python and TypeScript SDKs.
• Creates Native checkpoints, proofs, witnesses, backups, restores, vacuum generations, and complete doctor reports with bounded failure behavior.
• Imports format-2 state offline into a separate pending Native directory, verifies equivalence, and requires explicit promotion.

See the Native capability matrix, including surface differences, boundaries, and deliberate non-capabilities. The published 0.2.1 matrix remains separate.

Operational-scale measurements

The G7 authority exercised all 11 surfaces at C1, C8, and C32 on a DigitalOcean c-60-intel VM with 60 vCPUs and 120 GiB RAM. Each cell used 1,000,000 measured observations plus 100,000 warmup observations per surface against 1,000,000 documents and 1,000,000 384-dimensional vectors. Queueing time is included. Values below are observed p50 latency in microseconds.

Surface	C1 p50	C8 p50	C32 p50
Embedded structure point get	2.634 µs	352.043 µs	7,026.185 µs
Embedded prepared SQL primary key	3.710 µs	10.867 µs	7,224.293 µs
Local structure point get	123.323 µs	153.425 µs	303.213 µs
Local prepared SQL primary key	128.761 µs	126.416 µs	287.156 µs
Indexed SQL bounded read	45.443 µs	399.870 µs	8,340.482 µs
Two-index join bounded read	38.325 µs	325.779 µs	8,306.193 µs
BM25 top 10	1.595 µs	3.168 µs	64.335 µs
Filtered BM25 top 10	1.660 µs	3.250 µs	65.369 µs
ANN top 10	115.995 µs	139.118 µs	8,397.640 µs
Hybrid top 10	118.190 µs	141.885 µs	8,409.802 µs
Strict group commit	138,586.858 µs	141,622.215 µs	130,425.161 µs

The matrix completed 33/33 surface-concurrency cells: 33,000,000 measured observations and 3,300,000 warmups. ANN recall@10 was 1.0 in every cell. Strict group commit completed 3,000,000 logical commits with 3,000,000 distinct CSNs; recovery reported zero missing and zero mismatched commits.

These VM measurements establish functional concurrency, accounting, correctness, recall, and durable recovery at operational scale. They do not certify portable latency, dedicated hardware, bare metal, or background interference. The machine-readable measurements, method and limitations, and G7 closure authority retain the exact source, environment, contract, and artifact hashes. The machine-readable measurement file has SHA-256 95a78beb031de35a3d2532c7536d76491d6273f7b8ce74c6b3976038bc8c3234.

Install

Download the archive for your platform from the v1.1.0 GitHub release, then verify its checksum and Sigstore bundle before installing the hyphae binary. To install from crates.io, run:

cargo install hyphae-cli --version 1.1.0 --locked

Build and embed the exact release from source with:

git checkout v1.1.0
cargo build --release --locked -p hyphae-cli
./target/release/hyphae version --json

The release contains Linux x64, macOS x64/arm64, and Windows x64 archives plus checksums, SPDX/CycloneDX SBOMs, provenance, signatures, and attestations.

Legacy 0.2.1 compatibility flow

cargo build --release --locked -p hyphae-cli
export HYPHAE_DATA_DIR="$PWD/hyphae-data"

./target/release/hyphae version --json
./target/release/hyphae put \
  --key alpha --json '{"group":"x","score":10}'
./target/release/hyphae query \
  --field group --equals '"x"' --sort score \
  --proof-out result.hyproof
./target/release/hyphae backup --out ./hyphae-backup
./target/release/hyphae backup-verify --backup ./hyphae-backup
./target/release/hyphae doctor

These commands describe the published format-2 compatibility release, not the Native dev command surface. The query response names the snapshot and anchor needed by hyphae verify. The quickstart covers Windows syntax, compaction, restore, offline proof verification, the optional server, and clients.

Architecture

application
  ├─ embedded Rust facade ────────────────────────────────┐
  ├─ local CLI                                            │
  ├─ UDS / named-pipe clients (Rust / Python / TypeScript)│
  └─ optional loopback HTTP /v2 ──────────────────────────┤
                                                          ▼
                     Native product and transaction authority
                         │              │              │
                        SQL         structures       search
                         └──────────────┬──────────────┘
                                        ▼
                      catalog / WAL / MVCC / pages / blobs
                              checkpoints / backup / proofs

One operating-system lock gives one product instance exclusive ownership of a Native data directory. See the Native architecture and versioned Native specifications.

Public surfaces

Surface	Purpose
hyphae binary	Native local operations, administration, migration, server, and verifier
hyphae-native-product	Curated embedded Native product facade
Native local protocol	Primary UDS/named-pipe multi-client transport
HTTP /v2	Optional loopback-first Native edge
@celiums/hyphae	TypeScript Native local-protocol and HTTP client
hyphae-sdk	Python Native local-protocol and HTTP client
/v1 compatibility	Separately retained published format-2 HTTP product

OpenAPI 3.1 and JSON Schema 2020-12 under contracts/ are the canonical wire contracts. Native uses hyphae-v2.yaml and native-v2.schema.json; the published format-2 product retains hyphae-v1.yaml.

Rust crates

The Native line is organized around hyphae-native-product (embedded facade), hyphae-native-runtime (SQL, structures, search, transactions, and scheduling), hyphae-native-protocol/hyphae-native-daemon (local transport), and the owned hyphae-native-{types,catalog,pages,blobs,wal,mvcc,btree,records,manifest,ann} storage and execution primitives. hyphae-cli builds the single product binary.

Version 1.1.0 publishes the complete 24-crate graph:

• contracts and shared APIs: hyphae-core, hyphae-contracts, hyphae-query, and hyphae-retrieval;
• owned storage and indexing: hyphae-native-types, hyphae-native-ann, hyphae-native-catalog, hyphae-native-mvcc, hyphae-native-pages, hyphae-native-records, hyphae-native-wal, hyphae-native-blobs, hyphae-native-btree, and hyphae-native-manifest;
• runtime and public access: hyphae-native-runtime, hyphae-native-product, hyphae-native-protocol, hyphae-native-daemon, hyphae-engine, hyphae-storage, hyphae-client, and hyphae-server; and
• distribution and adapters: hyphae-cli and hyphae-pliegors.

The compatibility crates remain available as part of that graph:

Crate	Purpose	Documentation
hyphae-engine	Recommended embeddable facade	docs.rs
hyphae-storage	Durable log, recovery, snapshots, and backups	docs.rs
hyphae-query	Deterministic structured query	docs.rs
hyphae-retrieval	Deterministic exact, lexical, and hybrid retrieval	docs.rs
hyphae-contracts	Versioned /v1 models and embedded schemas	docs.rs
hyphae-client	Bounded async Rust HTTP client	docs.rs
hyphae-server	Loopback-first /v1 server	docs.rs
hyphae-core	Product and compatibility constants	docs.rs
hyphae-cli	Single hyphae binary, verifier, and MCP adapter	docs.rs
hyphae-pliegors	Optional PliegoRS public-contract adapter	docs.rs

Documentation

Start at the documentation index. Key guides:

• Native capabilities and limits
• Native 1.0 quickstart
• Published 0.2.1 compatibility guide
• CLI reference
• Configuration
• Native product contract
• Native HTTP API v2
• Native local protocol
• Operations and troubleshooting
• Security model
• Native local ecosystem target
• Microsecond-first target
• Release verification
• 1.1.0 publication receipt
• G7 operational-scale measurements
• 0.2.1 publication receipt
• crates.io release procedure

Product boundary

Hyphae Native is a local, single-node data ecosystem with Hyphae-owned SQL, structures, lexical search, and ANN under one durable authority. G0 through G8 are closed for their bounded contracts. G7 is an operational-scale C-60 authority with the explicit hardware and latency non-claims above; G8 protects the exact release commit.

Hyphae is not Mycelium, Hyphae Network, Celiums Network, an AI cognition runtime, a hosted SaaS, or a framework-specific data layer. The retained 0.2.1 compatibility line does not include the Native SQL/structures/search architecture. Replication, clustering, built-in TLS, at-rest encryption, multitenancy, billing, a control plane, an embedding model, and an LLM are also outside Native 1.0.

Hosted, distributed, and model-driven programs remain later phases. Applications still own process supervision, remote TLS termination, filesystem permissions, backup media policy, and optional embedding providers. Semantic providers can supply vectors to the Rust APIs but never become a core dependency or source of authority.

Repository map

• crates/: Native product/runtime/storage/protocol crates, retained format-2 libraries, public contracts, clients, servers, and the single CLI.
• contracts/: canonical OpenAPI and JSON Schemas.
• sdks/: TypeScript and Python clients/models.
• mcp/: MCP adapter guide; implementation is in the single binary.
• integrations/: optional PliegoRS, Astro, Next, and Vite adapters.
• examples/: maintained embedded, HTTP, and MCP examples.
• docs/: product, architecture, operations, security, normative formats, ADRs, and release gates.
• packaging/: deterministic multiplatform archives and release verification.
• compatibility/: immutable historical on-disk fixtures.

Development

The repository pins its toolchain and enforces format, Clippy, tests, rustdoc, contracts, documentation, dependency policy, secret scanning, cross-platform packages, fuzzing, and recovery stress.

cargo fmt --all --check
cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
cargo test --workspace --all-features --locked
cargo doc --workspace --all-features --no-deps --locked
python tools/check_documentation.py --binary target/debug/hyphae

See CONTRIBUTING.md and the development guide.

Historical source

Historical repositories are frozen inputs, not this repository's history. No historical source may enter this tree without an audited entry in the porting ledger. Hyphae Network is not modified by this project.

License

Software is licensed under AGPL-3.0-only; documentation is licensed under CC-BY-SA-4.0. See the licensing policy, NOTICE, and third-party notices. Releases through v1.0.1 retain their original Apache-2.0 terms. The Hyphae name and visual identity are covered separately by TRADEMARKS.md.