Hanzo Flow

Models, vector stores, document loaders, text splitters, output parsers, memory, retrievers and toolkits — plus anything you write yourself, which is a component like the rest.

A component is a Python class. Edit it in the browser and the change is live on the next run — no rebuild, no plugin format, no waiting for someone to add the parameter you need.

The playground runs a flow one node at a time and shows what each one received and returned. When a chain gives a strange answer, this is where you find the node that caused it.

Several agents on the same canvas, with conversation state between them and retrieval underneath — visible as a graph rather than buried in a prompt.

As a REST endpoint, as JSON your Python app loads directly, or as an MCP server — after which the flow is a tool your coding agent can call.

Credentials live as variables the graph references by name, so a flow you export or share carries the wiring and not the secrets.