GraFlo

Details

External ID

45835629

Source

HN

Company

—

Product

GraFlo

Website domain

github.com

Launched

Nov. 6, 2025

Cohort

—

Upvotes

5

Upvotes percentile

0.0982532751091703

Tags

—

Fetched at

Sept. 7, 2026, 9:25 p.m.

Updated at

Sept. 7, 2026, 9:25 p.m.

Description

We built GraFlo after repeatedly writing the same boilerplate code to transform datasets into Neo4j, ArangoDB, and TigerGraph. Every time we had a new dataset (OpenAlex, IBES financial data, Debian packages), we'd write yet another custom ETL script with the same problems: ID generation, type coercion, deduplication, and database-specific quirks.GraFlo is a declarative framework that handles this once and for all. You define your graph structure in a database-agnostic schema - vertices, edges, properties, and how they map to your source data (CSV, SQL, JSON, XML). GraFlo then generates the ingestion code for your target database. The key insight: while Neo4j, ArangoDB, and TigerGraph are all idiosyncratic, the underlying property graph model is universal. We crystallized that into a single abstraction layer.What GraFlo handles automatically:- Consistent ID generation across vertices and edges- Type coercion (strings to dates, numbers, etc.)- Vertex and edge deduplication- Generating database-specific ingestion scriptsIt's plug-and-play in the sense that swapping from Neo4j to ArangoDB takes no time — just change the target database type in your config (docker compose examples provided).We've used it to build knowledge graphs from academic publications, financial datasets, and package dependencies. Instead of maintaining N × M scripts (N datasets, M databases), we maintain N schemas.On the roadmap: SQL/API integration (e.g., automatically generating GraFlo configs from SQL schemas).Would love feedback from anyone working with graph databases or building knowledge graphs.

• Source listing
• Website