frankengraphdb

Stated design

frankengraphdb is described as a blank slate, memory safe, ultra high performance property graph database in Rust built on the Franken/asupersync ecosystem. It unifies MVCC, time travel history, git style branches, replication and change subscriptions into a single fountain coded commit stream, and runs transactional writes and static CSR analytics on one temperature tiered store. It offers three postures, an embedded library, a server and a CLI, all speaking GQL (ISO/IEC 39075:2024) with an openCypher on ramp, and it treats larger than memory as first class everywhere.

Honest status

The README includes an explicit note on tense: it is written in the present tense as if the entire design plan is fully realized, the 1.0 target state, so the document describes the finished system and is trued up in place as milestones land. Where the plan stages something as future work, such as horizontal sharding, the README says so plainly. There are no releases or installer yet; what runs today is example code from a source checkout via cargo run, for example cargo run -p fgdb --example open_a_database.

Context and positioning

The TL;DR argues every graph database on the market is a compromise around one old decision and surveys Neo4j, TigerGraph, Kùzu (noting Kùzu Inc was acquired by Apple and the upstream archived read only), Memgraph, FalkorDB, JanusGraph and NebulaGraph, claiming no shipping system has composed the solved academic subproblems. The project badges show Rust 2024 edition, a nightly toolchain, unsafe forbidden, and a closed universe of dependencies. The license is marked MIT plus an OpenAI/Anthropic rider.

Editorial conclusion

The license is marked MIT with an OpenAI/Anthropic rider (recorded as NOASSERTION in the metadata), the project has twenty three stars at indexing, and it is explicitly pre release with only source checkout examples runnable.