Developers

    Build on StreamFlow

    One YAML file. Four engines. A source observes, stages decide (streaming · rule-based · llm · mcp), a sink acts — every arrow between them is a durable, tailable topic.

    The mental model in one line

    text
    1source  →  stage 1  →  stage 2  →  …  →  sink
2
3 (in)      (.out)      (.out)              (act)
4
5        every arrow is a topic you can tail

    Start where you are

    Three doors in. Pick the one that matches how you learn.

    3-minute quickstart

    From empty folder to a live event — timed.

    Learning paths

    Six ordered routes: First App → Streaming → AI → Multi-Agent → Production → Scale.

    All tutorials

    Searchable catalog. Honest about time and prerequisites.

    Why developers stay

    3 minutes to first success

    The quickstart ends with your event visible in `pulse events tail` — not with a diagram.

    Everything is copy-paste-able

    Each step shows the command and the expected output. No pseudo-code, no "adapt to your setup" mid-tutorial.

    Two doors in

    Every tutorial runs in the hosted playground (zero install) or locally — same commands either way.

    Honest by policy

    Prerequisites are explicit. A tutorial that says 10 minutes takes 10 minutes.

    Everything else

    Installation

    Get Pulse on macOS, Linux, Windows.

    SDK

    Embedded or remote — same API, five languages.

    CLI reference

    Every command, every flag.

    Examples

    Working sample apps.

    When one machine stops being enough

    Everything you learn here runs free, self-hosted, forever. The day you need multiple nodes — HA, multi-region — the same app scales without a rewrite: that's StreamFlow Enterprise.

    Explore Enterprise