Cronus Overview

Cronus is a graph relationship engine built on Neo4j. Its first use case is genealogical data, but the architecture supports any relationship-heavy domain: org charts, professional networks, investment graphs, and more.

Status

Currently in development - Building the core database and API.

Key Features

• Graph-native storage - People as nodes, relationships as edges
• Complex queries - Ancestry paths, common ancestors, relationship degrees
• GEDCOM support - Import/export standard genealogy format
• FamilySearch sync - Bidirectional integration (pending API approval)
• Hancock-protected - Secure access via Jetta SSO + Hancock

Technical Stack

Component	Technology
Database	Neo4j (graph database)
API	Python + FastAPI
Auth	Jetta SSO + Hancock
GEDCOM	python-gedcom library

Why a Graph Database?

Family data is inherently graph-structured:

• Parent-child relationships form trees (with cycles from cousin marriages)
• Multiple relationship types (biological, adoptive, step)
• Queries like "find common ancestors" are natural graph traversals
• "Degrees of separation" is a shortest-path algorithm

Traditional relational databases struggle with these patterns. Neo4j makes them natural.

Architecture

┌─────────────────────────────────────────┐
│           CRONUS GRAPH ENGINE           │
│  (Neo4j + FastAPI + Generic Traversals) │
└─────────────────────────────────────────┘
                    │
    ┌───────────────┼───────────────┐
    ▼               ▼               ▼
┌─────────┐   ┌─────────┐   ┌─────────┐
│Genealogy│   │Org Chart│   │  Other  │
│ Schema  │   │ Schema  │   │ Schemas │
└─────────┘   └─────────┘   └─────────┘

Links

• URL: https://cronus.jettaintelligence.com
• Repo: aic-holdings/cronus (coming soon)
• Status Page: Cronus on Jetta Status

Related

• Neo4j Schema - Database schema design

More documentation coming as development progresses.