BlazeRules – YAML rule engine for streaming data, 3M records/SEC
Vectorized YAML rule execution hits 3M records/sec, outperforming row-based engines like DuckDB for streams.

Vectorized YAML rule engine hitting 5M records/sec before data hits your warehouse.
Backend engineers building real-time filtering or fraud detection systems
DuckDB · Apache Flink · Drools
I initially wanted to make a sub-millisecond log parser in C++ but that blew into a embeddable decision engine, that can run YAML defined rules on incoming data. The rules are executed in a vectorized format on incoming data by reprojecting into a columnar format first, if it's not already. Depending on the payload size and rules complexity, the performance goes from 200K records/s to more than million records/sec, in terms of througput this would be around 200 MiB/s to 3 GiB/s on average.
Rules can be sql expressions too, or onnx models (numeric), window ops and quite a few more operations are supported.
It's comparable to DuckDB but for streaming data and on the fly decisions
Vectorized YAML rule execution hits 3M records/sec, outperforming row-based engines like DuckDB for streams.
Vectorized SIMD execution on streaming data beats standard row engines by 10x.
Git remote trick streams CI logs to terminal, but GitHub Actions already does real-time.
YAML-to-animated-SVG terminal demos with pure CSS—no recording, embeds everywhere.
Deterministic <1ms policy kill switch for AI agent tool calls, zero ML.
YAML storyboards drive Playwright to record agent demo videos automatically.