Download TitanFlow

The orchestration kernel behind the Titan stack.

v0.1.0 — March 19, 2026

Choose Your Platform

macOS — Apple Silicon (M1/M2/M3/M4)

Download for macOS ARM64
0.1.0
38 MB
pending
tar xzf titanflow-v0.1.0-darwin-arm64.tar.gz cd titanflow ./install.sh

macOS — Intel (x86_64)

Download for macOS Intel
0.1.0
42 MB
pending
tar xzf titanflow-v0.1.0-darwin-x64.tar.gz cd titanflow ./install.sh

Linux — x86_64

Download for Linux x86_64
0.1.0
35 MB
pending
tar xzf titanflow-v0.1.0-linux-x64.tar.gz cd titanflow sudo ./install.sh

Linux — ARM64 (aarch64)

Download for Linux ARM64
0.1.0
34 MB
pending
tar xzf titanflow-v0.1.0-linux-arm64.tar.gz cd titanflow sudo ./install.sh

Windows — x86_64

Download for Windows
0.1.0
45 MB
pending
Expand-Archive titanflow-v0.1.0-windows-x64.zip -DestinationPath titanflow cd titanflow .\install.bat

Source code on TitanNook Board

System Requirements

macOS

  • macOS 13 Ventura or later
  • Apple Silicon (M1+) or Intel x86_64
  • 2 GB RAM minimum, 4 GB recommended
  • 300 MB available disk space
  • Network access for agent orchestration

Linux

  • Ubuntu 22.04+, Debian 12+, Fedora 38+, or equivalent
  • x86_64 or ARM64 (aarch64)
  • 2 GB RAM minimum, 4 GB recommended
  • 300 MB available disk space
  • glibc 2.31 or later, systemd optional

Windows

  • Windows 10 (21H2) or later
  • x86_64 architecture
  • 2 GB RAM minimum, 4 GB recommended
  • 300 MB available disk space
  • WSL2 recommended for full feature set

Why Self-Hosted?

Your orchestration layer should answer to you. Not to a billing dashboard, not to a terms-of-service update, not to someone else's uptime.

Own Your Orchestration

TitanFlow runs on your infrastructure. Agent routing, task queues, event buses -- all under your roof. No external dependency standing between you and your agents.

Zero Telemetry

TitanFlow sends nothing home. No usage analytics, no crash reports, no "anonymous" data collection. The kernel runs silent unless you tell it otherwise.

Built to Be Read

The source is available because you should be able to understand every decision your orchestration layer makes. Fork it, audit it, extend it. That is the point.