---

Heads up: This project is actively evolving. It has solid core capabilities and test coverage, and we continue to improve documentation, hardening, and feature depth with each release. Contributions, bug reports, and feedback are very welcome.

Features

• Visual graph investigation — drag-and-drop entities, explore connections interactively
• 20+ built-in transforms — DNS, WHOIS, SSL certs, geolocation, web/email/hash/social enrichment, and more
• Transform Hub — browse and install community transforms from the registry
• AI Investigator — prompt-driven agentic investigations that plan transform runs, stream progress live, and summarize findings with auditability
• Import / Export — JSON, CSV, GraphML, and MTGX format import
• Graph analysis — centrality, community detection, shortest paths
• Real-time collaboration — projects, sharing, and live sync via Supabase Realtime
• Async transform jobs — Redis/RQ queue with WebSocket progress updates
• Plugin system — directory-based plugin discovery with YAML manifests
• CLI tool — search, install, and manage transforms from the terminal
• Runs anywhere — local SQLite mode (zero config) or PostgreSQL + Supabase for team/cloud setups
• Docker ready — one-command deployment with docker compose up

Screenshots

Quick Start

Prerequisites

Tool	Version
Python	3.14+
uv	latest
Node.js	20+
pnpm	latest

Backend

cd backend
uv sync
uv run uvicorn ogi.main:app --reload

The API will be available at http://localhost:8000.

For local transform execution, Redis and the transform worker must also be running. Redis alone is not enough.

Start Redis:

docker run -d --name ogi-redis -p 6379:6379 redis:7-alpine

Start the transform worker in a second terminal:

cd backend
uv run python -m ogi.worker.run_worker

If you see Job queue not available or Redis not available, verify that:

• OGI_REDIS_URL points to redis://localhost:6379/0 for local host-based runs
• the backend was restarted after Redis came up
• the separate worker process is running
• you are not using the Docker-only hostname redis outside Docker Compose

If you run the backend against PostgreSQL (OGI_USE_SQLITE=false), startup will automatically apply Alembic migrations before serving requests. Docker deployments do the same in the backend container entrypoint.

AI Investigator runs are processed by another separate worker:

cd backend
uv run python -m ogi.agent.run_worker

Frontend

cd frontend
pnpm install
pnpm dev

Open http://localhost:5173. That's it.

AI Investigator

AI Investigator is an optional provider-backed workflow that can plan transform sequences, request approvals, and summarize investigation progress inside the workspace.

• Open the AI Investigator tab inside a project
• Configure a provider and model in the investigator settings dialog
• Store provider API keys in API Keys
• Run the separate agent-worker process alongside the backend

The current implementation supports per-user provider configuration and a dedicated worker that executes investigation steps independently from the main API server.

CLI

Two supported ways to run the CLI:

Recommended (no activation required):

cd backend
uv sync
uv run ogi --help

Activated virtualenv (plain ogi command):

cd backend
uv venv
# PowerShell:
.\.venv\Scripts\Activate.ps1
uv pip install -e .
ogi --help

Docker

Development

cp .env.example .env
docker compose up

Production

Use the prebuilt GHCR images.

Important: docker-compose.prod.yml requires an external PostgreSQL database. It does not include a db service.

If you want the all-in-one local Docker stack with built-in Postgres and Redis, use:

docker compose up -d

Use the production compose file only when you already have a reachable PostgreSQL instance and have set OGI_DATABASE_URL accordingly:

docker compose -f docker-compose.prod.yml pull
docker compose -f docker-compose.prod.yml up -d

Set OGI_IMAGE_TAG in .env to pin a specific release image tag (e.g. v0.2.6). Defaults to latest.

Hetzner Cloud

New Hetzner users can use the first link to sign up with Hetzner Cloud credits. It is a referral link, so the OGI maintainer may also receive Hetzner Cloud credits if the referral qualifies. After creating a server, use the Docker deployment commands above to run OGI.

Configurable transform caps