graphsub.com / wiki / zero-etl-graph-analytics
Zero-ETL Graph Analytics
Zero-ETL graph analytics lets teams query warehouse or lakehouse data as a graph without first loading it into a dedicated graph database.
Definition
Zero-ETL graph analytics maps existing data in warehouses, lakes, or lakehouses into a graph query layer.
Why teams care
The approach reduces migration friction and lets data teams run graph queries against governed analytical storage.
GraphSub context
GraphSub is complementary when the workflow needs live memory, operational traces, replay, approvals, and capsule outputs rather than only ad hoc graph analytics.
Code example
Capsule planner routesbash
curl 'https://graphsub.com/api/plan?capsule=trading-control-graph&target=enterprise-team&workload=risk-recompute' \
| jq '.execution_preview | {capsule, buyer, workflow, artifacts}'
curl -X POST 'https://graphsub.com/api/execute?capsule=regulated-evidence-graph&workload=audit-evidence' \
| jq '.execution.replay'
curl 'https://graphsub.com/api/examples'Use the live Modal routes to build and execute a capsule plan.
FAQ
- Is zero-ETL the same as operational graph state?
- No. Zero-ETL is usually analytical. Operational graph state changes as workflows run.
- Where does GraphSub fit?
- GraphSub fits where teams need a control graph for live agents, outputs, and proof.