ladybugdb

Python, LlamaIndex, LangChain, Docker Compose: 15 Property Graph, 4 RDF , 10 Vector, OpenSearch, Elasticsearch, Alfresco, Nuxeo DBs. 14 data sources (10 auto-sync), KG auto-building, Ontologies, LLMs, Docling, LlamaParse, LiteParse, GraphRAG, RAG, Hybrid Search, AI Chat. TypeScript React, Vue, Angular frontends, REST, MCP Server, optional Langflow.

AI-native financial intelligence platform for accounting, financial reporting, and investment management. Models your ledger, reports, and portfolios as a knowledge graph that AI agents can query and operate. Fork-ready: GitHub Actions CI/CD deploys the CloudFormation infrastructure to your own AWS account.

A rag + rag-graph native code intelligence layer for Java microservice estates, exposed to LLM agents via CLI

Benchmark suite for graph databases. Built to compare Grafeo with Neo4j, Memgraph, ArangoDB, FalkorDB, Nebula Graph and LadybugDB.

Thin Rust knowledge-graph service over LadybugDB. Logical successor to the Python graphiti fork.

A second brain in 3D: local-first hybrid graph-RAG. Flat vector search → graph traversal. Embedded DuckDB + LadybugDB, Ollama, NetworkX. Makes small local models punch above their weight via context efficiency.

nodejs bindings for ladybugdb

Interactive graph visualization for Python notebooks.

Git mirror for the Ruby binding for the LadybugDB embedded graph database

🧬 Probabilistic identity resolution with stable temporal CellIDs, IdentityREIM calibration, and graph persistence.

Public design handbook for building a trustworthy enterprise RAG system with hybrid retrieval, evidence ledgers, graph context, and MCP serving.

A Spring Data-like integration framework for [LadybugDB](https://ladybugdb.com), providing familiar Spring patterns for graph database operations.

A local MCP server for cross-repository semantic code intelligence in TypeScript and Go, backed by a persistent LadybugDB graph.

Proof of concept — agentic RAG over a Kimball-modelled property graph of OpenML experiment data. Claude Agent SDK orchestrator routes queries across three tools (Cypher / semantic / aggregate) against an embedded LadybugDB store with native HNSW. Local-only, no API billing.