mirror of
https://github.com/hanzoai/flow.git
synced 2026-10-17 01:29:18 +00:00
zeekayandHanzo Dev
5f360f4132
Three site deploys in this repo published to planes that are not ours. deploy-storybook.yml handed src/frontend/storybook-static to actions/deploy-pages. It is a real static site, so it moves: .hanzo/workflows/storybook.yml builds the export, POSTs /v1/projects/flow-storybook/deploy, syncs the bytes straight to the S3 prefix cloud names in the 202, then flips the deployment live — and marks it error if the run dies after enqueueing, so cloud never records a deployment as "queued" forever. Modelled on hanzoai/hips. It runs on hanzo-build-linux-amd64, a label the forge runners actually advertise; a label nothing answers does not fail, it queues silently until the 24h timeout. This is a SEPARATE file from .hanzo/workflows/deploy.yml on purpose. That one builds and pushes ghcr.io/hanzoai/flow — the App the operator runs. An App is a container the cluster executes, a Site is bytes S3 serves; folding a docs publish into an image build would couple it to a deployable release. deploy_gh-pages.yml pushed docs/ to a gh-pages branch via peaceiris/actions-gh-pages, and deploy-docs-draft.yml published per-PR docs previews to an AWS S3 bucket behind CloudFront on upstream's account (DOCS_AWS_ACCESS_KEY_ID, DOCS_DRAFT_CLOUD_FRONT_DISTRIBUTION_ID). Both are gone with no native replacement, because this repo is not where these docs live: hanzoai/docs carries them at apps/flow, and standing a second site up here would be a second source of truth for one set of pages. docs/static/CNAME (docs.flow.org) and docs/static/.nojekyll go with them — Pages artifacts that mean nothing to S3. The docs tree also shipped three third-party trackers: a Google gtag (G-SLQFLQ3KPT), the consent-mode + TrustArc scripts feeding it, and a Segment plugin reading SEGMENT_PUBLIC_WRITE_KEY. All removed, along with @docusaurus/plugin-google-tag-manager, @mendable/search and docs/src/plugins/segment. Telemetry goes to our own bus or nowhere. Analytics on the storybook is the ONE hosted tag (cloud apps/analytics/tag.go) posting to POST /v1/event. Its key is read from the project this run deploys, so pk- rotation is one server-side change rather than five repo edits, and no key means no tag: a keyless beacon is accepted 200 into $public, a tenant this org cannot read. Every other workflow stays. They are release, image-build, lint and test lanes, not deploy planes. Co-authored-by: Hanzo Dev <[email protected]>
Hanzo Flow
Hanzo Flow is a powerful platform for building and deploying AI-powered agents and workflows. It provides developers with both a visual authoring experience and built-in API and MCP servers that turn every workflow into a tool that can be integrated into applications built on any framework or stack. Hanzo Flow comes with batteries included and supports all major LLMs, vector databases and a growing library of AI tools.
Highlight features
- Visual builder interface to quickly get started and iterate.
- Source code access lets you customize any component using Python.
- Interactive playground to immediately test and refine your flows with step-by-step control.
- Multi-agent orchestration with conversation management and retrieval.
- Deploy as an API or export as JSON for Python apps.
- Deploy as an MCP server and turn your flows into tools for MCP clients.
- Observability with LangSmith, LangFuse and other integrations.
- Enterprise-ready security and scalability.
Quickstart
Install locally (recommended)
Requires Python 3.10-3.13 and uv (recommended package manager).
Install
From a fresh directory, run:
uv pip install hanzoflow -U
Run
To start Hanzo Flow, run:
uv run hanzoflow run
Hanzo Flow starts at http://127.0.0.1:7860.
Other install options
Run from source
If you've cloned this repository and want to contribute, run this command from the repository root:
make run_cli
For more information, see DEVELOPMENT.md.
Docker
Start a Hanzo Flow container with default settings:
docker run -p 7860:7860 hanzoai/flow:latest
Hanzo Flow is available at http://localhost:7860/.
Deployment
Hanzo Flow is completely open source and you can deploy it to all major deployment clouds.
Contribute
We welcome contributions from developers of all levels. If you'd like to contribute, please check our contributing guidelines and help make Hanzo Flow more accessible.